Using TinyTERM Plus Edition 4.04, how do you connect through a telnet firewall to an IBM host with TN5250 or TN3270 terminal emulation?

Configure a sessions using the TTY terminal type and a telnet connection to connect to the firewall as follows:

• Connection host: firewall name or IP address
• Connection Type: telnet
• Terminal Emulation: TTY
• Telnet Terminal Type: (depends on IBM emulation required)
  • 3270
    • IBM-3278-2
    • IBM-3278-3
    • IBM-3278-4
    • IBM-3278-5
  • 5250
    • IBM-3179-2
    • IBM3477-FC
• Save the session.
• Telnet to the firewall using this configuration. When the firewall prompts for the host, enter the hostname or IP address of the destination host.
• Depending on your firewall, you may have to hit the Enter key once to display the initial host screen.

NOTE 1: TinyTERM senses telnet binary mode to know when to switch emulations from TTY to one of the IBM emulations. The IBM terminal emulation desired is specified by the Telnet Terminal Type configuration.

NOTE 2: To preserve the initial firewall connection configuration do not save the session after the IBM host connection is made. TinyTERM changes your session properties when the IBM connection is made.

After installing third-party software that uses TCP/IP, TinyTERM may fail to connect on Windows 95. This happens when the new software replaces Winsock2 with an older version. This is not an issue on newer versions of Windows.

To fix this, reinstall Winsock2 on Windows 95. You can download the install here.

If you see strange characters after connecting, and the host is prompting multiple times for login, you probably have a setting wrong. This usually happens when TinyTERM is set up to login automatically on connection, but the username and password aren’t set.

You can do one of two things. In the Login settings, you can either turn off the “login at connect” option, or you can set the username and password for the automatic login. Either way, the extraneous characters and multiple login prompts should disappear.

Starting TinyTERM Plus Edition 4.03 on Windows 98 or NT , you may receive the error “Get Capture Failed,” followed by DLL errors. This usually indicates you do not have TCP/IP installed. To correct the problem, you will need to do the following:

1. Add TCP/IP to Windows.
2. Reboot your PC.
3. Uninstall TinyTERM, then reboot.
4. Reinstall TinyTERM. When the install completes, reboot your PC, whether or not you are prompted to do so.

Using TinyTERM version 4.02, when you try to remap or edit a key using the keyboard mapper, you receive errors. After remapping a key, the new settings aren’t saved.

To resolve this problem, you will need to install the patch files found in this directory. Save them to a temporary directory on your PC. In the directory C:\Program Files\Century\TinyTERM, locate the files CenTE.ocx, tt.exe and TT.ini. Rename each file as a backup.

Copy the patch files into the same directory. The next time you start TinyTERM, the patches will be in effect. You won’t see the keyboard mapping errors any more.

When setting up a modem connection in TERM or TinyTERM, do not use any country or area code options offered by the operating system. Instead, enter the entire phone number just as you would dial it from a standard telephone. For example, if it’s long distance in the United States, include the leading 1 and area code.

You can use dashes to separate the numbers for readability, but they are not required. To add a two-second pause, such as you might need when dialing 9 to get an outside number, enter a comma in the phone number:

9,1-801-268-3088

CR 89, country code usage added to TinyTERM 4.20

Using TinyTERM Plus Edition version 4.02 or 4.03, when you set the number of columns to 132 and save the session, TinyTERM still starts in 80-column mode. To resolve this you can create a one-line script. Enter the command:

te.numcolumns=132;

Configure the script to run as the “Post Session Start” script. This will force the correct number of columns.

Using self-created floppies of the TinyTERM 3.3 install on Windows 3.1, you may be unable to setup TCP/IP afterward. This generally happens when the TCP/IP or network utilities options were deselected during the install. You will need to uninstall the current install, reboot the system and reinstall. Make sure you select both TCP/IP and network utilities on the reinstall.

This error does not come from the terminal emulator. Instead, it comes from the server. It means all the available TCP ports are in use. It may also point to a network problem on the host system. Contact support for the host system for more information.

When you connect via direct serial cable, you may see incorrect, but readable, text instead of a login prompt. This generally happens when a process is still running on the serial port, which is usually caused by closing the emulator before logging out. The cause can be human error, power loss or something else.

To fix the problem, if possible get to a system prompt and log out. Otherwise, you’ll need to kill the process from the server itself, rather than from your workstation. Once the process has ended, you’ll see a login prompt the next time you connect.