Printer Errors When Printing Or No Output; Tcp/Ip Access Problem - Printronix PrintNet P8000 Line User Manual

Appendix A
Windows Troubleshooting Tips

Printer Errors when Printing or No Output

•
Is there a large job currently printing which is taking up all of the
printer resources? Usually when printing from Windows 95/98
stations, a busy printer can cause Windows to display a printer
error message. This is because it demands immediate printer
attention rather than holding the data until the printer is ready
again. The best way around this is to use a central spooling
station like an NT server.
•
Have you tried restarting the spooler under "Control
Panel:Services"? Sometimes this is needed to get printing
started.
NOTE: As a last resort, you may want to reboot the Windows

TCP/IP Access Problem

If you can ping the printer from a workstation, but you cannot Web
browse, Telnet, or print to the printer through the PrintNet, there
may be an incorrect entry in the TCP access list. In order for this
workstation to use the PrintNet interface in this case, one of two
things must happen.
•
The TCP list must have an entry added to grant access to this
workstation, or
•
All entries must be deleted from the TCP list to grant all
workstations/hosts access to the above TCP services.
To view the current access list, use the printer control panel to
access the configuration menu (see the User's Manual for
configuration menu information). From the DIAGNOSTICS/Printer
Tests menu choose the Ethernet Test Page. When the page prints,
look under the "TCP Sockets" section for the TCP access list
entries.
212
station. Sometimes this is the only option to completely
clear this situation. The PrintNet usually has nothing to do
with this problem.