Home > Event Id > Event Id 1054 Group Policy Windows 2008 R2

Event Id 1054 Group Policy Windows 2008 R2

Contents

It passed. I checked application event log and found event id 1054. Then stop logon service, flush DNS and register DNS again with IPCONFIG /registerDNS". The card doesn't support Zero Configuration and the NIC software doesn't load until after logon so it cannot connect to the DC until after the logon to the local workstation. navigate here

Your pings should look normal now and the 1054 errors every 5 minutes will go away. I opened up ICMP on my firewall between the dmz (demilitarized zone) and the domain controllers and the group policy was able to apply. 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 Edited November 14, 2005 by cluberti 0 Share this post Link to post Share on other sites joeadmin    0 0 1 post September 21, 2007 Posted September 21, 2007 If https://support.microsoft.com/en-us/kb/324174

Event Id 1054 Group Policy Windows 2008 R2

x 2 Greg In my case, this error occurred on a domain with 2 servers, one with Win2k and the other one with Windows 2003. In our case, the problem occured due to Group Policy settings pulled across a VPN. After allot of research that day i figured out that it had a virus.

  1. Creating your account only takes a few minutes.
  2. There are time related errors on the client though "The time provider NtpClient was unable to find a domain controller to use as a time source.
  3. On another PC with the same problem, I just gave the user admin privileges for the next login and the problem was solved under normal privileges as well.

x 207 Anonymous In my case, this was caused by the firewall on my WinXP machine. Se ha anulado el proceso de directiva de grupo.

Jul 26, 2011 Windows ne peut pas obtenir le nom du contrôleur de domaine pour votre réseau. (Le domaine spécifié n'existe pas Chipotle Feb 27, 2012 jackofall_masterofnone Manufacturing, 1-50 Employees Mine was outdated NIC drivers Jalapeno Jan 29, 2013 Just Me Entertainment, 101-250 Employees I have seen and corrected this problem on computers Event Id 1054 Error Code 58 ZoneAlarm) without configuring it properly (so the firewall blocked the access to the domain controller).

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 Event Id 1054 Windows 2008 R2 Because each processor maintains its own TSC and these counters are not sychronized with one another, QueryPerformanceCounter may return inconsistent results. Something odd was happening in the DNS configuration. https://social.technet.microsoft.com/Forums/windowsserver/en-US/e8ebc1af-146a-412a-bb99-d1942311bb26/event-id-1054-windows-cannot-obtain-the-domain-controller-name?forum=winserverGP Maybe it was because the Switch was too cheap.

Guy Friday, October 30, 2009 5:01 PM Reply | Quote 0 Sign in to vote Guy,1. Event Id 1054 Server 2012 Sponsored Links Alexey 4. This event occurred together with Event ID 14 from source W32Time, Event ID 29 from source W32Time and Event ID 5719 from source NETLOGON. Took PC out of domain and deleted the computer account there. 2.

Event Id 1054 Windows 2008 R2

x 2 Anonymous In our particular environment we had a 2003/XP computer separated from the 2003 DC over a VPN. https://support.microsoft.com/en-us/kb/938448 Repeat this command several times. Event Id 1054 Group Policy Windows 2008 R2 The problem occurs because link status fluctuates as the network adapter (also known as the network interface card, or NIC) driver initializes and as the network adapter hardware negotiates a link Event 1054 Group Policy All rights reserved.Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks|Site Feedback TechNet Products IT Resources Downloads Training Support Products Windows Windows Server System Center Browser   Office Office 365 Exchange Server   SQL Server

Wonder if it's worth locking the NIC at 100MB. check over here Group Policy Processing aborted. GPO is working fine for other desktops...in the same network, DC, DNS environment. I'd bet that would have some very salient information during the failure time periods.Also, you could enable logging on the userenv errors by adding the following to your registry:Key: HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinlogonValue: Event Id 1054 Dns

About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up 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 Plugged into a new switch and the problem was solved. his comment is here Privacy Policy Site Map Support Terms of Use Jump to content Primary Secondary Strawberry Orange Banana Lime Aqua Slate Sky Blueberry Grape Watermelon Chocolate Marble Strawberry Orange Banana Lime Aqua Slate

Are you an IT Pro? Windows Could Not Obtain The Name Of A Domain Controller Server 2012 Nuo Guest July 5th,08:04 AM #3 Re: Windows cannot obtain the domain controller name (userenv, id = 1054) Thanks for attention. This means the spanning tree cycle is never initiated.

XP did not apply group policy until I stopped the IPSec service.

Finally, you mention that some policies are being applied. See TB727055 - "Troubleshooting Common Active Directory Setup Issues in Windows 2000" and ME237675 - "Setting Up the Domain Name System for Active Directory". I have checked permissions and all look fine. Event Id 5719 The weird part was that the GPO settings seemed to be ok, it was just that the software wouldn't install.

When I changed the subnet of the location where the problem computers are in, to a different Active Directory site, it works ok. This behavior can occur if you have not started the Netlogon service. My workstations could not find a DC through DNS and my DNS was not dynamically updating its SRV records. weblink The only thing i can think of is that my nic hasn't finished initializing.

Group Policy processing aborted.

Jun 24, 2009 Windows cannot obtain the domain controller name for your computer network. (A socket operation was attempted to an unreachable host. ). We found the following page: AMD Opteron Processor Utilities and Updates. Group Policy processing aborted. the fast load of the OS.

CONTINUE READING Join & Write a Comment Already a member? The solution was to disable slow link detection on the DC. Group Policy settings cannot be applied until the problem is fixed". On most switches, this takes about 30 seconds after starting STP initialization.