202
Chapter 10 Unix Troubleshooting Tips
Unix Troubleshooting Tips
This section provides information on possible solutions to some standard
configuration errors. If you require technical support, please have the
following information (or as much as possible) when you call:
1. What level of software are you running?
2. What type of attachment do you have?
3. What is your host operating system?
4. Give a detailed description of the problem.
5. How often, and when, does the problem occur?
6. Give a detailed description of your network and the components attached.
Please follow these tips to determine what the problem may be with your NIC
configuration.
Nothing Prints
• Can you ping the NIC from your Unix station? If not, please refer to
Chapter 7, “TCP/IP Configuration” for information.
• Is the NIC able to communicate with the attached printer? To test this,
you can:
1.
telnet to the print server (e.g., telnet 192.75.11.9) and log
in as
root.
2. Enter the command start fox prn .
3. Execute
stop prn right after starting the test.
This test will send the same text line over and over to the attached printer.
• Is the job getting stuck in the Unix host queue? If so, check that the printer
is online. If it is, there is a configuration error on the Unix station so
creating a new print setup may be needed.
• Is the control panel showing any activity to indicate it is receiving data? If
so, but there is nothing printing, check to see if a manual form feed is
needed. Also, ensure that the printer can support the type of job coming
through.
• Do all jobs fail or just certain ones? For example, is it possible that jobs
from a certain application are the only ones to fail? If so, check the type of
data it sends to make sure it matches the printer emulation. Check the
application printer configuration for mistakes.
• If you are using System V, was the spooler restarted?