This error means the IP address or hostname supplied for the connection is incorrect. Test the connection using the ping command from a system prompt. If you receive errors, verify the address or hostname you’re using.

If ping works, try to telnet to the host from a command prompt. Errors from this command indicate possible problems with the network or TC/IP configuration on your PC.

In this situation, TinyTERM connects to a host via serial cable successfully. Another application on the PC then makes a modem connection. This causes the system to lock up completely.

Check the IRQs used by the serial port and modem. If both are trying to use one IRQ — or worse, one COM port — that will cause the lockup. Assign the modem its own IRQ.

TinyTERM and TERM for DOS can both connect via IPX/SPX. They do not require TCP/IP as TinyTERM and TERM for Windows do.

In TinyTERM 4.00-4.13, there is no flow control setting in the user interface. To set flow control for those versions, go through Windows Device Manager and set it directly on the serial port.

A user interface for this was added in TinyTERM 4.20.

CR 25

Closing TinyTERM version 4.x, if you get “An error occurred in CenTE.ocx” when the last connection closes, it indicates a corrupt file. To fix the problem, uninstall TinyTERM. When that completes, reboot the PC and reinstall TinyTERM.

The SNA protocol is a native IBM network protocol. TinyTERM does not support it for TN3270 or TN5250 emulations. Only TCP/IP connections are supported.

In this situation TinyTERM works with telnet, but SSH sessions connect and immediately disconnect. This only happens if you have “Login at connect” checked in the Login tab of TinyTERM’s Session Properties.

Early versions of SSH in TinyTERM require a username and password on the Login tab, but the “Login at connect” caused connection problems. Without that set, TinyTERM connects and logs in properly. In later versions of TinyTERM, that option is grayed out when SSH is set.

If that option is not checked, check the version of sshd running on the host. TinyTERM versions 4.10-4.13 use SSH version 1.5. SSH 2.0 daemons must be configured to allow pre-2.0 connections when using those versions of TinyTERM.

Using the telnet connection type, TinyTERM 4.0x may fail to connect. Older versions of TinyTERM work, as does Windows telnet. Switching between the hostname and IP address makes no difference. TinyTERM just seems to hang.

This happens when the host sends a signal that puts TinyTERM into binary mode. Binary mode is typically only used by TN3270 and TN5250 emulations. It can cause problems for other terminal emulations.

CR 65, fixed in TinyTERM 4.10

TinyTERM and TERM for Windows can store multiple IP addresses and telephone numbers in a single configuration file. If you want to clean the list out, so it only shows one address or phone number, close TinyTERM. Open the .tap or .tpx file you’re using, such as default.tpx, in any text editor. Notepad or Wordpad will work.

Search for the line that starts “node=”. Delete everything after the equals sign =. Save the file and exit.

If there is one host address or phone number you want to save, make it the only entry after the =. Either way, the changes you made will take effect the next time you start TinyTERM.

There are two main causes for this error. The first is an error in the fingerprint.

To remove the fingerprint in Windows, open the Registry Editor and go to HKEY_CURRENT_USER\Software\Century Software\HostKeys. Delete all the entries inside that folder, but leave the folder itself there, then close the Registry Editor. The next time you start TinyTERM and connect to that host, it will ask if the fingerprint is correct. Click Yes and continue.

To remove the fingerprint in UNIX, go to the user’s home directory and enter the command:

cd .ssh

In that directory you’ll find a known_hosts file. Rename that and attempt the connection again.

If that does not clear the problem up, the host is probably configured to accept RSA key authentication, but TinyTERM or TERM is using a username and password instead. To disable RSA on the host, go to its /etc/ssh directory and edit the sshd_config file. Look for the following two lines:

RSAAuthentication yes
PubkeyAuthentication yes

Change “yes” to “no” on each line. The lines may also be commented out with the # character. If so, remove it from the beginning of the line when making the change. Restart the SSH daemon after making the change.

CR 662
CR 802, request for option to continue on failed host key