Home > Event Id > Event Id 1054 Cannot Obtain The Domain Controller Name

Event Id 1054 Cannot Obtain The Domain Controller Name


Maybe it was because the Switch was too cheap. 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. Set the /usepmtimer switch in boot.ini and reboot the system. 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 have a peek here

See ME840669 to resolve this problem. x 1 Anonymous If you're using DHCP, make sure the DNS Server option (006) is set in your scope options. Pennsylvania Internal Links Log in Entries RSS Comments RSS More About Me Terms of Use Privacy Policy About this Blog Contact Me Copyright © 2016 SeattlePro Enterprises, LLC. Philippines 14.

Event Id 1054 Cannot Obtain The Domain Controller Name

Ohio 9. Updating the Realtek RTL8139/810x NIC drivers fixed the problem. x 2 Anonymous Try flashing with the latest BIOS. Took PC out of domain and deleted the computer account there. 2.

I see you have tried the GPO "fix". Directory service busy Correct me, if i'm wrong, you mean to say when you ping the dc it doesn't give you proper ping response, which can be RTO(Request time out). I had the 1054 Userenv event every 5 minutes. Event Id 1054 Error Code 58 On the negative-side of this it can cause group policy defects.

Thanks 0 LVL 6 Overall: Level 6 Windows XP 6 Message Expert Comment by:Antunb2006-04-17 ok other thing is try a different network card? 0 LVL 3 Overall: Level 3 Event Id 1054 Group Policy 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 driver, last updated October 11, 2007. Connect with top rated Experts 12 Experts available now in Live!

Switzerland The top 10 US states with the most visitors are: 1. Event Id 1054 Dns Privacy statement  © 2016 Microsoft. 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 x 6 Dave B I have this problem with a Wireless LAN card.

Event Id 1054 Group Policy

After having tried every possible solution on this site, I think the following did the trick: 1. Repeat this command several times. Event Id 1054 Cannot Obtain The Domain Controller Name Also, see ME933458, ME938448 and the links to "Fixing Scripts policy settings problems", "Troubleshooting network problems", WITP76721 and WITP79264 for additional information on this event. Event Id 1054 Windows 2008 R2 This error was also reported by users that installed a personal firewall on their computer (i.e.

x 221 Rob Lamb I found that my pc was connected to an older switch, and it wasn't receiving its group policies correctly. navigate here Because each processor maintains its own TSC and these counters are not sychronized with one another, QueryPerformanceCounter may return inconsistent results. 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. To verify that the domain controller can be contacted through Domain Name System (DNS), try to access \\\sysvol\, where is the fully qualified DNS name of your domain. Event Id 1054 Group Policy Windows 2008 R2

Want to Advertise Here? Stats Reported 7 years ago 11 Comments 21,343 Views Other sources for 1054 Microsoft-Windows-GroupPolicy Software Licensing Service DhcpServer Trend Micro Security Server Server Administrator NetDocuments Local Document Server flcdlock Others from So far this problem only happenning to this type of laptop with Broadcom gigabits nic. From a newsgroup post: "All computers must point to the DS for DNS resolution.

I had to delete zone and recreate the reverse lookup zone manually. Event Id 1054 Server 2012 Group Policy settings cannot be applied until the problem is fixed. What is the role of Userenv? -- Paul Bergson MVP - Directory Services MCITP: Enterprise Administrator MCTS, MCT, MCSE, MCSA, Security+, BS CSci 2008, Vista, 2003, 2000 (Early Achiever), NT4 Twitter @pbbergs Please no

So any more idea for this problem? After disabling this item in the network card properties, all these errors were gone. Since then I have been working to deploy XenDesktop 5 in a small environment with only 2 virt… Windows XP Be "Registry cleaner" of yourself! Windows Could Not Obtain The Name Of A Domain Controller Server 2012 so if to try different nic, i will call the tech support first.

It appeared right after I changed a Domain. Introduction: Always remember: A Clean registry = Better performance = Save your invaluable time In this article we're going to clear our registry manually! We appreciate your feedback. this contact form 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

After applying the policy without blocking ICMP, everything started working again. Netherlands 8. This problem is related to the initialization rate on the NIC vs. I and also seen this when the domains ntp server is unable to find its external time source so PCs stop synching time with the server.

Yes, manually! x 2 Anonymous In our particular environment we had a 2003/XP computer separated from the 2003 DC over a VPN. 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 First But the ability to create custom scanning profiles al… Document Imaging Document Management OCR Images and Photos Photos / Graphics Software How to Send a Secure eFax Video by: j2 Global

Are you an IT Pro? GPO is working fine for other the same network, DC, DNS environment. This posting is provided "AS IS" with no warranties, and confers no rights. Event ID: 1054 Source: Userenv Type: Error Description: Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted).

As the PC boots, some NICs perform a reset, which also forces the switch port to reset. There is a windows update specific to this issue that may correct this and or links to the utility at UNC-names were resolved right, but I could not search the network environment. Windows 2000 is generally more robust in this respect.