Home > Event Id > Event Id 1054 Server

Event Id 1054 Server


x 199 Anonymous On our server, I removed the logon script in the GPO and this fixed the problem. The reason you do not see a problem with all NICs is because some never perform a reset. Another workaround is to add the "/usepmtimer" switch to boot.ini. All rights reserved. http://qaisoftware.com/event-id/ms-event-id-1054.html

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. Installing an update driver from Intel resolves this or hacking the registry in this area. Thai Pepper Apr 21, 2010 Stephen5797 Manufacturing, 101-250 Employees @ATScuba - Try re-creating the user profile and disjoining/re-joining the PC to the network. 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 visit

Event Id 1054 Windows 2008 R2

If the DC is multihomed, numerous issues can result, too long to list. I had the client log on locally (which created the profile), then logged off, had him RDP then of course it loaded the temp profile but this time go to system You’ll be auto redirected in 1 second.

On the "Adapters and Bindings" tab, in the connections list, select the NIC that the clients use to connect to the server and move it to the top of the list. 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? UNC-names were resolved right, but I could not search the network environment. Event Id 1054 Windows 2012 Multihomed DCs.

Verify your Domain Name System (DNS) is configured and working correctly. Event Id 1054 Cannot Obtain The Domain Controller Name Joined the domain again & rebooted properly. 5. Folder redirection or computer Policies i.e. This problem has appeared to all of my machines with Gigabit NICs.

There are a number of reasons this event may occur, no matter which Source Name its related to. Event Id 1054 Group Policy Windows 2012 Upcoming Training Jan 19:Deploying Windows 10 OS using Microsoft Deployment Toolkit with Mikael Nyström Jan 24:Hyper Convergence 3.0 with Alan Sugano Jan 25:Crunching Big Data with Apache Spark with Sasha Goldshtein 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. You will be looking for the domain controllers to respond to this query.

Event Id 1054 Cannot Obtain The Domain Controller Name

x 209 Angie Bates We have an AMD Opteron dual core system that was recording this event every 5-10 minutes. 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 Group Policy Processing aborted. Event Id 1054 Windows 2008 R2 It probably wouldn't hurt to check them for goofy ping times and apply this fix as needed. Event Id 1054 Group Policy Windows 2008 R2 How can I figure out why GPUpdate can't find a DC?

It was found the AMD Opeteron processor has timing issue. http://qaisoftware.com/event-id/1054-event-id-group-policy.html This could be caused by a name resolution failure. I have done the gpupdate command - and don't get any additional events logged - and I can access sysvol (\\mydomain.com\sysvol\mydomain.com) Not a large network - one DC and all machines Attend this month’s webinar to learn more. Event Id 1054 Error Code 58

  1. Windows could not obtain the name of a domain controller.
  2. x 215 Galadmin Another resolution using the /usepmtimer switch, as others have posted, see ME895980: "This problem occurs when the computer has the AMD Cool'n'Quiet technology (AMD dual cores) enabled in
  3. The Group Policy application stack executes before the negotiation process is completed and can fail because of the absence of a valid link. * Possible Resolutions: Resolution 1: To resolve problem
  4. To fix the problem, I stopped the firewall and I restarted the Netlogon service.
  5. Then finally, the GPO was applied just as for the other PCs.

Wonder if it's worth locking the NIC at 100MB. x 217 Anonymous I initially fixed this by using the solution proposed by Christophe Derdeyn, but I have since found a more complete solution that addresses the underlying fault. It solved the GPO script installation problem, but the machine still cannot found the DC on startup. have a peek here Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe.

Other available timers include the PM_Timer and the High Precision Event Timer (HPET)." x 228 LH We had a Windows 2003 as PDC which was not able to even find himself. Windows Could Not Obtain The Name Of A Domain Controller Server 2012 This scenario might work for some. If you're new to the TechRepublic Forums, please read our TechRepublic Forums FAQ.

I had the 1054 Userenv event every 5 minutes.

Using a DNS address that doesn't have the AD zone data. User policy could not be updated successfully. x 1 Anonymous In my case, ZoneAlarm (personal firewall software) caused this problem. Windows Cannot Obtain The Domain Controller Name For Your Computer Network On most switches, this takes about 30 seconds after starting STP initialization.

Covered by US Patent. 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). On the other hand rejoining solves the problem (thanks to MikeRuralElectric). Check This Out Iam sure you will see resolution errors.

x 2 Anonymous I had the same error message on my Windows XP client. Now that we upped the maximum ICMP packet size to 2048 and rebooted the client machine, the group policies process fine.