Brother Print Server Nc 4100h User Guide

							CHAPTER 13 TROUBLESHOOTING
13-15
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 server is attached
to the server queue by going to PCONSOLE, selecting PRINT QUEUE
INFORMATION, and then CURRENTLY ATTACHED SERVERS. If the print
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 server and creating a new print queue in order
to eliminate the possibility of setup errors. 
						

							CHAPTER 13 TROUBLESHOOTING
13-16
1.
 If you changed the login password, you must change the password in both
the Brother print server (using the SET NETWARE PASSWORD command
if you are using the BRConfig software) or by using a web browser or the
BRAdmin utility and in the file server (using the PCONSOLE Print 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 server name you used in PCONSOLE exactly
matches the name that is configured in the print 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 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
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-17
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 Network Control Panel on
the Macintosh.
2.
 Make sure that the AppleTalk protocol of the print server is enabled.
3.
 If you have a large network, make sure that you have the Laser Writer V8.xx
or equivalent driver, since earlier versions may cause PostScript errors. Also,
verify that you get the correct printer information when you select Printer
Info from the Setup button in the Chooser.
4.
 Make sure that you have selected the correct Printer Description File (PPD)
from the Chooser (otherwise PostScript errors may result)
5.
 Verify that you have selected the correct AppleTalk zone. Because the print
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 BRAdmin, a web browser
or the SET APPLETALK ZONE command from TELNET. BRAdmin.
6.
 Verify that the Laser Prep versions on all Macintosh computers that need to
print to the print server are the same. 
						

							CHAPTER 13 TROUBLESHOOTING
13-18
DLC/LLC Troubleshooting
If you are having trouble printing with DLC/LLC, check the following:
1.
 Make sure that the DLC/LLC protocol is enabled using either BRAdmin, a
web browser or TELNET.
2.
 Make sure that the MAC address of the Windows setting is as same as the
print configuration page result. 
						

							CHAPTER 13 TROUBLESHOOTING
13-19
LAT Troubleshooting
If you cannot print from a VMS system 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 new queue with a different LAT port to reduce
the possibility of setup errors):
1.
 If the queue pauses when you try to print, check that the print server node
name and port name (or service name) agree with the names defined for the
VMS print queue in LATCP or for ULTRIX print queue in the /etc/printcap
file (ts parameter) and lcp -s command. The names MUST EXACTLY agree
in order for printing to work.
2.
 Make sure LAT is enabled for outgoing connections. For VMS, enter
LATCP and type SHOW NODE at the Latcp> prompt. The display should
show Outgoing Connections Enabled. If it does not, you should type SET
NODE/CONNECTIONS=BOTH. If you are using ULTRIX, make sure that
you have started LAT with the lcp -s command and that you have enabled
host-initiated connections with the lcp -h command.
3.
 Make sure that there are no duplicate LAT node names or LAT port
numbers. Try changing the node name to a different name and/or creating a
different LAT port to fix the problem. Also avoid having multiple print
queues that use the same LAT port.
4.
 If you are running ULTRIX, make sure that the /etc/printcap file 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.
5.
 If you are running ULTRIX, check your tty device to make sure that :
·
 The tty is a valid LAT tty (execute the command file /dev/tty* | grep
LAT and observe if the device has a 39 in its description).
·
 The device is in the /etc/ttys file and in the /dev directory.
·
 The same tty number was entered throughout the configuration process.
6.
 Intermittent random queue pauses can be caused if the VMS LAT port is not
set up as spooled device. Type SHOW DEVICE LTAxxx from the VMS
console; if the device is not spooled, type SET DEVICE/SPOOL LTAxxx
command. (One exception:  PATHWORKS for MACINTOSH queues
should not be set up with the LTA device set as spooled). 
						

							CHAPTER 13 TROUBLESHOOTING
13-20
7.
 Make sure that PROCESSOR=LATSYM is enabled on your VMS print
queue if you get any of the following symptoms:
·
 The queue pauses when you power off the print server for no apparent
reason.
·
 The print server generates excessive LAT traffic on the network
·
 Only one host computer can access the print server, others are locked out.
8.
 If the VMS LAT symbiont abruptly terminates and shuts down one or more
queues, the problem may be the result of the inability of the LAT symbiont
to handle the load (particularly if you are printing heavy graphics). Try
creating multiple LAT processors (copy the LATSYM.EXE file) and
splitting the load among these processors.
9.
 If your VMS graphics printouts are distorted, make sure that you have the
LTA port set for PASSALL, PASTHRU, and TAB.
10.
 If you are having trouble printing PostScript files with VMS (PostScript
errors or no printout), make sure that you have the form set for
NOTRUNCATE and NOWRAP. Also, make sure you are not trying to print
a flag page (unless you are using DCPS) since the flag page in the LAT
symbiont is a non-PostScript text file.
11.
 If you are having trouble printing PostScript files (for example, from
DECprint Supervisor or from a Windows-based PATHWORKS PC), try
disabling binary mode on the printer with the command SET PORT P1
BINARY DISABLED.
12.
 If you are printing across a wide area network bridge (for example, Vitalink)
