Chapter 5
Unix Troubleshooting Tips
150
Nothing Prints
•
Can you
ping
the NIC from your Unix station? If not, please
refer to “NIC Cannot Be Found On The Network” shown above.
•
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.
4.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 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?
Summary of Contents for Network Interface Card
Page 1: ......
Page 3: ...Network Interface Card User s Manual...
Page 6: ......
Page 32: ...Chapter 1 Printronix Customer Support Center 32...
Page 83: ......
Page 86: ......
Page 96: ...Chapter 4...
Page 102: ......
Page 144: ......
Page 202: ...Chapter 7 Troubleshooting 10 100Base T 202...
Page 210: ...Chapter 8 OS 2 Workstation Configuration 210...
Page 228: ...Chapter 9 Handling z OS Connectivity Problems 228...
Page 292: ...Chapter 12 Configuration Screens 292...
Page 300: ...Chapter 13 Font Identifier FONT Help 300...
Page 356: ...Chapter 16 Periodic Ping 356...
Page 362: ...362...
Page 376: ...Index 376...
Page 377: ......