Tcp/Ip Troubleshooting - Brother NC-series User Manual

USER'S GUIDE

TCP/IP Troubleshooting

If you are using TCP/IP and cannot print to the print server and you have
checked the hardware and network as described in the previous steps, then
check the following (note that it is always a good idea to try creating a
another print queue to eliminate the possibility of setup errors):
1. The problem may be the result of mismatched or duplicate IP
addresses. Verify that the IP address is correctly loaded into the print
server (via the configuration page or through the front panel of the
printer (if your printed has an LCD panel and you are using an
internal print server). Make sure that no other nodes on the network
have this address (DUPLICATE IP ADDRESSES ARE THE
BIGGEST CAUSE OF TCP/IP PRINTING PROBLEMS).
1. If you used NCP, BRCONFIG, or ccr to enter the IP address, make
sure that you exited the remote console properly with a CTRL-D 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).
2. Make sure that the TCP/IP protocol is enabled.
4. If you used rarp, make sure that you started the rarp daemon using the
rarpd, rarpd -a, in.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.
5. If you used bootp, make sure that bootp is enabled (i.e., the "#" is
removed from the bootp entry) in the /etc/bootptab file is
correctly configured.
6. Also verify that the host computer and the print server are either on the
same subnet (for example, Brother print servers have a default subnet
mask of 255.255.255.0 and the host must have the same subnet mask)
or that the router is properly configured to pass data between the two
devices.
7. Make sure that the /etc/printcap file (if applicable) is typed in
correctly. In particular, look for missing ":" and "\" characters, because
a small error anywhere in the file can have major consequences. Also
check the /usr/spool directory to make sure that you have created
a valid spool directory.
8. If you are using a Berkeley-based UNIX, make sure that the daemon is
started on Berkeley based systems with the command lpc start printer,
where printer is the name of the local print queue.
12-6