Windows Server 2003 GPMC produces this error:

[Guest]

I have a recent install of Windows 2003 server. I've been playing around with it for the first time and probably broke it. Recently I've been getting logon errors. No user I've added except adminstrator can log on to the client computer. I suspect because the admin credentials are cached. In Event Viewer I'm getting Userenv 1030 and 1058 saying it cannot load the group policies from the server.

I download and installed the GPMC from microsoft and here is the error when I try to access Default Domain Controller object:

"Windows cannot find the network path. Verify that the network path is corect and the destination computer is not busy or turned off. If windows still cannot find the network path, contact your network administrator.

What should I do?

 

[Buz [MSFT]]

Only members of the administrators group will be able to logon locally to a
domain controller.

For the second issue make sure the Domain Controller points to itself for
DNS and verify the netlogon and Sysvol shares are in fact shared.

Buz Brodin
MCSE NT4 / Win2K
Microsoft Enterprise Domain Support

Get Secure! - www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.

I have a recent install of Windows 2003 server. I've been playing around

with it for the first time and probably broke it. Recently I've been
getting logon errors. No user I've added except adminstrator can log on to
the client computer. I suspect because the admin credentials are cached.
In Event Viewer I'm getting Userenv 1030 and 1058 saying it cannot load the
group policies from the server.

I download and installed the GPMC from microsoft and here is the error

when I try to access Default Domain Controller object:

"Windows cannot find the network path. Verify that the network path is

corect and the destination computer is not busy or turned off. If windows
still cannot find the network path, contact your network administrator."