Networks

Ask something
Discussion Locked

4.11 print queue dropping on XP 4.83SP1

0 helpful
11 replies

by robert_jones

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We still have Netware 4.11 servers for file and print services. We are deploying Windows XP with client 4.81 SP1. We are seeing random problems with users getting "not available" in the printer status. Not all users see it at same time and is not consistant. Not all print queues show this and can be different printers each time. A reboot will sometimes fix it or multiple reboots. No problems accessing the file servers. Hard to troubleshoot since we can't recreate it and it is very inconsistant.We are going to try some direct IP printing to see if that works but it looks like it is the 4.83 SP1 client. Anyone know of any fixes, client settings to stop this?

11 replies

by slowlearner

If you are using IPX/SPX make sure that put them in the first in binding order. Also check to see if client NIC is 100Mbps VS 10Mbps (server, hub...) so take it down to 10Mbps (auto detect is sometime not good enough).

by pierrejamme

We have the same problem occassionally using HP Lasers with jetDirect cards even on the Win98s. TCIP is always available though. Select add port and chose TCIP, it never goes away like the NetWare configuration seems to any more. I don't think HPis really ibnnterested in upporting NetWare printers. Wish some company would take up the gauntlet.
If you do have HPs get their HP Install wizard. If you know the printers IP number (Print Config Page) it does an excellent job of re-install after the IPX is no longer found. Print config page will probably show NetWare is not configured.

by chris in windsor

We have had similar problems with NT 4 and W2k workstations and Hp printers with JetDirect cards. There is no rhyme or reason why it drops the connection. But trhe best way to solve the problem is to search the registry for the queue name and delete the registry entry pertaining to that queue (there could be several entries in the registry pertaining to the affected queue ...delete them all). Once the registry entries are deleted, you will now be able to reinstall the printer once again and print to it. There is a MS knowledgebase article referring to this (can't remember the number) but it basically tells you to do the same thing that I have written above.

by chris in windsor

In Response to the comment that normal users cannot add or remove printers.

This is the same situation that we have at our location. It is necessary for the administrator to make the changes to the registry and the removal and readdition of the printers.

by kumar

We had the same problem and used login script to map to the server where the printer queue existed.

by kumar

We had the same problem and used login script to map to the server where the printer queue existed.

This discussion is closed to new replies.