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.

Port forwarding, or tunneling, is a way to forward normally non-secure TCP/IP traffic through an SSH connection. You would normally need it any time you have traffic over a public network, such as the Internet, that you don’t want anyone to snoop on. More information is available elsewhere on our website.

To set it up in TinyTERM version 4.3 or higher, do the following:

1. Open a new session in TinyTERM.
2. Click on the Edit menu and select Session Properties.
3. Change the connection type to SSH and click the Apply button.
4. Click on the Port Forwarding tab.
5. Enter a name for the connection.
6. Choose whether to forward a local TCP/IP port to a remote host (Local to remote forwarding), or forward a remote port to the local PC (Remote to local forwarding).
7. Enter the local port that will forward or receive forwarding.
8. If the SSH server is not the remote system, check the “Remote host is different machine from SSH server machine” box and enter the hostname or IP address of the SSH server.
9. Enter the TCP/IP port for the remote host.
10. Enter the name of the local PC application to run, or click the Browse button to select one. Enter any command-line parameters for the local PC application.
11. Click the Add button to add the connection to the list.

The next time you open this TinyTERM session, the port forwarding you set up will be active. Sample application setups are available here.

CR 385, added in TinyTERM Plus 4.30

SSH (Secure SHell) is a replacement for telnet and rlogin. It encrypts all data transmissions between the terminal and the host, rather than sending them in plain text.

When connecting to a host over the Internet, the data transmissions are available to anyone with the technical knowhow to tap into them. Telnet and rlogin send data in plain text, so they can easily be read. This could compromise proprietary or confidential information.

With SSH, the data transmissions are encrypted. Even if someone manages to hack into your connection, the information is in a format readable only by your PC and the remote host. This helps protect your valuable information from unauthorized access.

TinyTERM Plus, TinyTERM Thin Client and TinyTERM Web Server all include SSH from versions 4.10 on. (TinyTERM Thin Client was combined with TinyTERM Plus in version 4.40.) TERM for UNIX version 6.28 also includes SSH.

You will also need an SSH daemon on your host computer. You can download this program from http://www.openssh.org/ at no cost.

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

When TERM for UNIX displays this error, test cu or uucp against the same port. If either of those works, there may be a lockfile on the port. To bypass that, enter the command:

term -i

If that fails, list the port explicitly in the command line:

term -l/dev/ttyS0

Replace ttyS0 with the actual tty port. You can also combine this with the -i command-line parameter.

If everything above checks out, look at the number you’re dialing with the CALL command. The # character will cause the “unknown transport” error. This is problematic, particularly if your phone system requires you to dial something like #8 to get an outside line.

CR 412, CALL

Using TERM for UNIX on a tty port, it may fail even though cu can see the port. When this happens, first verify the port permissions are 666 (-rw-rw-rw-). If that’s correct, launch TERM with the -i parameter:

term -i -l/dev/tty04

This will ignore any lockfiles on the tty port. Please be aware that if another application is using the port, it will be interrupted when you do this.

This error comes up when using TinyTERM or TERM for DOS on a PC with no networking installed. You will need to configure the connection again, as it’s been changed to try to use a network.

You may run into a situation where transparent printing works for a few pages of text, then gives a print error. After that the job may fail, or it may print one line per page.This is a flow control issue. Disable flow control on both the PC and the server port. Printing should work properly after that.

This was seen using TERM 6.2.5 on an AIX 4.2 system, which had been upgraded from AIX 3. TERM randomly locked three different ports, requiring a system shutdown to clear them.

It turned out that TERM 6.2.4 was still on the system when TERM 6.2.5 was installed. Removing all versions of TERM and reinstalling only version 6.2.5 fixed the problem.

This error means no modem is installed in Windows. If the modem does appear to be installed, remove it and reinstall it.