Windows 2000/xp ipp troubleshooting, Novell netware troubleshooting – Brother HL-4000CN User Manual

Page 75

Advertising
background image

10-8

Windows 2000/XP IPP Troubleshooting


Make sure that the URL setting for IPP is set to http://ip_address:631/ipp
(enter your printer IP address to "ip_address").

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 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.

1. If you changed the login password, you must change the password in both

the print server by using a web browser or the BRAdmin application 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 selected the appropriate Queue at the Netware
Environment button in Netware tab on BRAdmin application.

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 a Web browser.

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).

Advertising