Verify your Domain Name System (DNS) is configured and working correctly. I opened up ICMP on my firewall between the dmz (demilitarized zone) and the domain controllers and the group policy was able to apply. Custom search for *****: Google - Bing - Microsoft - Yahoo Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? Therefore, you should always refresh Group Policy to determine if Group Policy is working correctly.To refresh Group Policy on a specific computer:1.Open theStart menu. http://introbuilder.net/event-id/windows-event-error-1054.php
Windows could not obtain the name of a domain controller. x 1 Bill Gilbert I had the same issue with Broadcom 440x drivers in Dell Inspiron and Dimension computers using the XP built in driver (ver 3.5.1). We had a Dell Latitude C600 laptop out of the office for three months that would not process GPOs once the person brought it back in, could not find domain controller, After ensuring that the network connectivity to the domain controller has been reestablished, refresh the Group Policy on the computer: Open the Start menu. https://social.technet.microsoft.com/Forums/office/en-US/4061ae7b-b692-4df4-bcca-95a7c8c86330/gpupdate-fails-event-id-1054-windows-could-not-obtain-the-name-of-a-domain-controller?forum=winserverGP
x 3 Michael I have had the same error with a notebook running XP. From a newsgroup post: "I have the same problem and the only thing I have read that makes any sense is someone saying there was a XP hard drive image problem The solution I came up with was to include “localhost” (127.0.0.1) to be a trusted IP on both machines.
x 1 Robbie Foust This problem can occur if the user is authenticating to a MIT Kerberos realm with a Kerberos name mapping defined in AD. To correct the problem I set this flag in the registry to force it to treat the link as fast. x 1 Anonymous If you're using DHCP, make sure the DNS Server option (006) is set in your scope options. Event 1054 Group Policy Use a different network card Its hard to diagnose the exact cause.
On the client computer, run ipconfig /flushdns and check again. Event Id 1054 Windows 2008 R2 Wednesday, March 25, 2015 11:29 PM Reply | Quote 0 Sign in to vote Absolutely, 100% not the answer, not even an answer. Comments: EventID.Net According to Microsoft, this event occurs because the domain from which the group policy should be downloaed either does not exist or could not be contacted. https://technet.microsoft.com/en-us/library/cc727331(v=ws.10).aspx The process of detecting loop causes the switch port to go through multiple states: blocking, listening, learning, and finally forwarding.
But usually for me its been domain membership (even the errors do not relate SPECIFICALLY to domain membership) 0 LVL 3 Overall: Level 3 Message Author Comment by:davidkklim2006-04-17 Nope, no Event Id 1054 Error Code 58 Resolve Determine domain controller name The Group Policy service logs the name of the domain controller and the error code. x 9 EventID.Net As per Microsoft: "This problem may occur if the Group Policy engine or Active Directory times out while it waits for the network to start. x 3 Anonymous The problem is not with the NIC or DNS, but rather with the Microsoft XP OS.
Newer operating systems typically do not use the TSC by default if other timers are available in the system which can be used as a timekeeping source. https://www.experts-exchange.com/questions/21816984/Userenv-Event-ID-1054-Windows-cannot-obtain-the-domain-controller-name-for-your-computer-netowkr-Group-Policy-Processing-aborted.html Click Command Prompt. Event Id 1054 Cannot Obtain The Domain Controller Name My workstations could not find a DC through DNS and my DNS was not dynamically updating its SRV records. Event Id 1054 Group Policy Windows 2008 R2 Group Policy Processing aborted.
I checked application event log and found event id 1054. check over here I found a blog entry that said to install the "AMD Athlon™ 64 X2 Dual Core Processor Driver for Windows XP and Windows Server 2003". Windows could not obtain the name of a domain controller. I solved this problem by moving the user to another OU (to apply other GPOs), login once and move the user back to the original OU. Event Id 1054 Dns
Windows could not obtain the name of a domain controller. x 4 Anonymous I encountered this problem on my DC. driver, last updated October 11, 2007. his comment is here It appeared right after I changed a Domain.
Changed the File System of "C:\" from FAT32 to NTFS (wanted to do this on this machine for a long time, so even if it may have nothing to do with x 2 Richard Sims I had this problem with a new domain controller running Windows 2003.DHCP was installed on the server, but not yet configured or authorized.Removing DHCP, or configuring and This could be caused by a name resolution failure. Event Id 1054 Group Policy Windows 2012 Then stop logon service, flush DNS and register DNS again with IPCONFIG /registerDNS".
W2K and XP both require an accurate DNS server that accepts active updates. They reinstalled XP from the Cd that can with the computer. The problem was caused by the fact that the server's NIC was configured for IPSec. weblink Yes: My problem was resolved.
so if to try different nic, i will call the tech support first. Get 1:1 Help Now Advertise Here Enjoyed your answer? Enter the product name, event source, and event ID. To diagnose the failure, review the event log or run GPRESULT /H GPReport.html from the command line to access informati on about Group Policy results.
Event Logs Show: Log Name: System Source: GroupPolicy: Event ID: 1054 Level: Error User: System OpCode: (1) The processing of Group Policy failed. Why? USERENV(20c.aa4) 14:20:57:242 PingComputer: First time: -25 USERENV(20c.aa4) 14:20:57:242 PingComputer: Second time: -25 USERENV(20c.aa4) 14:20:57:257 PingComputer: First and second times match. How can I figure out why GPUpdate can't find a DC?