and you get paused or stalled queues, increase the print server circuit timer
to 120 milliseconds with the command SET SERVER TRANSMIT 120.
13.
 If you can print successfully from PATHWORKS using DOS but have
problems printing from Windows, try increasing the Device Not Selected
and Transmission Retry timeouts from the Windows Printer Manager (select
Printer Setup, select the desired printer, and press the Connect button). 
						

							CHAPTER 13 TROUBLESHOOTING
13-21
Banyan VINES Troubleshooting
If you are having trouble printing with Banyan VINES, check the following:
1.
 Make sure that you have the Banyan VINES PCPrint software option
installed.
2.
 Make sure that the Banyan protocol is enabled.
3.
 If there are more than two hops (i.e., more than two routers) between the
print server and the file server, make sure that you have changed the hop
count to the appropriate number via BRAdmin or the print server console.
4.
 Use the VINES MUSER or MANAGE utility to verify that the print server
has logged in. If it has not, make sure that the StreetTalk login name
configured in the print server exactly matches the login name that was
configured using the MUSER or MANAGE utility on the file server.
5.
 Verify that the StreetTalk name associated with the print server service name
exactly matches the name of the print queue that was configured using the
MSERVICE or MANAGE utility on the file server.
6.
 Check to see that you have not exceeded the user limit on your Banyan file
server (because the print server must login as a user), that printing is enabled
on the queue, and that there are no security restrictions on the file server that
would prevent the print server from logging in. 
						

							CHAPTER 13 TROUBLESHOOTING
13-22
Web Browser Troubleshooting (TCP/IP)
1.
 If you can not connect to the print server using your web browser it may be
worth checking the Proxy Settings of your browser. Look in the Exceptions
setting and if necessary, type in the IP address of the print server. This will
stop your PC from trying to connect to your ISP or proxy server every time
you wish to look at the printer server.
2.
 Make sure that you are using the proper Web Browser, we recommend
Netscape Navigator version 3.0 or later/ Microsoft Internet Explorer version
3.02a or later. 
						

							APPENDIX
APPENDIX-1
A
APPENDIX
Appendix A
General Information
You can change the configuration of your print server using any of the following
methods.
· Brother BRAdmin utility for Windows 95 or later
· HTTP (using a web browser)
· HP’s JetAdmin or WerbJetAdmin Software
· TELNET (command utility)
· Brother BRCONFIG NetWare Utility (command utility)
· DEC NCP or NCL Utility
BRAdmin (Recommended)
The Brother BRAdmin utility can use the TCP/IP or IPX/SPX protocol. This utility
allows you to graphically manage aspects of the network and printer. It can also be
used to upgrade the firmware of the print server.
HTTP (Recommended)
Use your favorite web browser to connect to the Brother print server. This will allow
you to configure print server parameters.
JetAdmin or WebJetAdmin
Brother’s print server range is HP JetAdmin and WebJetAdmin compatible. 
						

							APPENDIX
APPENDIX-2
TELNET
To connect to the print server using TELNET on UNIX, Windows NT, or most other
TCP/IP systems, type: TELNET ipaddress at the command prompt of the system
prompt, where ipaddress is the IP address of the print server. When you are
connected, push RETURN or ENTER to get the # prompt, enter the password
access (the password will not appear on the screen), and type anything in response
to the Enter Username> prompt. When you see the Local> prompt, you are ready to
enter commands.
Enter HELP at the command prompt for a list of supported commands. For a
complete list of supported commands along with an explanation of them, please refer
to the file commands.pdf
BRCONFIG
Brother BRCONFIG utility runs on the DOS system prompt and is installed with
BRAdmin. To connect the print server using the Brother BRCONFIG NetWare
utility, Choose the BRCONFIG utility from the Brother BRAdmin utilities menu or
insert the Brother BRAdmin utility diskette into Drive A and type: A:BRCONFIG at
the DOS system prompt. If you have only one print server, you will be immediately
connected to that server. If you have more than one print server, you will be given a
list of available print servers. Type the number of the print server to which you wish
to connect. When you are connected, enter the password access (the password will
not appear on the screen) at the # prompt, and type anything in response to the
Enter Username> prompt. When you get the Local> prompt, you are ready to enter
commands. To use BRCONFIG, a Novell Server (running the IPX protocol) is
necessary and an active connection must be made to the server.
Enter HELP at the command prompt for a list of supported commands. For a
complete list of supported commands along with an explanation of them, please refer
to the file commands.pdf
For a list of commands and for information about upgrading firmware, please refer to
the chapter: commands.pdf on the CD-ROM that is supplied with the product CD.