Brother Print Server Nc 4100h User Guide

							CHAPTER 13 TROUBLESHOOTING
If the print server and printer start up OK, but you intermittently have problems 
						

							CHAPTER 13 TROUBLESHOOTING
13-6
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:
It is always a good idea to try following in order to eliminate the possibility of setup
errors.
Turning off the printer and then again,
Deleting and recreating the print 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 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.
 If you used BRCONFIG, NCP or ccr 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 again (it may take up to two minutes for
the IP address to take effect).
3.
 Make sure that the TCP/IP protocol of the print server is enabled.
4.
 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.
5.
 If you used bootp, make sure that you started the bootp deamon 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.
6.
 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. 
						

							CHAPTER 13 TROUBLESHOOTING
13-7
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 printer.
if
:lp = /dev/null: \
then to
:lp = :\
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 printer, where
printer is the name of the local print queue.
4.
 If you are using an AT&T-based UNIX, make sure the printer is enabled
(enable printer, where printer is the name of the local print queue).
5.
 Make sure that the lpr/lpd remote line printer service are running on the host
computer (refer to your host computer documentation for information on
how to do this). 
						

							CHAPTER 13 TROUBLESHOOTING
13-8
6.
 If you are having trouble printing more than one job at a time, try increasing
the IP timeout using the SET IP TIMEOUT command or using BRAdmin.
7.
 If text or PCL jobs are run together, try setting the service (remote printer)
with EOT set to string number 2 (E). For example:
SET SERVICE BRN_xxxxxx_P1 EOT 2
NC-2000 series print servers use service names that begin with
BRO_xxxxxx_P1. The above line on a NC-2010h or a NC-2100h would be
SET SERVICE BRO_xxxxxx_P1 EOT 2
8.
 If PostScript jobs fail to print or are run together, try setting the service
(remote printer) with EOT set to string number 3 (control-D). For example:
SET SERVICE BRN_xxxxxx_P1 EOT 3
NC-2000 series print servers use service names that begin with
BRO_xxxxxx_P1. The above line on a NC-2010h or a NC-2100h would be
SET SERVICE BRO_xxxxxx_P1 EOT 3
9.
 If the lines of a text file are staggered, make sure that you have specified a
remote printer (rp) name of TEXT in your /etc/printcap file.
10.
 If you are using Sun Solaris V2.4 or earlier, there is a bug which causes long
print jobs to fail when using a print server. If you are having trouble printing
long jobs (over 1MB), add the line mx#0 to your etc/printcap file entry.
11.
 If you cannot print from DEC TCP/IP Service for VMS (UCX), make sure
that you have version 2.0B or later of this software, because earlier versions
will not work with Brother print servers. 
						

							CHAPTER 13 TROUBLESHOOTING
13-9
Windows NT/LAN Server (TCP/IP)
Troubleshooting
If you are having trouble printing with Windows NT or LAN Server, check the
following:
1.
 Make sure that TCP/IP and TCP/IP print service are installed and running on
the Windows NT system or the LAN Server file server.
2.
 If you are using DHCP and you have not created a reservation for the print
server, make sure that you enter the NetBIOS name of the print server in the
Name or address of server providing lpd box. 
						

							CHAPTER 13 TROUBLESHOOTING
13-10
Windows 95/98/Me Peer to Peer Print
(LPR) Troubleshooting
If you are having trouble printing on a Windows 95/98/Me Peer-to-Peer network
(LPR method), check the following:
1.
 Make sure that the Brother LPR Port driver is correctly installed and
configured according to the Windows 95/98/Me Peer-to-Peer chapters.
You may find that during the installation of BLP software, the screen that prompts
you for a Port name is not displayed. This may happen on some Windows 95/98/Me
computers. Press the ALT and TAB keys to make it appear. 
						

							CHAPTER 13 TROUBLESHOOTING
13-11
Windows 95/98/Me Peer-to-Peer (HP
JetAdmin compatible method)
Troubleshooting
If you are having trouble printing on a Windows 95/98/Me Peer-to-Peer network,
check the following (HP JetAdmin compatible method):
1.
 If the print server does not show up under JetAdmin on a Windows
95/98/Me Peer-to-Peer network, try removing all of the Windows 95/98/Me
network software from the Network Control panel and then reinstalling them
as follows:
·
 First install the IPX/SPX-Compatible Protocol (or the TCP/IP protocol
if you are using a later version of JetAdmin), the Client for Microsoft
Networks, and the network adapter card driver.
·
 Install the Latest HP JetAdmin software
·
 Restart the system, and then add the HP JetAdmin service. 
						

							CHAPTER 13 TROUBLESHOOTING
13-12
Windows 95/98/Me/NT 4.0 Peer-to-Peer
Print (NetBIOS) Troubleshooting
If you are having trouble printing on a Windows 95/98/Me/NT 4.0 (or later) Peer-to-
Peer network (NetBIOS), check the following:
1.
 Make sure that the Brother NetBIOS Port driver is securely installed and
configured according to the Windows 95/98/Me/NT 4.0 Peer-to-Peer
(NetBIOS) chapters. You may find that during the installation of the port
driver, the screen that prompts you for a Port name is not displayed. This
happens on some Windows 95/98/Me/NT 4.0 computers. Press the ALT and
TAB keys to make it appear.
2.
 Make sure that the print server is configured to be in the same workgroup or
domain as the rest of your computers. It may take several minutes for the
print server to appear in the network neighborhood. 
						

							CHAPTER 13 TROUBLESHOOTING
13-13
Brother Internet Print (TCP/IP)
Troubleshooting
1.
 The first step in troubleshooting is to make sure that you have a valid E-mail
connection on both the sending PC and the receiving print server. Try
sending an E-mail message from the PC to a user at the remote site who can
receive mail via the POP3 server. If this does not work, there may be an E-
mail configuration problem on the PC, on the local E-mail server, or on the
remote POP3 server. Double check to make sure that the E-mail parameters
that you configured on the PC and on the remote print server match those
that are configured on the E-mail servers.
2.
 If you can print small files OK but are having problems printing large files,
the problem may be in the e-mail system! Some E-mail systems have
difficulties printing large files. If the file does not reach its destination intact,
then the problem is with the E-mail system.
3.
 You can also enable the partial e-mail print facility on your client PC, this
will split the e-mail up into fragments which should then not overwhelm
your e-mail server. To do this, select the property dialog of the Brother
Internet Print Port. 
						

							CHAPTER 13 TROUBLESHOOTING
IPP not a n active p rotocol
ipp,  the
“Get More Info” option i n Windows 200 0 will not function. If yo u wish to use the