"access denied, unable to connect"

Status
Not open for further replies.

ceobill

Beta member
Messages
1
I have a Windows Server 2003 domain controller and a bunch of Windows 2000 clients.

All of the Win2k clients have "access denied, unable to connect" for the status of their network printers. This holds true for both admin and regular accounts. I've read that I have to make a registry change to the "restrictAnonymous" key.

I made this change yet the policy it corresponds to still has "not defined" as its value under "Default Domain Controller Policy" settings.


Shouldn't the policy be effected when making a registry change? Am I looking at the right policies?

Any help would be greatly appreciated.
 
What is the share permissions for the printer?Admins should have full control and everyone else that needs to print to it change.Can an admin print to it from the 2003 sever OS?Also how do you have the shared printer set up?Through a print server?How are the client's paging into it.
 
Status
Not open for further replies.
Back
Top Bottom