[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 764
  • Last Modified:

Active Directory Event ID 1054

I get this error message on the Domain Controller ever 5 minutes.  

I checked the network connections---they seem fine
netdiag didn't show any errors
we can go to \\mydomain.com\sysvol\mydomain.com from all the computers that I've checked to ensure connectivity.
tried gpupdate /force

any other suggestions?


Product: Windows Operating System 
ID: 1054 
Source: Userenv 
Version: 5.2 
Message: Windows cannot obtain the domain controller name for your computer network. (%1). Group Policy processing aborted. 
A network connectivity or configuration problem exists. Group Policy settings cannot be applied until the problem is fixed.

Open in new window

  • 3
  • 2
3 Solutions
seven45Author Commented:
Thanks for the quick response:  

I had tried the kb 324174....and made sure the DNS was pointing to the right location.  
the first preferred dns is the DC itself, and the second dns is the second DC.

the second link (the hotfix),  I remember applying that on one of the computers-- I remember the hotfix not applying on some of the machines as they had the sp2 and patches that were newer than the hotfix, or were on sp3.    What I was wondering:  Is it possible that if we have just a couple of xp machines with sp1 that "require" the hotfix on the domain--- will it cause the DC to give errors every 5 mins.  If that is the case, it would be a pain to locate that pc or those small group of pc's in a domain of 450 computers.   I wouldn't suspect (or hope) that to be an issue, else, it would be very commonly found in most networks.  

Also,  One other addition:  There are two Gig cards that are  Teamed (HP).  There was an issue with the teaming in one of the KB's that could be a suspect---but I don't know or can confirm it.  
After the hotfix is applied you should add and registry key, GpNetworkStartTimeoutPolicyValue.

Set the value to 60 if you got Gig card.

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

seven45Author Commented:
Yea, I had set it to 60, then 90, up to 240 to see at what value the error would go away.  so far, the DC error still remains the same.
check whether following commands give rt output

>set q=srv
>_ldap._tcp.<FQDN of Domain Name>      ------->Shoud show all the DCs
>_kerberos._tcp.<FQDN of Domain Name>
>gc._tcp.<FQDN of Domain Name>

If above commands are showing right DCs.Try to access sysvol share by \\<domainName>\sysvol
If it failes check DFS client service is started or not
Check the following registry value:
DisableDFS: REG_DWORD: range: 0 or 1
0 = enabled; 1 = disabled
Default: 0
Make sure that the value is set to 0, enabling the Dfs client. Also, File and Printer Sharing for Microsoft Networks must be enabled on the interface

seven45Author Commented:
Although, these did not help my specific situation, the responses were great and helped ensure a healthy server configuration.

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now