Brother Print Server Nc 8100h User Guide

							CHAPTER 13 TROUBLESHOOTING 
13-5 
Intermittent Problems 
 
If the Print / Fax server and printer start up OK, but you 
intermittently have problems printing, check the following: 
 
1.  If you can print small jobs but large graphics jobs are distorted or 
incomplete, make sure that you have adequate memory in your printer 
and the latest printer driver installed on your computer. The latest 
Brother printer drivers can be downloaded from 
http://solutions.brother.com. 
 
2.  Check the individual protocol troubleshooting sections in this chapter for 
additional causes of intermittent printer problems.  
						

							CHAPTER 13 TROUBLESHOOTING 
13-6 
TCP/IP Troubleshooting 
 
If you are using TCP/IP and cannot print to the Print / Fax 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 / 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.  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 / Fax 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 
/ Fax server name matches the name in the /etc/hosts file. 
 
5.  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. 
 
6.  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.  
						

							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 
 
8.  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. 
 
9.  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 / Fax server. If you are having 
trouble printing long jobs (over 1MB), add the line mx#0 to your 
etc/printcap file entry. 
 
10.  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 / Fax 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 / Fax server, make sure that you enter the NetBIOS name of the 
Print / Fax server in the Name or address of server providing lpd box. 
 
 
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 chapter 7. 
 
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-10 
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 / Fax 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. 
 
 
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) chapter 7. 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 / Fax 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 / Fax server to appear in the network neighborhood.   
						

							CHAPTER 13 TROUBLESHOOTING 
13-11 
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 / Fax 
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 / Fax 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 
13-12 
Windows® 95/98/Me/2000/XP FTP/IPP 
Troubleshooting 
 
 
Want to use a different Port number other than 631 
If you are using Port 631 for IPP printing, you may find that your 
firewall may not let the print data through. If this is the case, use a 
different port number (port 80), or configure your Firewall to allow 
Port 631 data through. 
 
To send a print job using IPP to a printer using Port 80 (the standard 
HTTP port) enter the following when configuring your Windows
® 
2000/XP system. 
 
http://ip_address/ipp 
 
Get More Info option in Windows
® 2000/XP not working 
If you are using a URL of: 
 
http://ip_address:631
 or 
http://ip_address:631/ipp
, the “Get More Info” option 
in Windows® 2000 will not function. If you wish to use the “Get 
More Info” option use the following URL: 
 
http://ip_address  
 
This will then force Windows
® 2000 to use Port 80 to communicate 
with the Brother Print / Fax server. 
 
Windows
® 95/98/Me clients not able to get the driver from a 
Windows® 2000/XP  system. 
 
You must be using version 4.0 or later of Internet Explorer and the 
“Microsoft Internet Print Services” software must be installed on 
your client computers.  
  
						

							CHAPTER 13 TROUBLESHOOTING 
13-13 
Novell NetWare Troubleshooting 
 
If you cannot print from NetWare and you have checked the 
hardware and network as described in the previous steps, first verify 
that the Brother Print / Fax server is attached to the server queue by 
going to PCONSOLE, selecting PRINT QUEUE INFORMATION, 
and then CURRENTLY ATTACHED SERVERS. If the Print / Fax 
server does not appear in the list of attached servers, then check the 
following: 
 
It is always a good idea to try followings in order to eliminate the 
possibility of setup errors 
Turning off the printer and then on again to force to rescan the 
Netware queue. 
Deleting and recreating the Print / Fax server and creating a new 
print queue in order to eliminate the possibility of setup errors. 
 
 
1.  If you changed the login password, you must change the password in 
both the Brother Print / Fax server (using the SET NETWARE 
PASSWORD command if you are using the BRConfig software) or by 
using a web browser or the BRAdmin application and in the file server 
(using the PCONSOLE Print / Fax server Information Change Password 
command). 
 
2.  If you created the print queue using PCONSOLE and instead of 
BRAdmin, make sure that you have enabled at least one NetWare file 
server using the SET NETWARE SERVER servername ENABLED 
command. 
 
3.  Have you exceeded your NetWare user limit? 
 
4.  Make sure that the Print / Fax server name you used in PCONSOLE 
exactly matches the name that is configured in the Print / Fax server, and 
make sure it is defined as a Queue Server for the print queue. 
 
5.  If you are running both 802.3 and Ethernet II frames on different file 
servers on your network, there is a possibility that the Print / Fax server 
may not make a connection to the desired file server. Try forcing the 
frame type to the desired one using the SET NETWARE FRAME 
command from the Print / Fax server remote console or using BRAdmin. 
 
6.  If you are using DOS CAPTURE statement and losing portions of your 
print job, try setting the TIMEOUT parameter in your CAPTURE 
statement to a higher value (at least 50 seconds for Windows
®). 
  
						

							CHAPTER 13 TROUBLESHOOTING 
13-14 
AppleTalk Troubleshooting 
 
If you cannot print from an AppleTalk for Macintosh computer and 
you have checked the hardware and network as described in the 
previous steps, then check the following: 
 
1.  Make sure that you are running Phase 2 AppleTalk and that you have 
selected the correct network interface from the AppleTalk Control Panel 
on the Macintosh. 
 
2.  Make sure that the AppleTalk protocol of the Print / Fax server is 
enabled. 
 
3.  Verify that you have selected the correct AppleTalk zone. Because the 
Print / Fax server gets its zone information from router broadcasts, it 
may not be in the zone you expect, and will therefore not show up in the 
Chooser. If this is the case, you may need to force the zone name using  
a web browser or the SET APPLETALK ZONE command from 
TELNET.