Unable to Connect. Access Denied

[Phil Strack]

Hi All-
Using Windows Server 2003 and Windows XP SP1 clients. Clients and servers
are in Active Directory.

Can anyone explain what causes the "Unable to Connect. Access Denied." error
when a client opens a printer. All of my XP clients are seeing this when
opening network printer resources. I do have some group policies implemented
but am not enforcing anything that should affect this. I have verified that
all of the permissions to the shared resources are correct and valid.
Users can still print but it is not as responsive as it should be.

I found a KBase link for Windows 2000 regarding changing a registry setting
to change the AllowAnonymous key to a particular value and although the
details escape me at the moment, I did verify that it was set as specified
in the KBase article.



Thanks

-Phil

 

[Alan Morris\(MSFT\)]

Yes, your Server is getting denied access when communicating to the spooler
on the XP machines.

You need to set AllowAnonymous on the clients

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Phil Strack]

I checked the AllowAnonymous settings against what the KBase article said
and they are correct. Any other suggestions?


Yes, your Server is getting denied access when communicating to the spooler
on the XP machines.

You need to set AllowAnonymous on the clients

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Alan Morris\(MSFT\)]

this is usually related to a security setting on the client. There was one
user who had this issue when the clients could not authenticate the session
from the server and the problem was resolved when they corrected something
on the Domain Controller.

If you share a folder on the client, can the server connect or is an error
generated?

here's a couple more kb
Access denied from server
http://support.microsoft.com/default.aspx?scid=kb;en-us;162695
SMSINST: "Access Denied" Error Message When You Try to Connect to a Shared
Network Printer

needs to be set to 1
http://support.microsoft.com/default.aspx?scid=kb;en-us;246261
How to Use the RestrictAnonymous Registry Value in Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;312055
Cannot Use Network Printer If Your Password Is Not Saved

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

I checked the AllowAnonymous settings against what the KBase article said
and they are correct. Any other suggestions?


Yes, your Server is getting denied access when communicating to the spooler
on the XP machines.

You need to set AllowAnonymous on the clients

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi All-
Using Windows Server 2003 and Windows XP SP1 clients. Clients and servers
are in Active Directory.

Can anyone explain what causes the "Unable to Connect. Access Denied." error
when a client opens a printer. All of my XP clients are seeing this when
opening network printer resources. I do have some group policies implemented
but am not enforcing anything that should affect this. I have verified that
all of the permissions to the shared resources are correct and valid.
Users can still print but it is not as responsive as it should be.

I found a KBase link for Windows 2000 regarding changing a registry setting
to change the AllowAnonymous key to a particular value and although the
details escape me at the moment, I did verify that it was set as specified
in the KBase article.



Thanks

-Phil