Articles

access denied, unable to connect

April 10, 2005 at 14:36:47
Specs: Windows 2000, n/a

I have a Windows Server 2003 PDC 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 for admin/regular accounts. I've read that I have to make a registry change to the "restrictAnonymous" key. Do I make this change on the domain controller or the clients?


See More: access denied, unable to connect

Report •


#1
April 12, 2005 at 03:07:07

I don't think you should have to change that key value from the default. Where did you read this?

When you say 'network printer' do you mean print servers or printers attached to workstations or servers? (I can see where there might be a problem if they were on servers).

If they are printers connected to workstations, have you tried some basic diagnosis like pinging or accessing a shared dir, etc, on those workstations, or trying to print remotely when logged on as an admin?

Peter


Report •

#2
April 12, 2005 at 17:24:26

Yeah, their printers attached to the server. We can print fine from any workstation under any account (admin & normal user accounts) we just can't view the printer queue or manage documents. The permissions are properly set. We even gave admin access to normal users and the same error occurs. The restrictAnonymous thing I was talking about can easily be found through a google search. We made the change on the clients (which I believe is what your suppose to do) but nothing happened. I'm eager to hear your suggestions.

Report •

#3
April 12, 2005 at 18:59:10

I'm familiar with the restrictanonymous reg. setting but not in conjunction with printer problems. However, you are correct in that it is mentioned in this context on Usenet and other places. Personally I try (successfully so far) to avoid hooking network printers to servers.

What is it at now (both on the server and workstations), and have you rebooted after changing it?

Is this more of an annoyance than anything else or do you really need to manage the queues from the workstations?

Peter


Report •

Related Solutions

#4
April 13, 2005 at 08:59:34

I'm seeing the same thing. We've got 3 Server 2003 machines and 20+ Windows 2000 workstations. Non-administrators can't even view the print queues, let alone control or cancel jobs. Permissions on the printers look like "Domain Users" should have full rights.

Workstations running NT4 don't have any problem. Windows 2000 machines accessing print queues on NT4 print servers don't have a problem. Domain administrators on the Windows 2000 machines can manipulate the queues on the Server 2003 machines.

We run the printers through servers because some of them are in a different department and this way that department only has to pass one IP address through their firewall. This problem is affecting both those and our own local printers.


Report •


Ask Question