Home > Event Id > Event Id 1054

Event Id 1054


GPUpdate /force reports: Updating Policy... You may see negative ping times, or ridiculously high ping times. One of the main reasons this behavior may occur is if the address for the configured preferred DNS server unreachable. Using a DNS address that doesn't have the AD zone data. Check This Out

Setting the registry key “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\DisableDHCPMediaSense” to “1” as per ME239924 solved it. Checking the event logs, this seems to have been happening consistently for the last month or so. See ME924441 for the update from Microsoft. This is a microsoft bug and has wasted hours of my time this week and last. my site

Event Id 1054 Cannot Obtain The Domain Controller Name

Promoted by Recorded Future Enhance your security with threat intelligence from the web. Once I removed that the problem was gone. thx 0 Comment Question by:mcrmg Facebook Twitter LinkedIn Email LVL 12 Best Solution bypiattnd One thing you can try is disable all non Microsoft services and run it for a To correct the problem I set this flag in the registry to force it to treat the link as fast.

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. Ipconfig /all showing correct result as it suppose to. Computer Configuration was just not applied to this machine whilst other PCs (even identical Notebooks) had the same GPO applied without problems. Event Id 1054 Dns Event ID 1054 — Group Policy Preprocessing (Security) Updated: September 21, 2007Applies To: Windows Server 2008 Group Policy preprocessing uses security to act on behalf of the computer or user.

This was an older blog that I’ve revamped. Event Details Product: Windows Operating System ID: 1054 Source: Microsoft-Windows-GroupPolicy Version: 6.0 Symbolic Name: gpEvent_FAILED_DSNAME Message: The processing of Group Policy failed. After I uninstalled this program, the problem disappeared. They said all the problems were solved." x 2 Anonymous The Intel Pro 1000 MT series of NICs in confuction with Windows XP shows an Error code 1054.

Each return all three DCs, and thecorrect IP addresses,when queried for _ldap._tcp.dc._msdcs.domainname. Event Id 1054 Server 2012 Make sure time is configured properly. DarrenDarren Mar-Elia MS-MVP, Group Policy - "The Group Policy Experts" Friday, October 19, 2012 10:23 PM Reply | Quote 0 Sign in to vote Hi, Regarding the current issue, Events appearing in the event log may not reflect the most current state of Group Policy.

Event Id 1054 Windows 2008 R2

KB895980 provides more specifics about this issue. It can ping the DCs and all the machines on the network once I login into domain, everything seem fine, but just couldn't get the GPO deploy on this kind of Event Id 1054 Cannot Obtain The Domain Controller Name Errors were generated after blocking ICMP on workstations with IPSec. Event Id 1054 Group Policy Windows 2008 R2 This means the spanning tree cycle is never initiated.

x 2 Mark Casemore I was having this problem on a Win2k3 member server using a static IP address. his comment is here 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. No luck. 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 Id 1054 Error Code 58

ClickAll Programs and then clickAccessories.2.ClickCommand Prompt.3.In the command prompt window, typegpupdate and then press ENTER.4.When the gpupdate command completes, open the Event Viewer.Reference LinksEvent ID 1054 from Source Microsoft-Windows-GroupPolicy Did Internet Marketing E-Commerce Windows XP Sales MS SQL Server How to Monitor Bandwidth using SNMP or WMI using PRTG Network Monitor Video by: Kimberley This video gives you a great overview read more... this contact form You’ll be auto redirected in 1 second.

First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. Event Id 1054 Group Policy Windows 2012 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, If you cannot ping the domain controller from any computer, first ensure that the domain controller is running.

Join the community of 500,000 technology professionals and ask your questions.

The following errors were encountered: The processing of Group Policy failed. This could be caused by a name resolution failure. I checked application event log and found event id 1054. Verify Your Domain Name System Dns Is Configured And Working Correctly Ensure that the machine account has sufficient permissions To fix this, on the server that contains Active Directory Domain Services, grant the machine account for the Windows Deployment Services server the necessary permissions

As for the GPO, I did add two settings in the Registry (FOR LOCAL ADMINISTRATOR, the same user i did the Wireless setup for): [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System] "GroupPolicyMinTransferRate"=dword:00000000 Windows Registry Editor Version 5.00 Computer policy could not be updated successfully. You can fix this by forcing Windows to use the PM timer for QueryPerformanceCounter. navigate here Even the firewall was configured on both machines to trust each other’s IP address, the error was still there.

Note the following: If you can successfully ping the domain controller by IP address, but not by FQDN, this indicates a possible issue with DNS host name resolution. Windows could not obtain the name of a domain controller. You’ll be auto redirected in 1 second. From a newsgroup post: "All computers must point to the DS for DNS resolution.

Joined the domain again & rebooted properly. 5. you culd try and remove the workstation from the domain and add it again, this should fix the issue 0 LVL 3 Overall: Level 3 Message Author Comment by:davidkklim2006-04-17 Comment x 217 AceyMan We have a new Opteron server (1210, AM2 socket) on a Tyan S3950 mainboard (Broadcomm HT-1000 chipset).This server was promoted to a DC and now holds all the x 1 Anonymous Also had this problem on machines with Gigabit NICs.

M326152 helped as the server was connected to a Netgear Gigabit switch. Active Directory Domain Service is running and has network connectivity. System Warning: DHCP Your computer was not able to renew its address from the network (from the DHCP Serve) for the Network card with the newtork address:XXXXXXXXX. We appreciate your feedback.

Join our community for more solutions or to ask questions. The Netlogon service is not robust enough to account for variances with some network cards and network environments. If XP is not able to transmit during that 30 seconds it will be logged as a failure and it will not retry. While in the DNS console everything looked fine, in the SBS administration console, Computer management (local), Service and application, DNS there was something different: The zone was pointing to another address.

If you cannot successfully ping the domain controller by IP address, this indicates a possible issue with network connectivity, the firewall configuration, or the IPsec configuration. x 11 Alex Albright You might get this event after turning on the firewall on a DC. Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended Because it's a domain controller, you likely don't have many items in there that are critical, though look for any raid controller software or things of that nature that you would

Then moved the PC-Account in the ActiveDirectory to the container with the GPO I want to apply to the PCs. The specific driver update is dated September 2007 and is called “AMD Opteron™ Processor with AMD PowerNow!™ Technology Driver Version for Windows XP and Windows Server 2003 (x86 and x64)”. These two articles fixed the same problem for me.