This error means that the host TinyTERM or TERM contacted rejected the connection. There are several possible reasons this can happen:

1. The host isn’t configured for the connection type you used. Make sure that you used the right connection type — telnet, rlogin or SSH. Also check the host to be sure the right server application is running.
2. The default port for the connection type isn’t what the host is using. The default ports by connection type are:
   

   telnet: 23
   rlogin: 513
   SSH: 22

   If the host is configured to use a different port, change that in TERM or TinyTERM.

3. TinyTERM connected to the wrong host. There are a few possible reasons for this:
   1. Check the hostname or IP address. If the address is wrong or has a typo, make the necessary change.
   2. If the address is correct, you can test a telnet connection in Windows or UNIX. (There is no equivalent test available in Windows for rlogin or SSH connections.) Go to a command prompt. At the prompt, type:
      

      telnet hostname

      Replace “hostname” above with the correct hostname or IP address. If that also fails to connect, check the TCP/IP settings on your PC and correct them where needed.

   3. If the address and TCP/IP settings are correct, change the address TinyTERM is using. TinyTERM references hostnames and IP addresses in a different manner. So if you have an IP address in TinyTERM, try a hostname instead. If using a hostname, try the host’s IP address.If the server has no hostname assigned, edit the system’s hosts file to create a name. Instructions for doing that in Windows are available here.
4. A firewall is blocking the connection. Check the firewall settings on your desktop system first. Windows XP and Vista include firewalls. There are also third-party products such as Norton Personal Firewall. Make sure TERM or TinyTERM is in the exceptions list for each firewall installed.

Click here to watch a screencast about this and other network connection errors.

Windows 3.1

There is one special case in Windows 3.1. If you are using Novell Client32 TCP stack, TinyTERM will give this error. The 32-bit stack does not work with Windows 3.1-compatible versions of TinyTERM.

This entry was posted on Wednesday, January 31st, 2007 at 11:45 am and is filed under Screencast, TCP/IP. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.