FAQs & Troubleshooting
I am using TCP/IP and cannot print to the print server. What should I do?
If you are using TCP/IP and cannot print to the print server and you have checked the hardware and network, then check the following:
The problem may be the result of mismatched or duplicate IP address. Verify that the IP address is correctly loaded into the print server (via the configuration page. Make sure that no other nodes on the network have this address (DUPLICATE IP ADDRESS ARE THE BIGGEST CAUSE OF TCP/IP PRINTING PROBLEMS).
If you used BRCONFIG or NCP to enter the IP address, make sure that you exited the remote console properly with a CTRL-D or EXIT and that you turned the printer off and then on again (it may take up to two minutes for the IP address to take effect).
Make sure that the TCP/IP protocol of the print server is enabled.
If you used rarp, make sure that you started the rarp daemon on any workstation using the rarpd, rarpd-a, or equivalent command. Verify that the /etc/ethers file contains the correct Ethernet address and that the print server name matches the name in the /etc/hosts file.
If you used bootp, make sure that you started the bootp daemon on any UNIX® workstation and bootp is enabled (i.e., the "#" is removed from the bootp entry) in the /etc/bootptab file is correctly configured.
Also verify that host computer and the print server are either on the same subnet, otherwise that the router is properly configured to pass data between the two devices.