Event Id 1054 Cannot Obtain The Domain Controller Name
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. The specific driver update is dated September 2007 and is called “AMD Opteron™ Processor with AMD PowerNow!™ Technology Driver Version 1.3.2.0053 for Windows XP and Windows Server 2003 (x86 and x64)”. Setting the registry key “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\DisableDHCPMediaSense” to “1” as per ME239924 solved it. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.I'm relatively new to investigating server problems, is there a good place to start looking into this issue? http://kshelper.com/event-id/event-id-1054-group-policy.html
Now that we upped the maximum ICMP packet size to 2048 and rebooted the client machine, the group policies process fine. Even the firewall was configured on both machines to trust each other’s IP address, the error was still there. All Activity Home Software, Hardware, Media and Games Forum Categories Networks and the Internet 1054: Windows cannot obtain the domain controller name... See ME555381 for information on how to configure the Windows 2003 SP1 firewall for a Domain Controller.
Event Id 1054 Cannot Obtain The Domain Controller Name
It is also configured as a DHCP and DNS server (another server is the primary DHCP server).We monitor the server using CA unicenter and were first alerted to the server via nslookup getting right hostname and DNS server. See ME299563 for more details. The reboot is very important!!!!
I went to a client system and the time sync is now fixed - thank you!!Ran a 'gpupdate /force', but still receiving the GPO error.ZT Friday, October 30, 2009 7:19 PM Are there any other time related errors on the DCs or clients? 3. You can also turn on debug logging for Userenv which will give you a lot more information about what is breaking: Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon Value: UserEnvDebugLevel Value Type: REG_DWORD Value Data: Windows Cannot Obtain The Domain Controller Name Server 2003 They reinstalled XP from the Cd that can with the computer.
A couple of other ideas as Go to Solution 13 Comments LVL 6 Overall: Level 6 Windows XP 6 Message Expert Comment by:Antunb2006-04-17 look in the event log, in system This event occurred together with Event ID 14 from source W32Time, Event ID 29 from source W32Time and Event ID 5719 from source NETLOGON. To troubleshoot the network connectivity or configuration problem, try one or all of the following: In Event Viewer, click System, and check for any networking-related messages, such as Netlogon messages, that http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=1054&EvtSrc=Userenv 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.
Group Policy processing aborted. Event Id 1054 Dns I have tried all the suggestions found from Microsoft and other forums, none seem to help. To verify that the domain controller can be contacted through Domain Name System (DNS), try to access \\mydomain.com\sysvol\mydomain.com, where mydomain.com is the fully qualified DNS name of your domain. These two domain controllers are both GC.
Event Id 1054 Group Policy
Wonder if it's worth locking the NIC at 100MB. http://www.techrepublic.com/forums/discussions/windows-cannot-obtain-the-domain-controller-name-for-your-computer-network/ Sign In Sign Up Home Forums Browse Back Browse Forums Rules Donation Activity Back Activity Unread Content Content I Started My Activity Streams All Activity Search Subscription Back Subscription Orders Manage Event Id 1054 Cannot Obtain The Domain Controller Name x 199 Anonymous On our server, I removed the logon script in the GPO and this fixed the problem. Event Id 1054 Group Policy Windows 2008 R2 x 1 Anonymous If you're using DHCP, make sure the DNS Server option (006) is set in your scope options.
Verify that you can access the domain controller by using tools such as the Active Directory Users and Computers snap-in. Check to see whether other computers on your network are having the same problem. If you allow ICMP-traffic for the local network (or just the DC), the error will go away. http://kshelper.com/event-id/frs-event-id-13508.html Over 25 plugins to make your life easier
Go to the following key in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters 3. Event Id 1054 Group Policy Error Code 58 The following error occurred: The semaphone timeout period has expireed...... \\This is not true, machine is getting IP from DHCP and i can run ipconfig /release /renew... \\Next system warning is This causes the spurious ping times, and causes problem for GPO transfer rate calculations (hence Christophe Derdeyn's solution) You can read more about this issue in this blog by the Active
This fix will most certainly cause problems for mobile users, but it worked for my desktop machines.
It solved the GPO script installation problem, but the machine still cannot found the DC on startup. Or sign in with one of these services Sign in with Facebook Sign in with Twitter Sign Up All Content All Content This Topic This Forum Advanced Search Facebook Twitter Google Ipconfig /all showing correct result as it suppose to. Windows Cannot Obtain The Domain Controller Name For Your Computer Network See TB727055 - "Troubleshooting Common Active Directory Setup Issues in Windows 2000" and ME237675 - "Setting Up the Domain Name System for Active Directory".
Every tests we did was fine except the user login over VPN. Recreating the zone as an Active Directory integrated zone with only secure updates and then running net stop netlogon and net start netlogon successfully recreated the missing _msdcs forward lookup zone. x 2 EventID.Net Error: "A socket operation was attempted to an unreachable host." - As per Microsoft, this event may occur if the address for the configured preferred Domain Name System this contact form Join the community Back I agree Powerful tools you need, all for free.
Multi core or multiprocessor systems may encounter Time Stamp Counter (TSC) drift when the time between different cores is not synchronized. x 91 Markus H. so if to try different nic, i will call the tech support first. A couple of other ideas as food for thought; http://support.microsoft.com/default.aspx?scid=kb;en-us;840669#E6ADAAA assuming there is more than one network adapter (wired and wireless) check the network adapter binding order in advanced Network Connections,
This firewall was blocking all the connections via 127.0.0.1, so the Netlogon service was not able to communicate. ZoneAlarm) without configuring it properly (so the firewall blocked the access to the domain controller).