GPO Event error 1054

[Tony Haberman]

I keep getting the following message on all XP Pro SP1
machines on my 2000 SP3 Domain I have searched the KB and
don't have any of the problems it lists. DNS servers pass
all tests. I have run nslookup and can't find a problem
there either. Policies that once applied aren't applying
anymore. This is at a High School where it is important
to be able to lock down the machines to some degree. Any
suggestions?
Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1054

Date: 11/18/2003

Time: 4:05:05 PM

User: NT AUTHORITY\SYSTEM

Computer: ED-CPUTECH

Description:

Windows cannot obtain the domain controller name for your
computer network. (An unexpected network error
occurred. ). Group Policy processing aborted.

 

[Veets]

Hey Tony,
Not sure if this is applicable but I've seen GPO problems when there's a
conflict between the local security policy & the GPO. Also, there's a
Microsoft utility called mpsreport (I think that's what it's called) that
can help you troubleshoot domain issues ->
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd915706/MPSRPT_DirSvc.EXE>
Hope that points you in the right direction
Veets

 

[Cary Shultz [A.D. MVP]]

Tony,

The utility that Veets suggested is a good one. There are about 12
different files to download. I would look at the MPS_DirSvc. Essentially
it will give you the contents of the various log files ( Event Viewer ) and
run many of the tests that you can already run manually. So, if you are not
familiar with the many various tests ( most of which become available after
installing the Support Tools ) I would go for it.

If you already have the Support Tools installed and are familiar with the
dcdiag and netdiag tests I would run them and redirect the output to a file.
So, for example, run 'dcdiag /v >c:\dcdiagdc01.log'. This will produce the
output of that test to a .log file called dcdiagdc01.log located at c:\ that
you can open with Notepad. Then search for 'fail' and 'error'.

I strongly suggest that you first focus on DNS. This is usually the
culprit. You must also ensure that the DC that holds the FSMO role of PDC
Emulator is available. This is muy importante for GPO. You can use 'netdom
query fsmo' or 'nltest /dsgetdc:yourdomain' or 'nltest
/dclist:yourdomain.com' or ReplMon.

Have you tried running GPOTOOL and / or GPRESULT?

HTH,

Cary