Like the 10022 Invalid Argument error, this message means TinyTERM is being blocked by a firewall. Error 10013 usually indicates that the tt.exe program is specifically blocked.

To get rid of the error, change the firewall configuration so that tt.exe is no longer blocked. Set it to be exempt or always allowed instead.

A TCP/IP connection creates a pseudo-tty device (ptty) on the fly at the host system. The numbers assigned to them are not stored, but are lost at disconnect. The specific ptty may change with each connection.

Some configurations may require that users login through specified ptty ports. SCO UNIX has a solution for this in the recon command. Similar commands may exist for other host operating systems, but they are not as well documented.

This error generally indicates a firewall is blocking TERM or TinyTERM from connecting via TCP/IP. To get rid of the error, configure the firewall to allow TERM or TinyTERM to connect without restrictions. The specifics will depend on how your firewall is configured.

CR 708, firewall handling improved in TinyTERM 4.50

This error comes up in TinyTERM version 4.20, usually when trying to connect again after logging off a network connection. If you wait long enough, you don’t get the error on connecting. It’s not a problem in other versions.

It’s actually tied to the Ribbon Bar. To fix the error, go to the View menu and make sure the Ribbon Bar option is checked. Once that’s on, you won’t see the error again.

CR 275, HP-UX
CR 283, fixed in TinyTERM 4.21

Any network connection requires a TCP port be open and available on the server. There is an excellent list of common TCP ports at www.iss.net.

If you are using a non-standard port in TERM, you can specify the correct port by adding to the address, after a colon. For example:

term -l telnet:192.168.0.1:1023

will cause TERM to use telnet to connect to port 1023, rather than using the default port of 23. TinyTERM for DOS can also be configured this way.

In TinyTERM for Windows, you will need to go into the advanced setup for the telnet, SSH or SSL/TLS protocol. That dialog box will include a port number that can be edited.

At this writing, no file transfer protocol has this capability. This includes FTP in the emulator, as well as the protocols available in the Century FTP Client or SecureFT. The NFS client and server likewise cannot be changed.

CR 235, Century FTP Client
CR 620, FTP in emulator
CR 828, SecureFT

A TCP/IP connection error usually includes a five-digit number that starts with 100 or 110; e.g., 10057. These errors always come from the operating system, not TERM or TinyTERM.

There is an excellent reference to the error numbers at sockets.com. Toward the bottom of the page is a list of all the errors in numeric order for quick reference. It’s an excellent way to troubleshoot TCP/IP socket errors.

This error means that a system somewhere in the connection sent a reset signal, which will disconnect TinyTERM or TERM. Any system from the PC to the server — and any router, firewall or gateway in between — can generate this error.

To find the source of the problem, you will need to run a packet capture utility such as Ethereal. That will show you which system is sending the reset signal. With that information you can correct the error on that system.

When connecting over the Internet with a telnet or SSH connection, occasionally temporary network drops happen. TinyTERM can normally recover from these if you don’t type while the network is down. However, since it’s hard to tell that the network connection was temporarily lost until you type something, you’ll normally notice the failure when TinyTERM appears to lock up.

It has not actually locked. Instead, it has lost the network connection it had to the server. In most cases the menus will work normally, and you can exit TinyTERM gracefully.

Some versions of TinyTERM do not handle the connections as well. In those cases, the only thing you can do is close TinyTERM from the Task Manager. Typing Ctrl-Alt-Delete will bring that up in any version of Windows.

CR 126, disconnect handling improved in TinyTERM 4.10.
CR 159, intermediary system disconnects

TinyTERM version 4 requires Winsock2 for TCP/IP connectivity. This is not installed by default in Windows 95. You will need to add two patches: DCOM95 and WS2Setup. We recommend you install these before installing TinyTERM.

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.