"Access denied, unable to connect" status when viewing printers

  • Thread starter Thread starter Robert Dean
  • Start date Start date
R

Robert Dean

When Windows 2000 machines open "Printers" the Status for all of the
printers is "Access denied, unable to connect". When a single printer is
opened (double click on printer) the title bar of the window displays the
printer name followed by "Access denied, unable to connect" and queued print
jobs are not displayed. Users can not manage (Cancel, Restart, etc.) their
print jobs. This problem effects only Windows 2000 machines, Windows NT
machines can view and manage print jobs with no problem. The symptoms are
the same regardless of who (user or administrator) logs on to the machine.

There are no problems submitting print jobs. Users can submit jobs and can
modify the printer settings. The problem is limited to viewing and managing
queued print jobs on Windows 2000 machines.

The print server is a Windows NT SP 6a server. All printers are network
printers (using TCP/IP Ports). The domain is Windows NT. The Windows 2000
machines are at SP 4.

The problem started after installing several security patches and modifying
registry settings as suggested by the "Baseline Security Analyzer". I have
tried rolling back these changes but have had no luck in resolving the
problem. One thing that I thought might be the problem is the
restrictanonymous registry setting. I set it to 0 but the problem persists.
 
I have the same issue on my site, but it dose not affect
any of the functions for users. They can administer their
jobs. It's more of any annoyance with the status message
appearing incorrectly. If you get any feedback, please
forward that to me.

Thanks
Sam
 
In the KB article (
http://support.microsoft.com/default.aspx?scid=kb;en-us;162695
) the symptoms are the same but the cause does not match my circumstances.
I did not use SMS Installer to install the printers. The NullSessionShares
key on the server and client contains several values including spoolss.

I have found that if I change HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlset\Control\Lsa\restrictanonymous from 2 to 1 on the client
the problem goes away. In my original post I stated that I changed this
value to 0, but that was on the server.

Anyway, problem solved. I would like to set restrictanonymous to 2, but I
guess that will have to wait until I move from a NT domain to a 2000 domain
and use a 2000 server to share the printers.


Alan Morris(MSFT) said:
This is the result of the Server not having proper access to the client.

Here's the KB article on this


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




--
Alan Morris
Microsoft 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.

Sam said:
I have the same issue on my site, but it dose not affect
any of the functions for users. They can administer their
jobs. It's more of any annoyance with the status message
appearing incorrectly. If you get any feedback, please
forward that to me.

Thanks
Sam
Click to expand...
Click to expand...
 
Hello,

We recently had the same problem after implementing some hotfixes and
registry settings that MBSA suggested.

After reviewing the changes, we changed the registry value:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\restrictanonymous
= 1

This is from the setting that MBSA suggested of 'restrictanonymous =
2'.

This seemed to fix the problem we were having viewing the print queues
on our NT 4 print server. Hope this helps.


geblah
 
Robert said:
*In the KB article (
http://tinyurl.com/2f4zm
) the symptoms are the same but the cause does not match m
circumstances.
I did not use SMS Installer to install the printers. Th
NullSessionShares
key on the server and client contains several values includin
spoolss.

I have found that if I change HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlset\Control\Lsa\restrictanonymous from 2 to 1 on th
client
the problem goes away. In my original post I stated that I change
this
value to 0, but that was on the server.

Anyway, problem solved. I would like to set restrictanonymous to 2
but I
guess that will have to wait until I move from a NT domain to a 200
domain
and use a 2000 server to share the printers.


Alan Morris(MSFT) said:
This is the result of the Server not having proper access to th client.

Here's the KB article on this


http://tinyurl.com/2f4zm
SMSINST: "Access Denied" Error Message When You Try to Connect to Shared
Network Printer




--
Alan Morris
Microsoft 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 confer no
rights.
Click to expand...
Click to expand...


-
dotjohnso
 
Robert said:
*In the KB article (
http://tinyurl.com/2f4zm
) the symptoms are the same but the cause does not match m
circumstances.
I did not use SMS Installer to install the printers. Th
NullSessionShares
key on the server and client contains several values includin
spoolss.

I have found that if I change HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlset\Control\Lsa\restrictanonymous from 2 to 1 on th
client
the problem goes away. In my original post I stated that I change
this
value to 0, but that was on the server.

Anyway, problem solved. I would like to set restrictanonymous to 2
but I
guess that will have to wait until I move from a NT domain to a 200
domain
and use a 2000 server to share the printers.


Alan Morris(MSFT) said:
This is the result of the Server not having proper access to th client.

Here's the KB article on this


http://tinyurl.com/2f4zm
SMSINST: "Access Denied" Error Message When You Try to Connect to Shared
Network Printer




--
Alan Morris
Microsoft 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 confer no
rights.


*
Click to expand...
Click to expand...

I would like to thank Robert Dean for resolving the issue with "acces
denied, unable to connect". Making the change to restrictanonymou
from to 2 to 1. I also had used the Baseline Security Analyzer, an
had the same problem after I ran the security updates. I tired all th
MS resolutions and they we are all unsuccessful. Thanks again Rober
Dea


-
dotjohnso
 
Back
Top