Connecting to the server behind a stormShield firewall #424
Replies: 3 comments 4 replies
-
|
We have never encountered this. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, We have again somme acces error on some server behind a "complex firwall" (such as stormShield, cisco, or cosy), event with a 443 proxy firwall. I would like to know if rustdesk use some other port (21115, 21118, ...) event with the 443 proxy. PS : on most of our clients (event on some client with a stormShield firewall), the proxy on 443 solved our access problems |
Beta Was this translation helpful? Give feedback.
-
|
j'ai créé deux version d'executable, l'une en http (utilisé par defaut), et l'autre en https. Ainsi j'économise un peut de ressource CPU, en ne passant pas la phase encodage/décodage que lorsque c'est nécessaire. Et je n'ai pas contacter de bug avec le HTTPS (contrairement à ce que l'on peut lire sur d'autre post avec la methode HTTPS via apache/gninx) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
We have just installed a Pro version of RustDesk on our server.
In most cases we have no problems.
However, for some of our customers where we want to install 'the host version' the connection is impossible.
The particularity of these customers: their network infrastructure includes a stormShield firewall upstream (https://www.stormshield.com/ ). It is a kind of "advanced" firewall that does a lot of things and among other things DPI. And obviously we do not have access to the interface of these stormShield
The error message is relatively clear. "network XXXX inaccessible".
Similarly we cannot connect the application to the user account (socket timeout).
Have you ever encountered this kind of problem?
Note: TeamViwer Host works behind a stormShield
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions