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.

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.

TinyTERM is compatible with DSL and cable modems; however, they are very different from traditional analog modems. DSL and cable modems provide a direct connection to the Internet over existing cable or phone lines. They do not have the ability to dial a phone number.

In other words, you cannot use the Modem connection type within TERM or TinyTERM to dial a DSL or cable modem. You can only use the connection types that run over TCP/IP, such as SSH, Telnet, and Rlogin. If your connection requires that you dial a phone number to connect to your server, then you must have a traditional analog modem installed on your computer.

TinyTERM version 4.x requires Winsock2 to connect via TCP/IP. This is standard in Windows 98 or higher.

Windows 95 does have the ability to use Winsock1 only. You must update to Winsock2 to use TinyTERM version 4. In fact, TinyTERM 4.0x won’t install unless Winsock2 is included, even if you plan to use a serial or modem connection.

Older versions of TinyTERM or TERM for Windows can use Winsock1 or Winsock2 interchangeably.

CR 55, Winsock2 requirement removed for non-TCP/IP connections

Using TinyTERM 3.3 on Windows 95, when connecting you may get “Error (620) Reserve sockets in use.” This indicates a TCP/IP problem. To fix it, delete TCP/IP from the network properties, reboot the PC and then reinstall TCP/IP.

Using TERM Professional 3.3 on Windows 95, if you shut down the PC, it immediately reboots. If Century NFS is removed, the machine shuts down properly.

This is usually caused by a load order issue between NFS and TCP/IP. To clear it, remove NFS from the system, then remove TCP/IP. Reinstall NFS before adding TCP/IP back in.

You may see sporadic Winsock errors in TinyTERM when connecting to an Ishare modem server. This happens when the Ishare modem server conflicts with the TCP/IP settings for the local network. You will need to redirect Ishare to look at the modem server only, and redirect the local network to look at the network configuration only. This may require a hosts file on the PC.

Using TinyTERM 3.2 on Windows 3.1, Netscape will not load pages if the Marathon Winsock.dll is in place. However, using Netscape’s Winsock.dll causes TinyTERM to dial the modem, rather than connecting to an ISP.

To bypass this, use the Century Internet Dialer to connect to the ISP before starting Netscape or TinyTERM. This will allow the use of Netscape’s Winsock.dll, while TinyTERM will still recognize the ISP connection.

TinyTERM Plus 3.2 comes with a Marathon TCP/IP stack for Windows 3.1. If you want to install without it, edit the PC’s AUTOEXEC.BAT and CONFIG.SYS files.

In the AUTOEXEC.BAT, REM out everything except ECHO, PROMPT and PATH commands. In the CONFIG.SYS, REM out everything except FILES, BUFFER, HIMEM.SYS and EMM386.EXE.

Restart your PC after this. When you install TinyTERM, you will be able to bypass the Marathon portion.

This error comes up when installing TinyTERM 3.2 on Windows 3.1. It’s caused by one of two things:

1. Multiple Winsocks are installed on the PC. Remove them and reinstall only one.
2. No Winsock is installed on the PC. Install one before installing TinyTERM.