Access denied, unable to connect

Hi ..I got a serious problem here with my 2003 DC (print server), everything
has been going well, until recently my 2 (win2k) clients get the above error
when opening printers folder, but they can print, but why does it do that???
Nothing has changed ..I mean permissions wise or anything like that. Please
help

Have you installed new application on their PCs? or new service on their
machiens also? or a new service on the DC ???

if yes follow this and tell us back the result:

Warning If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk.
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Right-click the following registry subkey, and then click Permissions:
HKEY_LOCAL_MACHINE\SYSTEM\CurentControlSet\Control \SecurePipeServers\Winreg
4. Click each account that is displayed in the Group or user names list, and
then verify that the appropriate permissions are configured for that account
in the Permissions for AccountName list.

If you have to add a group or a user account and assign permissions to that
account, follow these steps:
a. Click Add.
b. In the Enter the object names to select box, type the group or the user
account that you want to add, click Check Names, and then click OK.
c. In the Permissions for AccountName list, click to select the Allow check
box that is next to the permission setting that you want to assign.
5. Click OK.

"Brainscan" wrote:

> Hi ..I got a serious problem here with my 2003 DC (print server), everything
> has been going well, until recently my 2 (win2k) clients get the above error
> when opening printers folder, but they can print, but why does it do that???
> Nothing has changed ..I mean permissions wise or anything like that. Please
> help

No nothing has changed ...This is what puzzles me. Not on the clients or the
DC.

"Maamoun" wrote:

> Have you installed new application on their PCs? or new service on their
> machiens also? or a new service on the DC ???
>
> if yes follow this and tell us back the result:
>
> Warning If you use Registry Editor incorrectly, you may cause serious
> problems that may require you to reinstall your operating system. Microsoft
> cannot guarantee that you can solve problems that result from using Registry
> Editor incorrectly. Use Registry Editor at your own risk.
> 1. Click Start, and then click Run.
> 2. In the Open box, type regedit, and then click OK.
> 3. Right-click the following registry subkey, and then click Permissions:
> HKEY_LOCAL_MACHINE\SYSTEM\CurentControlSet\Control \SecurePipeServers\Winreg
> 4. Click each account that is displayed in the Group or user names list, and
> then verify that the appropriate permissions are configured for that account
> in the Permissions for AccountName list.
>
> If you have to add a group or a user account and assign permissions to that
> account, follow these steps:
> a. Click Add.
> b. In the Enter the object names to select box, type the group or the user
> account that you want to add, click Check Names, and then click OK.
> c. In the Permissions for AccountName list, click to select the Allow check
> box that is next to the permission setting that you want to assign.
> 5. Click OK.
>
> "Brainscan" wrote:
>
> > Hi ..I got a serious problem here with my 2003 DC (print server), everything
> > has been going well, until recently my 2 (win2k) clients get the above error
> > when opening printers folder, but they can print, but why does it do that???
> > Nothing has changed ..I mean permissions wise or anything like that. Please
> > help

You dont have to change things to cause such problems, some kind of
services/spywares/etc can do so.

backup your registry and go ahead.

"Brainscan" wrote:

> No nothing has changed ...This is what puzzles me. Not on the clients or the
> DC.
>
> "Maamoun" wrote:
>
> > Have you installed new application on their PCs? or new service on their
> > machiens also? or a new service on the DC ???
> >
> > if yes follow this and tell us back the result:
> >
> > Warning If you use Registry Editor incorrectly, you may cause serious
> > problems that may require you to reinstall your operating system. Microsoft
> > cannot guarantee that you can solve problems that result from using Registry
> > Editor incorrectly. Use Registry Editor at your own risk.
> > 1. Click Start, and then click Run.
> > 2. In the Open box, type regedit, and then click OK.
> > 3. Right-click the following registry subkey, and then click Permissions:
> > HKEY_LOCAL_MACHINE\SYSTEM\CurentControlSet\Control \SecurePipeServers\Winreg
> > 4. Click each account that is displayed in the Group or user names list, and
> > then verify that the appropriate permissions are configured for that account
> > in the Permissions for AccountName list.
> >
> > If you have to add a group or a user account and assign permissions to that
> > account, follow these steps:
> > a. Click Add.
> > b. In the Enter the object names to select box, type the group or the user
> > account that you want to add, click Check Names, and then click OK.
> > c. In the Permissions for AccountName list, click to select the Allow check
> > box that is next to the permission setting that you want to assign.
> > 5. Click OK.
> >
> > "Brainscan" wrote:
> >
> > > Hi ..I got a serious problem here with my 2003 DC (print server), everything
> > > has been going well, until recently my 2 (win2k) clients get the above error
> > > when opening printers folder, but they can print, but why does it do that???
> > > Nothing has changed ..I mean permissions wise or anything like that. Please
> > > help

Maamoun, I'll try this out and let you know. Please keep looking at this
thread in the future so I can tell you my results.

Thanks.

--
Message posted via http://www.winserverkb.com

Maamoun,

Could you please explain your reasoning for this? It is my understanding
that the Winreg registry key controls who has remote access to the
registry. How does that play in with the printing error exactly?

--
Message posted via http://www.winserverkb.com