"Network Names" and Connection Modes-
  FAQs 
  < BACK TO QUESTIONS 
question
What would be the best "Network Name" for my connection (or published application)?
  
answer

WebConnect Server allows the users to work in two different connection modes:

1) Direct mode ("No Gateway") - The user connects to the WebConnect Server in order to authenticate himself, and in order to get the list of published applications and host connections. When launching the desired connection - a direct and independent channel between the user and the remote host is established.

This mode can be used only when a direct connection between the user and the remote host (Terminal Server \ legacy host) is possible.

For example, in order to be able to use RemoteView in direct mode, the user has to have the ability to establish RDP connection from his machine to the remote Terminal Server.


2) Gateway mode - All the communication between the user and the host (or Terminal Server) goes through WebConnect`s SSL tunnel. This mode should be selected when the users must use the WebConnect as a gateway in order to be able to connect to the remote host or Terminal Server.  

The direct mode has two main advantages:

A. Better performances - since all the communication between the user and the remote host goes directly between them.

B. An active session between the user and the remote host does not disconnect when the WebConnect Server is unavailable or down. 

 In case that some of the users who use the connection can work in direct mode and others do not have a direct access to the remote host, WebConnect can automatically determine the appropriate working mode for each user. In order to configure WebConnect HostView to set the appropriate working mode according to the user`s location, simply set the Network Name to "Public".

RemoteView users can get the same functionality by setting the Network Name to one of the following options:

I) "Smart Internal"  - When the WebConnect Server and the Terminal Server\s are located on the same network.

II) "Smart External" - In case that the WebConnect Server and the Terminal Server\s are located in different networks.

 Comments:

* In most cases, the RemoteView connections should be set to "Smart Internal"

* In order to improve the performances of remote users (who are currently working in "Gateway Mode") - we would recommend providing the users SSL VPN connection. SSL VPN connection will allow the users to work in Direct Mode, and will improve their connection`s performances significantly.




Top