Connect to Test Server

Use the Connect on the Test Server Administration window to launch a Utility terminal/Shell window to Test Server. The new terminal based on the entered command, and it tries to use the USER/IP/PORT information with the SSH connection.

NOTE: If you wish run Wireshark, Connect to the Test Server and then run Wireshark manually.

To Connect via the Test Server Administration window:

Click Connect to display the Connect to Test Server Virtual Terminal Window.

Default values are build based on the Operating System. When a user uses the EXACT Default command , LS adds shell prefix commands to the string, but if just one character is different from the Default command, we do NOT do this prefixing. The command as shown in this table:

Operating System	Default Command	Actual Command
Windows	ssh -p $PORT $USER@$IP	cmd.exe /C start ssh -p $PORT $USER@$IP
Linux	ssh -p $PORT $USER@$IP	bash -c ssh -p $PORT $USER@$IP
MAC	ssh -p $PORT $USER@$IP	osascript -e ssh -p $PORT $USER@$IP

We build for different OS to wrap the command to start a Terminal. As an example for my Mac, when I click OK button, a new Terminal will pop up with below:
In addition, you can update your command based on your OS system and your Terminal application.

If the User Entered Command matches the Default Command (i.e. RESET Button), the Actual command is slightly different.
Else the command is executed WYSIWYG, exactly the string you enter is the string we execute.
Example:
Windows Default command is ssh -p $PORT $USER@$IP
If I change it to ssh $USER@$IP, the command executed will NOT include the cmd.exe shell wrapper…

cmd.exe /C start ssh $USER@$IP
putty -ssh $USER@$IP
The “OK” button will save this to the Client Settings, also the “Reset” button will set to the default command.

Click OK to launch the Connect window.
Clicking RESET button will reset the command to default value.

NOTEs:

The dialog saves and remembers your settings when you click OK.
For VPN enabled Test Server, Connect may require direct access and depending on Customer network may require the use of a “Non-VPN Public Address”. See Ping test in Configure VPN between TAS and Test Server to verify which connection to use.