Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Printer getting "Access denied, unable to connect"

Status
Not open for further replies.

CLJBville

Technical User
Sep 10, 2004
8
US
I have two servers sharing printers one is Windows 2000 with 99 printers, the other is 2003 with 6 printers. The problem started about Monday or Tuesday this week. I have multiple XP Pro clients with SP3 that will have some issue with documents not printing. So I delete the network printer from the XP PC and re-add it. Sometimes it works, sometime it doesn't. One XP has 5 printers attached from the 2000 server, but two of them show "Access denied, unable to connect". Also when you re-add the printers the names do display consistently.

There seem to be three name combonations:
1. is just the share name with no server reference, this one won't print.
2. is like "share on server.domain.org", when the name is like this it shows the "Access denied, unable to connect" message.
3. is "share on server" and this one works.

The name changes seem to be consistent with how you add the printer. If I open the server and right click the queue and pick connect, I get #1. If I use the wizard and enter the UNC I also get #1. If I use the wizard and search the directory I get #2 or #3. So sometimes doing the wizard with the AD search will work fine, sometimes not. It appears to be luck as to whether it will work or not.

Finally, I've done the following trying to resolve this:
1. Rebooted both servers.
2. Rebooted all PCs having the problem.
3. Removed Symantec Endpoint AV from one of the PCs.
4. Tried connecting via Net Use.
5. Loaded critical patches on XP PCs.
6. Checked event logs on servers and PCs, no errors or odd messages.

Any help would be appreciated! We have about 300 PCs and only about 5 are currently showing this problem. The PCs are all in different departments and don't have anything unique about them that sets them apart from the majority of our systems.

Thank you!

Chris
 
Oops, I messed up the 2000 server is actually 2003 server.

Chris
 
Try adding one as a local printer to one of the workstations. Create a new port for it and set it to standard TCP/IP port. On the port name, type in the printers name as it is shown on the network. Does that work?
 
The problem started about Monday or Tuesday this week".

Just about the time of the most recent Window's Updates?

Not sure if this is that relevant, but if you are adding and deleting printers it may be worth a read?
Stopping of the Print Spooler
thread779-686557

There are also the Server Forums to check out.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top