SSH Server for Windows NT/2000/XP/2003 Online HelpInstalling GoodTech SSH Server Configuring GoodTech SSH server Creating and Configuring Accounts Setting up Configuration Variables GT_SSHD_LOGIN_IDLE_TIME - Login Timeout GT_SSHD_SESSION_IDLE_TIME - Session Timeout GT_SSHD_MAX_USERS - Limiting the number of users GT_SSHD_USER_HOME - Specifying User Home Directory GT_SSHD_DISABLE_WEB_ADMIN - Disabling web administration GT_SSHD_HTTP_PORT - Defining Port for web administration GT_SSHD_DOMAIN_ENABLE - Show domain prompt in authentication GT_SSHD_DEFAULT_DOMAIN - Default domain when domain is disabled GT_SSHD_DISABLE_UNMAP - Disabling unmapping of network drives GT_SSHD_DISABLE_JOB - Disabling the termination of job process tree GT_SSHD_PROTOCOL - SSH protocol (SSH2) GT_SSHD_LOGIN_FILE - Setting global login script
Administrating GoodTech SSH server Using Windows Interface to Control GoodTech SSH Service Starting GoodTech SSH server Service Stopping GoodTech SSH server Service Pausing GoodTech SSH server Service Working with GoodTech SSH Server IntroductionThis help document describes how to install, configure, use and administrate GoodTech SSH Server. Although we did our best to proofread this help, we are unfortunately not immune to mistakes and omissions. If you find any mistake or have suggestions to improve this help, please let us know. GoodTech SSH Server product uses the cryptographic library cryptlib, by Digital Data Secutity (DDS). cryptlib is a powerful security toolkit, and it is used in GoodTech SSH Server product to implement encryption and authentication services. All cryptlib copyrights are reserved to DDS. Introduction to GoodTech SSH Server GoodTech SSH server for Windows NT4, 2000, XP, and 2003, provides secure remote access to your Windows machine that includes: Remote Console, File Transfer and Port Forwarding. GoodTech SSH Server for Windows NT/2000/XP/2003 is an SSH Server application that runs on a host computer and allows remote users to securely access the host. It supports the following services:
When Goodtech SSH Server is installed on your Windows system, you can securely access from remote systems and run programs on your Windows System. It is a secure, functional, easy to use and high performance tool, that is written based on security standards, can communicate with any standard SSH client and is highly integrated with Windows operating system. You can connect to GoodTech SSH Server from anywhere in the world and login as if you were sitting at the console, using SSH client. Whether you are a system administrator, a programmer or a DOS application user, GoodTech SSH Server can provide you with the SSH Server functionality that you need. The installation program creates a SSH service called SSHd and adds it to the list of services available on your Windows system. When the SSH Server service is started, either manually or automatically, it executes a program named SSHd.exe. The program SSHd.exe opens a log file SSHdv#.log (v# is the SSH server version number) in the %gt_SSHD_installation_dir% directory (gt_SSHD_installation_dir is a system environment variable created during installation, that contains GoodTech SSH server installation directory) SSHd.exe is now ready for connection requests. It listens to requests on the specified listening address and on the specified port. If a listening address was not specified it listens on all host IPs. If a port was not specified it listens on the default SSH port (#22) . When a user wants to remotely access the host running GoodTech SSH Server, he runs a secure SSH client. The SSH client program sends a connection request to the listening address. The SSHd.exe program gets the request and opens a thread, which is responsible for this connection with the client. This thread relieves SSHd.exe from communicating with the client and let SSHd.exe focus on listening to other connection requests. The client thread starts the authentication process. It asks the SSH client for login information. The login information consists of a User ID, Password and optional Domain. The client thread then uses the internal Windows security mechanism to check if the user is allowed to access the host. If the user passes authentication, he is logged onto the host system. The client thread creates a process that runs a program named SSHcmd.exe. The SSHcmd.exe program creates a shell process that by default runs the cmd.exe or a a different shell that was specified. The remote user is now ready to work on the host.
GoodTech SSH Server Key Features
When you purchase GoodTech SSH server we email you your registration number along with your registered copy of the product. Our simple licensing policy lets you purchase as many copies as you need and get a single license for all copies. It simplifies multi copy installations. Installing GoodTech SSH ServerGoodTech SSH Server requires Windows NT 4.0 (all service packs), Windows 2000, Windows XP and Windows 2003. The TCP/IP protocol must be installed on your Windows System. This protocol is included with the Windows operating system but is not always installed on all systems. You can check if TCP/IP is installed on your system by choosing Network from the Control Panel. If TCP/IP is installed on your system it should show up in the list of Installed Network Software. You should use the Administrator account or any other account with administration privileges to install GoodTech SSH Server. Make sure that all users have READ/WRITE/EXECUTE permissions to the SSH Server installation directory, and READ permission to the SYSTEM32 directory. (e.g. C:WINNT\SYSTEM32). You can change the permissions to the executable files in the SSH Server installation directory to READ only. Running the Evaluation copy Installation Program After downloading the evaluation copy of GoodTech SSH server or receiving the registered copy, you have to perform the following steps:
Running the Registered product installation program If it is the first time that you install GoodTech SSH Server and you don't have the evaluation copy installed on your computer, follow the instructions for "Running the evaluation copy installation program". In case an evaluation copy is already installed on your computer (or an earlier version of the product) you have to uninstall the evaluation copy (follow the "Running the uninstall program" section) and then install the registered software as listed in ""Running the evaluation copy installation program". If you want to install a new version of GoodTech SSH Server but have a previous version currently on your system, you have to do the following:
If you want to uninstall GoodTech SSH server from your system, choose one options from the following 3 options:
Please note that silent uninstall is also supported by issuing the command: uninst.exe /S Configuring GoodTech SSH serverCreating and Configuring Accounts Creating the SSH Administrator Account – sshd sshd is the SSH administrator account. Administration commands can be performed only from the sshd account. You have to create an account for the user sshd (in lower case!), using the Windows NT User Manager or User Manager for Domains. No special permissions/groups are required for this account. When a user logs in to your system via GoodTech SSH Server, he must be a valid user that was created by the Windows network administrator, using Windows User Manager or User Manager for Domains. GoodTech SSH Server sets a user’s process to run in the security context appropriate to that user. The user privileges on the SSH host machine are identical to those he would have if he sits in front of it and logs in on the console. If a user’s home directory is specified in the Windows account database, GoodTech SSH Server changes to that home directory when the user logs on. Network drive for a user home directory is supported. If the user home directory is not specified in the Windows account database, the configuration variable gt_SSHD_user_home is used by GoodTech SSH Server. Please refer to "Setup Configuration Variables" for information on how to setup a configuration variable. If no home directory is specified, the %SystemDrive% is assumed as the home directory. If a user’s login script is specified in the Windows NT local account database, GoodTech SSH Server executes the login script in the user’s home directory when the user logs on. GoodTech SSH Server supports local logon script and domain logon script. If you want to specify a local login script, you can put it in the default scripts
directory: If the login script is located in a subdirectory of the default login directory, precede the filename with that relative path. For example, you might type clerks.bat if the script is located in the default script directory, or you might type \admin\clerks.bat, if the script is located in a subdirectory admin under the default logon path. If you want to specify a domain
login script, you can put it in the default domain scripts directory, on the
domain server machine: You can also define global login script that will be used for ALL users. Setting Up Configuration Variables You can create the file config.dat in your installation directory in order to change the default configuration of GoodTech SSH server. You can specify in the file only the parameters that you need to change their value. The file contains a list of parameters and their values, one in a row, in the following format: PARAMETER=value The parameter should be written in upper case. No spaces next to the equal sign. GT_SSHD_LOGIN_IDLE_TIME - Login Timeout Definition: Specifies the time period, in seconds, allowed for the login process before it is automatically disconnected from the host. if a user doesn’t provide login input in the timeout period (for example, 30 seconds), the session is closed by the SSH Server. In case a session is disconnected, the message "Timeout period expired" is displayed on the user’s SSH window. Default value: 60 seconds GT_SSHD_SESSION_IDLE_TIME - Session Timeout Definition: Specifies the time period, in minutes, allowed for a session to be idle before it is automatically disconnected from the SSH Server. In case a session is disconnected, the message "Timeout period expired" is displayed on the user’s SSH window. Default value: 120 minutes GT_SSHD_MAX_USERS - Limiting the number of users Definition: Specifies the maximum number of concurrent SSH users allowed to connect the host machine. For example, if you have a 10 concurrent connections license, and you set gt_SSHD_max_users to 5, then 5 users at the most can be concurrently connected to the host. Valid values: 0 < GT_SSHD_MAX_USERS <= License limit Default value: License limit GT_SSHD_USER_HOME - Specifying User Home Directory Definition: Specifies the home directory for the users. If a user’s home directory is specified in the Windows NT account database, GoodTech SSH Server changes to that home directory when the user logs on. If the user home directory is not specified in the Windows NT account database, this configuration variable is used. If no home directory is specified, the %SystemDrive% is assumed as the home directory. Valid value: Full path of the user home directory Default value: If no home directory is specified, the %SystemDrive% is assumed as the home directory (Windows environment variable). GT_SSHD_DISABLE_WEB_ADMIN - Disabling web administration Definition: Allows to disable the Web administration interface. In this case, the command line interface is used for administration. Valid values: yes Default value: not defined GT_SSHD_HTTP_PORT - Specifying Port for web administration Definition: Specifies the HTTP port for Web administration. You can later administrate the SSH Server at the following URL: http://name or IP address of machine that runs SSH Server:GT_SSHD_HTTP_PORT value (e.g. http://localhost:2280) Default value: 2280 GT_SSHD_DOMAIN_ENABLE - Show domain prompt in authentication Definition: You can enable a domain prompt during login phase, by setting this configuration variable to 'yes'. Enable the domain prompt to allow remote authentication. (The user provides the remote domain name during login). For local authentication on the server where GoodTech SSH server runs, there is no need for the domain prompt. In this case, the local account database is searched. Valid values: yes Default value: not defined GT_SSHD_DEFAULT_DOMAIN - Default domain when domain is disabled Definition: In case the GT_SSHD_DOMAIN_ENABLE is set to yes, this parameter defines that domain name for authentication. A User can override it in the login process by typing a different domain name. Valid values: Valid domain name Default value: not defined GT_SSHD_DISABLE_UNMAP - Disabling unmap of network drives Definition: When a user exits a session, all mapped drives are removed by default. To leave the mapped drives, set this parameter to 'yes'. Valid values: yes Default value: not defined GT_SSHD_DISABLE_JOB - Disabling the termination of job process tree Definition: A user can run applications in the background (i.e. clock, or notepad) while working in a SSH session. When the user exits the session, all the applications are closed by default. To leave background applications running after session exit, set this parameter to 'yes'. Valid values: yes Default value: not defined GT_SSHD_PROTOCOL - SSH protocol (SSH2) Definition: Specifies the SSH protocol used for communication between the SSH server and the SSH client. SSH2 is the preferred protocol. Valid values: SSH2 Default value: SSH2 You can define global login script for ALL users using the SSH Server. The file will be executed as part of the login process of each user connecting through the SSH Server. You should create environment variable named gt_sshd_login_file and set the value to the full path of your login file. (Including the file prefix). Valid values: Full path of the login script. Default value: None You can disable SSH (Secure Shell) or SFTP (Secure file Transfter) for users using SSH Server. You can add the following line to your config.dat file when you want to disable SSH: GT_SSHD_DISABLE_OPTION=SSH Valid values: SSH or SFTP Default value: Both options (SSH and SFTP) are enabled. By default the bell character (ASCII 0x7) is heard on the Server machine when using SSH protocol. In order to hear the bell sound on the SSH Client, you should create a system environment variable named gt_bell_char and set the value to ASCII decimal 134 (which is a lowercase a with a circle over it). Any application running on the server that writes the ASCII value 134 to the screen will enable the bell sound on the client side. This option in only valid when using screen mode. Valid values: ASCII number 134 Default value: None By default ASCII characters under decimal 32 will be replaced by the space character (ASCII 32). In order to see ALL characters including the ones under ASCII 32, you should create a system environment variable named gt_show_all_chars and set the value to 'yes'. Valid values: yes Default value: Characters under ASCII 32 (space char) will be replaced by the space character. Changing the default window size By default the Window size is set according to the size of the SSH client. In case you want to change the default behavior you should create a system environment variable named gt_window_size and set the value to rows,cols. For example to set the default window size to be 10 rows and 40 columns the value for this system variable should be 10,40. Valid values: rows,columns Default value: 25,80 (Depending on the SSH client window size) The IP that GoodTech SSH server listens on is defined in a file called: gt_sshd_address.dat If the file does not exist (this is the default), SSH Server listens on all the IPs defined on the server machine. The format of the file is one line that specifies a valid IP address, (i.e. 10.0.0.250). Host name is not supported. The default SSH port is port number 22. However, in case port 22 is used by another application, you can set up GoodTech SSH server to use a different port. You can set a different port by doing the following: 1. Click on the start button and run the
REGEDIT program. This method works for both, automatic and Manual startup of GoodTech SSH Server. Another way to do this is to specify the port number to be used by the SSH Server in the Startup parameters input box when starting the SSH Server service. This method works only if you start and stop the SSH Server manually. The SSH client program must be set up to use the same port as the SSH Server. If you set up the SSH Server to use a port different than the default (#22), you also have to set up the SSH client to use the same port. Host server identifies itself to a client using a unique host key. The first host key is generated during the installation of GoodTech SSH Server. In the installation process the administrator is prompt for host key password. This password is used as a key-encryption key. The host key is stored in encrypted form in the file sshd_hostkey.dat. It is recommended to establish a policy that determines the permitted lifetime of the key host, and to generate a new host key anytime the key lifetime is over. The program that generates a new host key is named: hostgen.exe, and is located in the SSH installation directory. Anytime that you run this program, you are prompt for a new password. Filtering - Configuring which client hosts can connect Remote access can be limited to specific hosts or IP addresses. Host or IP filters are enforced when the file gt_sshd_ipf.dat exists in your installation directory. The first line in this file can be ONE of the keywords, INCLUDE or EXCLUDE. When the first line contains the INCLUDE keyword, all hosts or IP addresses listed in the following lines are the only hosts/IP addresses that have the permission to access the server machine via SSH. All other hosts or IP addresses are not allowed. If the first line contains the keyword EXCLUDE, all hosts/IP addresses listed after this line do not have permission to access the server machine via SSH. All other hosts or IP addresses are allowed. The following lines list IPs or hostnames, one in a row. It is also possible to list a partial IP, i.e. 10.0.0 to refer to all the IPs that start with 10.0.0 (from 10.0.0.0 to 10.0.0.255) For example: In full screen applications, such as MS edit, VI, FCW. etc., the cursor can be located anywhere on the screen. Screen mode applications are displayed properly only if you are in screen mode. In Line mode, the cursor is always located on the last line of your SSH session window. In this mode you can use the scroll buffer. You can setup a system environment variable gt_mode to either screen mode or line mode (valid values are "screen" or "line"), based on the mode that most system users use the most. The default is screen mode. It is possible for users to change the mode on the fly during a SSH session. In order to change the mode from screen to line, issue the command: set gt_mode=line. To switch back to screen mode issue the command: set gt_mode=screen In addition you can also create a file named gt_ip_mode.dat in your SSH Server installation directory that contains the default mode for a specific IP address. (line or screen). For example the following line sets the default mode to be line mode for IP 192.168.10.1: 192.168.10.1 line You can also sets the default mode for a specific user. You can create a file named gt_user_mode.dat in your SSH Server installation directory and create a line that contains the user with the default mode. (line or screen). For example the following line sets the default mode for user Sam to be screen mode: sam screen Each of the above files can contain more than one line. You can customize the welcome message that appears during login phase by creating a file named gt_sshd_welcome_message.dat in your SSH Server installation directory. You can put your custom welcome message in this file and it will be displayed during the login phase. If you want users to print locally from a SSH session, you need to configure both the SSH Server and the SSH client. The configuration of the SSH Server side is explained below. Please refer to "Configuring the SSH Client/Client Printing" for information on how to configure the SSH Client for client printing. See also "Work with GoodTech SSH Server/Client Printing" for information on how to set up your SSH session to print locally. You need to Follow the steps below if you want to allow users to print locally on their printers:
2.
Create a Virtual Printer
Using Alternate Command Shells GoodTech SSH Server for Windows NT supports other command shells than CMD.EXE. For example, 4Dos for Windows NT (4NT) from JP Software is supported. If you want all the SSH users to make use of a command shell other than CMD.EXE, change your ComSpec system environment variable to point to that command interpreter program. For example, if you want to make use of 4NT, change the ComSpec system variable to point to 4NT.EXE program instead of to CMD.EXE program. For instructions on how to change the Comspec variable value please refer to the "Setup System Environment Variables in Windows NT" section. If different users have different preferences regarding what command shell to use, it is possible to make the change at a user level. A user can change the command shell used from its SSH session. For instructions on how to do that, please refer to Work with GoodTech SSH Server/alternate command interpreter. Setting Up System Environment Variables in Windows NT Go to the control panel, system, environment, select the system variable scrolling list, then enter the parameter (gt_print_monitor, gt_mode or comspec) in the variable text box and the value in the value box. Press the Set button and then the OK button. You have to reboot your computer after defining system environment variables for the change to take effect. (Please note that you need to create SYSTEM variables and not USER variables). Administrating GoodTech SSH ServerConnecting to the Web Interface Administration commands can be performed via a web browser. This management option gives you a graphic interface to administrate the SSH Server product. You can always use the command line interface to get the same results. In order to use this option, you should open a web browser with the following URL: http://name or IP address of machine that runs SSH Server:GT_SSHD_HTTP_PORT value For example: you can write http://my-machine:2580 In this case the host name is my-machine and the GT_SSHD_HTTP_PORT configuration parameter is set to the value of 2580. or you can write http://192.168.0.1:2280 In this case the host IP is 192.168.0.1 and the default http port is used (GT_SSHD_HTTP_PORT configuration parameter is not set). If the SSH Server is up you get a login page. You can login as a 'sshd' user or any other user that belongs to the administrators group. Administrators group is the only group that has SSH Server administrative privileges. This page offers the following options:
Press the Submit button to execute the option of your choice. The Disconnect button disconnects you from the server. The Refresh button refreshes the SSH Server status on the status line. The following information is displayed for each open session: Login time - client login time Sid - system identifier of the client session IP address - client IP address User name - client user name Kill Connection button - kills all checked client sessions. Main Menu button - takes you back to the options page. Refresh button - refreshes the SSH Server status on the status line. Administration commands can be performed only from the 'sshd' account. You have to SSH to the host as user sshd, either locally, from the host itself, or remotely, from a client. More than one sshd user can SSH out to the host at the same time. However, each is count against the maximum number of concurrent connections allowed. It is recommended to keep at least one sshd user session open, so administration commands are available even when all concurrent connections are in use. The following commands are available: Service Administrating Commands
Clients Administrating Commands
Using Windows Interface to Control GoodTech SSH Service It is possible to specify an automatic startup for GoodTech SSH Server. To do so, you have to perform the following steps:
Starting GoodTech SSH server Service You have the following options:
Stopping GoodTech SSH server Service You have the following options:
Pausing GoodTech SSH server Service You have the following options:
Continuing GoodTech SSH Server Service You have the following options:
Restarting GoodTech SSH Server Service from remote
Administrative Messages from the SSH Server
GoodTech SSH service uses two Log files, SSHd.log and SSHdcmd.log, to keep a record of everything it does. The log files are kept in GoodTech SSH server installation directory. For information on how to monitor your Log file please see the section "Monitoring the Log File". Your log files can grow quite large and quite fast, especially if your host gets a large number of SSH users per day. The size of the files can eat into your disk quota and tie up needed space. To reset your log files, you need to delete the files when the SSH Server service does not run. The next time the SSH Server will run, new log files will be created. Working with GoodTech SSH ServerChoosing Your SSH Client software GoodTech SSH Server can work with any standard secure SSH client and secure file transfer client. There are quite a few SSH and file transfer clients available. We recommend GTTerm from GoodTech systems. Some of them are free. For example, you can use PuTTY as SSH and port forwarding client and WinSCP as GUI secure file transfer client. Encryption, Authentication and Compression You can configure your SSH client to use the following encryption and authentication algorithms, which are supported by Good|Tech SSH Server: AES, Blowfish, CAST, DES, triple DES, IDEA, RC2, RC4, RC5, and Skipjack, conventional encryption, MD2, MD4, MD5, RIPEMD-160 and SHA hash algorithms, HMAC-MD5, HMAC-SHA, and HMACRIPEMD-160 algorithms, and Diffie-Hellman, DSA, Elgamal, and RSA public-key encryption. If you need to secure an unsecured server application in use in your organization, you can use the secured channel of GoodTech SSH Server. GoodTech SSH Server gets the client requests on a secured channel and forwards them, locally, to the unsecured server. All you need to do is define on the client a source port on which the client listens, and a destination port and IP to which data is transferred. The key maps expected by GoodTech SSH Server are listed below. Check the SSH client for documentation on how to add entries into the keyboard mapping table. The first column is the keyboard key and the second column is the string sequence GoodTech SSH Server expects to receive for the keyboard key. Double quotes are shown in the escape sequence for reading convenience, but are NOT to be sent. Numbers (\xxx) are given in decimal notation. For example, to simulate F1, the SSH client should send ASCII number 27(not the string 27), followed by O and P (\027 stands for the decimal ASCII 27).
If you want the backspace key to work properly, configure the backspace key to send backspace and not delete. The backspace key should send CTRL-H. PC applications use the PC character set to generate character graphics. Many terminal emulator graphic character sets are different from the PC character set. In order to get all graphic characters properly displayed by GoodTech SSH Server, use a SSH client that supports character set or font selection. Choose the character set or font that is based on the IBM PC character set. Some PC applications make use of colors. In order to get all colors properly displayed by GoodTech SSH Server, use a SSH client that supports colors. Choose the ANSI color option in the SSH client setup menu. ESC key To simulate the ESC key, you need to press the Escape key twice. Follow the steps below if you want to print locally from your SSH session:
Enable an Alternate Command Shell You can make use of a command shell other than the default CMD.EXE, by running the other shell program from the SSH session. For example, to use 4NT from JP software, you can run 4NT.exe from your SSH session prompt. Connecting to GoodTech SSH Server Once you have chosen a SSH client or file transfer client, connecting to GoodTech SSH server is simple. Although SSH clients and file transfer clients vary in their exact configuration, most of them will simply require you to specify a "remote host". Your remote host is the host where the SSH Server runs. Once you are connected, you are prompted for your login name, login password and optionally for domain (if the configuration variable GT_SSH_DOMAIN_ENABLE is set to yes). The login name is the name of the user account. The password specifies the password for the user account. The domain specifies the name of the domain whose account database contains the user name account. For remote authentication you provide the remote domain name. For local authentication on the server where GoodTech SSH server runs, leave it blank. In this case, the local account database is searched. While the SSH Server authenticates your login information, the message "Authentication is in progress…" is displayed on your screen. If the authentication fails, the message " Login incorrect, please try again, authentication failure" is displayed on your screen. After three failure attempts the message " Login incorrect, Closing, 3 failure attempts" is displayed on your screen. Your session is disconnected from the host. If you don't fill out the login information within the time period that was specified by the system administrator for login input, your session is disconnected from the host and the message: "Timeout period expired " is displayed on your screen. After a successful login, you have access to the host Server and can issue commands at the command prompt. Switch Between Screen Mode and Line Mode You can easily switch between modes while in a SSH session. There is no need to re-login any time you change the mode. The default mode depends on how the administrator set the system via the system environment variable gt_mode. If you want to switch to line mode, type the command: set gt_mode=line You have to type the above command in lower case letters and with no extra spaces. This command creates a new DOS session and you are ready to work in line mode. The scroll buffer is available. If the cursor does not move to the next line any time you press the enter key, you need to set up your SSH client to do so. If you want to switch to screen mode, type the command: set gt_mode=screen You have to type the above command in lower case letters and with no extra spaces. This command creates a new DOS session and you are ready to work in screen mode. The scroll buffer is not available any more. Some old applications, such as EDIT.com or debug.exe, are best displayed if the window size is set to 25 lines * 80 columns. However, if the application supports a window size other than 25*80 (i.e. FCW.exe), it is possible to resize the window while connecting to GoodTech SSH server. The window size is changed automatically when you change the window size on the SSH client. The default window size is 25*80. You can also change the window size using the following command within the SSH session: set gt_window_size=row,column where row and column define the window size. For example, if you type: set gt_window_size=30,80 GoodTech SSH Server will support the new window size of 30*80. Windows NT interprets the Alt as a local menu key. As a result, the Alt key is interpreted by Windows NT and is not transferred to the SSH Client program (or other programs). A replacement key have to be entered at the SSH client in order to have it mapped to the Alt key in the SSH Server. CTRL-A has been re-mapped to act as the Alt key in a SSH session. For example, when working in EDIT.COM, to access the File Menu, instead of pressing ALT-F, press CTRL-A and F to represent ALT-F. Because CTRL-A is used to simulate the ALT key, you need to press CTRL-A twice to simulate CTRL-A. To simulate ALT-A, you need to press CTRL-A and ESC key. To use the number pad keys, make sure that NUM-LOCK is disabled. If you want to print locally from your SSH session, you need to issue the following command from the SSH session any time you SSH to the server: NET USE lptn: \\ServerName\gt_printer lptn: lpt1, lpt2 or lpt3 depending on what port you are printing to. lpt1 is the default port for printing. ServeName: The remote host you are connected to. Example: NET USE lpt1: \\YourHostName\gt_printer This command redirects printing from the server printing port to the virtual printer, so GoodTech SSH Server can read from the virtual printer and send the printing to the client for print out. If your session is connected to the SSH Server, but is idle (no input is sent from the client to the server within the time period that was specified by the system administrator), it is disconnected from the host and the message: "Timeout period expired " is displayed on your screen. Once your SSH connection is established, your SSH client remains connected to GoodTech SSH Server until one of the following happens: You request to disconnect by:
The SSH administrator disconnects you by:
Abnormal termination:
Trouble ShootingIt is possible to encounter a problem while using GoodTech SSH server, especially if these are your first steps with the SSH Server. The best place to look for answers to questions/problems is this help. You can try monitoring the log file. If you don't even get to the point that your SSH Server is up and running and the log file does not exist yet, try our error messages list. If your error is listed on that list, you'll find the corresponding recommended course of action. And of course, you can always contact our technical support experts. Don't hesitate to contact us, your questions are welcome. Please provide the following information when you contact our support:
The GoodTech SSH service uses Log files to keep a record of everything it does. Most of the entries you'll find in the log files are informational or success messages. However, error messages are also written to the log files, and these are what you are looking for, when you are facing a problem. Whenever an error occurs, the SSH Server writes the error number into the log file. You can get the error number by searching the string "error no" in your log file. In case this string is found more than once, the first error message is the error you want to solve. In most cases, other errors are a result of the first one. In the log file you will find only the error number, but you can easily translate the error number to its description by doing the following: Go to a Command Shell Prompt and type "NET HELPMSG [error number]" If the error description is too vague and you are not sure what should you do to overcome the problem, try to check out the error in our list of common errors for a recommended course of action. The error messages you encounter as you start using GoodTech SSH Server are most likely common errors that others encountered as well.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||