Tcp/Ip Troubleshooting; Unix Troubleshooting - Brother mfc8440 Service Manual
Hide thumbs
Also See for mfc8440:
- User manual (426 pages) ,
- Software user's manual (183 pages) ,
- Quick setup manual (52 pages)
Table of Contents
Advertisement
CHAPTER 6 TROUBLESHOOTING
10.3
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:
It is always a good idea to try the following in order to eliminate the possibility of setup errors.
• Turning off the machine and then on again,
• Deleting and recreating the print/fax server and creating a new print queue in order to
eliminate the possibility of setup errors.
(1) The problem may be the result of mismatched or duplicate IP address. Verify that the IP
address is correctly loaded into the print/fax 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).
(2) Make sure that the TCP/IP protocol of the print server is enabled.
(3) 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/fax server name matches the name in the /etc/hosts
file.
(4) 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.
(5) Also verify that host computer and the print/fax server are either on the same subnet,
otherwise that the router is properly configured to pass data between the two devices.
10.4
UNIX Troubleshooting
(1) 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.
(2) If you are using a Linux operating system, the X-Window Print tool program that is
included with Linux may not properly configure the etc/printcap file for lpd operation, then
you might also edit the etc/printcap file and change the following line in the entry for the
machine.
(3) If you are using a Berkeley-based UNIX, make sure that the daemon is started on
Berkeley based systems with the command lpc start machine, where machine is the
name of the local print queue.
(4) If you are using an AT&T-based UNIX, make sure the machine is enabled (enable
machine, where machine is the name of the local print queue).
(5) Make sure that the lpr/lpd remote line machine service are running on the host computer
(refer to your host computer documentation for information on how to do this).
(6) If text or PCL jobs are run together, try setting the service (remote machine) with EOT set
to string number 2 (<ESC>E). For example:
if
:lp = /dev/null: \
then to
:lp = :\
SET SERVICE BRN_xxxxxx_P1 EOT 2
6-58
Advertisement
Chapters
Table of Contents
Troubleshooting
