Table of Contents
Advertisement
Printer Problems
You can check some of the same problem notes in the terminal section because most are
applicable to printers. The main problem is with cabling.
Terminal Server User Guide
Printer Problems
Problem
Action required
Testing the port
If you experience printer problems, it's a good idea to temporarily
connect a terminal in place of the printer so you can ensure some of
the basic functions are working correctly. Simply telnet into the
communications server port:
telnet elroy 10006 (port 6 on unit elroy)
If the Telnet session will not connect, check the network and if you are
using any of the RS-232 flow control signals, ensure they are
connected correctly. If the telnet session still refuses to operate, re-
configure the port for normal terminal operation and trouble-shoot
again from this level.
Another method is the use the test command from the CLI. This
sends a continuous test pattern out to the printer.
Example for port 6 (press to halt):
local> test port 6 count 0
If there is no printout, check the cable or the printer.
Flow control problems
If characters disappear from the printout it may be due to a flow
control problem, therefore check that the flow control is set to be the
same at both ends of the cable and re-try. Alternatively, the host
software may be incorrectly configured. If you are using ioland, set
the debug level to a high value so that the log file will contain as much
information as possible.
Configuration wrong
The first method to test this is to check the Statistics - Users Status
screen. This screen should show next to the port number, the printer
name (if the administrator has added it) and then the diagnostic
'Waiting for incoming connection'. If the diagnostic is something else,
such as 'Connections Menu' then the port is not correctly set up and
needs rechecking. Be sure to kill the port after changing its
configuration.
Page 178
Advertisement
Table of Contents
