Table of Contents
Advertisement
Terminal Server - User and Administration Guide
Faulty terminal
Wrong port on
terminal
Faulty Server port
Cable too long
Electrical noise
Software
application error
120
Try a known working terminal on the Terminal Server port.
Many terminals have more than one port (i.e. AUX). Check
that the cable has been connected to the correct port .
Try a known working terminal on the suspect port. If
possible, attach a serial line monitor. If the area you are
working in is prone to electrical storms, it is possible that a
high voltage surge has been induced in the cable and
damaged the driver/receiver chips within the server.
The RS-232 specification states a maximum length of cable
proportional to the bps rate. A good rule of thumb is that a
19200 bps connection should not be used on cable lengths
in excess of 15m (50 ft). Also a 9600 bps signal operates
reliably up to a distance of approximately 30m (100 ft).
Cables of greater lengths may seem to work correctly but the
connection will be less reliable.
If your equipment (especially cables) is near any high voltage
equipment it may be picking up electrical noise which is
corrupting the data signals. Check the stats screen of the
Terminal Server (check Line Stats for malformed characters).
Ensure all cables are correctly screened and attempt to keep
them away from high voltage equipment.
If there are problems whenever a certain application is used
then the fault may lie with the software. Check the manuals
to ensure the application is configured correctly.
Note: Many fax packages will not work properly with
remote ports.
Advertisement
Table of Contents
