Windows cannot access registry info

  • Thread starter Thread starter Dan Buonocore
  • Start date Start date
D

Dan Buonocore

We are receiving the following error message (Event ID
1000, Source Userenv) within the application log on
several of our W2K servers:

Windows cannot access the registry information at
\\domainname.com\sysvol\domainname.com\Policies\{31B2F340-
016D-11D2-945F-00C04FB984F9}\Machine\registry.pol with
(5).

Research on the error message 5 suggested an 'Access
Denied' error while accessing the Sysvol folder. However,
I confirmed the Sysvol folder was shared and I can
directly connect to the registry.pol from the servers
getting the error message.

In addition, our Exchange server recently stopped
replicating within AD, and it took four days to get
Exchange back in AD. This error message is still being
entered in all W2K servers Application logs about every 1
1/2 hours, and may be the reason behind the Exchange
replication problems.

Any help would be appreciated
 
In
Dan Buonocore said:
We are receiving the following error message (Event ID
1000, Source Userenv) within the application log on
several of our W2K servers:

Windows cannot access the registry information at
\\domainname.com\sysvol\domainname.com\Policies\{31B2F340-
016D-11D2-945F-00C04FB984F9}\Machine\registry.pol with
(5).

Research on the error message 5 suggested an 'Access
Denied' error while accessing the Sysvol folder. However,
I confirmed the Sysvol folder was shared and I can
directly connect to the registry.pol from the servers
getting the error message.

In addition, our Exchange server recently stopped
replicating within AD, and it took four days to get
Exchange back in AD. This error message is still being
entered in all W2K servers Application logs about every 1
1/2 hours, and may be the reason behind the Exchange
replication problems.

Any help would be appreciated
Click to expand...

This can be indicative of a DNS misconfiguration. AD contacts DNS for all
it's resource and service locations. If using an ISP's DNS in any machines'
IP properties, then this error can occur, along with a multitude of other
errors. The idea is to only use the internal DNS servers that host the AD
zone and configure a forwarder for efficient Internet resolution.

If you like, to better assiste, we'll need some configuration information.
If you can post an unedited ipconfig /all from your DC, a client and from
the Exchange machine and please let us know what your AD DNS domain name
actually is and we can point out what's what in your configuration.

Thanks!

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Back
Top