Connection
Last updated
Last updated
The Connection tab page allows you to specify connection settings and logon information.
On the Connection tab page, you can define a primary connection and one or more secondary connections.
The primary connection is what Parallels Client will use first to connect to the specified server. This should be the server where the primary RAS Secure Gateway is running.
To specify the primary connection information:
In the Primary Connection field, specify the server name or IP address. To connect to a specific RAS Theme, specify its name after the server name or IP address separated by a slash. For example, workspaceus.parallelsras.net/theme1. If not sure which Theme you should use, ask your system administrator.
In the Connection Mode drop-down list, select one of the following options:
Gateway Mode. Parallels Client connects to the RAS Secure Gateway and the session connection is tunneled through the first available connection. This mode is ideal for servers which are only reachable via the gateway and do not require a high level of security.
Gateway SSL Mode. Same as the gateway mode above, but uses encryption to secure the data.
Direct Mode. Parallels Client first connects to the RAS Secure Gateway for the best available terminal server and then connects directly to that particular server. This is best used when the Parallels Client and the terminal server are on the same network.
Direct SSL Mode. Same as the direct mode above, but uses encryption to secure the data.
In the Port field, specify the port on which the gateway listens for incoming connections. If the default value (80) has been modified on the server side, you have to replace the default value here as well. Ask your system administrator about the port number if you are having a problem connecting to the server.
In the Friendly Name field, choose and type a name of your choice, so you could easily identify the server in Parallels Client later.
If the Parallels RAS farm that you are connecting to has more than one RAS Secure Gateway, you can define a secondary connection, which will be used as a backup connection in case the primary gateway connection fails.
To add a secondary connection:
Click the Secondary Connections button.
In the Secondary Connections dialog, click the Add button and specify a server name or IP address. This should be a server hosting a secondary RAS Secure Gateway (the primary gateway is used by the primary connection).
Select the connection mode and modify the port number if necessary. Click OK and then click OK again to return to the Connection Properties dialog.
In the Logon section, specify the following properties:
Select the Auto Logon option to enable Parallels Client to connect automatically (using this connection) on startup.
In the Authentication type drop-down list, select the desired method of authentication:
Credentials. Select this option and then enter the username, password, and domain information. You will be authenticated on the remote server using the specified credentials. Please note that if the password specified in the connection properties has expired or will expire soon, you will see a corresponding message on the screen when trying to connect to Parallels RAS. If the password has expired, you'll be asked to change it. If the password will expire soon, you will be offered to change it now or later. Follow the onscreen instructions and change your password.
Single Sign-On. This option will be included in the list only if the Single Sign-On module is installed during Parallels Client installation. Select this option to use local system credentials to connect to the remote server.
Web. Select this option to use the SAML SSO authentication.
Smart Card. Select this option to authenticate using a smart card. When connecting to the remote server, insert a smart card into the card reader and then enter a PIN when prompted.
Note: Smart card authentication is not supported in Parallels Client for Linux.
Note for Administrators: The allowed authentication type(s) must be specified in the RAS Console in Connection / Authentication.