Sometimes users will close TinyTERM when they’re done, instead of properly logging out of the host first. This can use up concurrent server licenses, or even corrupt the host database. For TinyTERM version 4.10 or higher, you can prevent this.

In the TinyTERM directory, you’ll find a sample script named outfirst.cs. It will work for network or modem connections, but not direct serial connections. RS232 connections actually connect only to the serial port in the PC, which then gets information from the line connecting it to the host. Logging out of the host does not end a serial connection the way it does over a network or modem.

To use outfirst.cs, open TinyTERM on the user’s PC. Go to the Edit menu and select Preferences. Next to the Application startup script line you’ll see a Browse button. Click on that and use the resulting Windows Find dialog to locate the outfirst.cs script. Select that script and click the Open button to make it the application startup script.

This will take you back to the Preferences dialog. Click the Apply and OK buttons. Go to TinyTERM’s File menu and select Save Session. The next time TinyTERM is started, a warning message will pop up whenever a user tries to close TinyTERM before logging out. TinyTERM will stay open and connected when the error is closed.

For screen-by-screen help with this configuration, please view our screencast on this topic.

There is one way around the outfirst.cs. If you shut down Windows, it bypasses the shutdown blocks running in TinyTERM.

CR 554

TinyTERM Plus 4.10 and higher include the SSH connection type. TinyTERM 4.1x includes only SSH1. Version 4.20 and higher include SSH2 as well. An option to specify SSH2 only at connection was added in TinyTERM Plus 4.31. Public key authentication was added in TinyTERM Plus 4.42.

For help in configuring SSH connections, you can watch screencasts on configuring password authentication and configuring RSA authentication.

In TinyTERM 4.10, the SSH option is grayed out by default. This is due to export restrictions at the time Century Software, Inc., first released the product. You can add SSH by downloading and applying this patch. Download it to a temporary directory, then run it after TinyTERM Plus Edition is installed. It will also work for TinyTERM Thin Client Edition or TinyTERM Web Server Edition version 4.10.

If you have version 4.11 or higher and SSH is grayed out, you have TinyTERM, not TinyTERM Plus. TinyTERM does not include SSH, though TinyTERM Thin Client and TinyTERM Web Server do.

SSH2 is also available in TERM for SCO UNIX and TERM for Linux version 6.28 as a command-line option. The basic command is:

term -lssh:username@host.or.IP

Replace “username” with an actual username, and “host.or.IP” with the correct hostname or IP address.

Century Software, Inc., does not provide SSH daemons for host systems. Check sites such as www.openssh.com for daemons and source code.

CR 37, SSH
CR 144, SSH2
CR 205, RSA key authentication
CR 297, TERM 6.28
CR 481, SSH2 only

Some FTP servers will show an empty directory in the Century FTP Client or SecureFT. This happens when the server uses a different directory item structure than the client’s default. The following steps will change the default in the Century FTP Client:

1. Open the Century FTP Client. It displays the configuration dialog automatically.
2. Click the View/Sort tab.
3. Set the Directory Item Structure value by clicking the Set Default button.
4. Edit the Directory Item Structure value for the required format.

The steps for SecureFT are (also available as a screencast):

1. Go to the Edit menu and select Setup.
2. Click the Directory Structure tab.
3. Click the item under Active Items you want to change.
4. Click the Push button to move it to the Inactive Items. Or use the up and down arrows on the left to change the item’s position in the list.

The required format may be found by connecting to the FTP server using a command-line client, such as the one included in Windows. After connecting, type “dir” at the prompt for a directory item listing. The default format used by the graphical FTP client is:

-rwxrw-rw- 1 owner group 32 May 19 21:35 file.txt

This corresponds to Directory Item Structure:

ATTRIBUTE UNKNOWN USER GROUP SIZE MON DATE TIME FILENAME

Compare the listing on the FTP server with the listing above and change the order as needed, removing any directory items not displayed. The most common change needed is to remove the GROUP item.

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 error means the IP address of the server you are attempting to connect to is unreachable from your computer. It’s almost always due to incorrect network settings on the PC. To check your network settings, do the following:

Windows 95, Windows 98, Windows Me

1. Click Start->Run
2. Type “winipcfg” in the Open: box and then click OK

Windows NT, Windows 2000, Windows XP

1. Click Start->Programs->Accessories->Command Prompt
2. At the prompt, type “ipconfig” and press Enter

Verify that these settings are correct. If they are incorrect, contact your network administrator for assistance in properly configuring your computer.

If these settings are correct, then it is possible that your server may be down, or you may be experiencing some other problem with your network. You should contact your network administrator for assistance in this situation also.

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

This error indicates that a timeout occurred before a connection could be made. There are several different situations in which this error can occur.

First, you will need to verify that you have entered the correct IP address or hostname into TinyTERM.

Once you have verified that, you will need to test the network connectivity between your PC and the server. You can do this by using the Windows utilities ping and telnet. Both utilities use the Windows command prompt.

To open a command prompt, go to Start | Programs | Accessories. The prompt will be listed as either “Command Prompt” or “MS-DOS Prompt.”

Once you have the command prompt, ping your server. At the prompt type:

ping address

replacing “address” with the hostname or IP address of the system you’re connecting to; for example, “ping 192.168.0.1”.

If you receive multiple timeout messages, this means that your PC cannot locate the server. Contact your system administrator for help with the network setup.

If your server replies, test the connection with Windows telnet. At the prompt type “telnet address” and hit Enter; for example, “telnet 192.168.0.1”.

If you receive an error message that reads “Connection Failed”, this means the Windows telnet program is experiencing the same problem as TinyTERM. This also indicates that the problem is not related to the TinyTERM software, but rather to a connectivity problem with either the PC or the server. You will need to contact your network administrator for assistance.

If telnet connects successfully, this error may be due to the way TinyTERM handles IP addresses and hostnames. In many cases, using a hostname in place of an IP address or vice versa will get TinyTERM to connect. Check with your system administrator to get the hostname or IP address for the server, whichever you’re not currently using in TinyTERM.

If there is no hostname assigned to the server, you can edit your PC’s hosts file to give it one. Instructions for this are available here.

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

Windows 95

There is one special case regarding Windows 95 and Internet Explorer 3.0. If you configure and used IE’s email, TinyTERM will give the 10060 error. To resolve this, you can either delete IE’s email, or you can upgrade to Internet Explorer 4.01 or higher.

CR 607

If TinyTERM doesn’t open when you try to start it, but just puts a button on the Windows taskbar, it means the window position information has gotten corrupted. To fix that, right-click the button and select Maximize from the pop-up menu. TinyTERM will open full screen. From the File menu, select Save Session. This will usually fix the problem.

If it does not, you’ll need to edit the configuration file you’re using. Close TinyTERM and edit the .tpx file being used in Notepad. Search for the following two lines, which will be one right after the other:

xwindow=
ywindow=

They’ll both be set to very high numbers, or they’ll be negative numbers. Change each to 100:

xwindow=100
ywindow=100

Save the changes and close Notepad. The next time you start TinyTERM, it will open in a normal window. It may be too small, so resize it if you need to. Then save the session to make the changes permanent.

If your version of TinyTERM is old enough to use a configuration file with the .tap extension, the correct line to adjust in that file is:

window=

Change the first four numbers in that line     they’re separated by commas     to 100. The next time you start TinyTERM, resize the window to your needs.

Watch a screencast demonstrating this process.