XP and SYSVOL Issues

  • Thread starter Thread starter Amanda
  • Start date Start date
A

Amanda

I have recently installed several new XP machines into our network, and
recently noticed some strange errors.

I cannot get access to \\domainname\sysvol . but I can access it by using
the DC name ie. \\domaincontroller\sysvol . This itself is causing a whole
headache of troubles.

GPO's are not applying because of this. Below is a list of the errors I am
getting.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 7/29/2003
Time: 12:44:19 PM
User: NE\admin
Computer: NE004
Description:
Windows cannot query for the list of Group Policy objects. A message that
describes the reason for this was previously logged by the policy engine.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: 7/29/2003
Time: 12:44:19 PM
User: NE\admin
Computer: NE004
Description:
Windows cannot access the file gpt.ini for GPO
CN={C953E940-2BD4-4DEC-A931-7008D4B4BCE6},CN=Policies,CN=System,DC=NE. The
file must be present at the location
<\\NE\SysVol\NE\Policies\{C953E940-2BD4-4DEC-A931-7008D4B4BCE6}\gpt.ini>.
(The network path was not found. ). Group Policy processing aborted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Does anyone have any idea why these machines would not be able to access the
SYSVOL share? I am at a loss....
 
I *think* the resolution of the domain based sysvol lookup is site aware.
Have you checked the DNS settings on the clients are pointing to a DNS
server containing the SRV records for your DCs, the SRV records are setup
correctly, and the DCs are advertising? dcdiag has an advertising test you
can run on your DCs that can help with the latter parts.

Jason
 
Back
Top