Home > Event Id > 1054 Event Id Error

1054 Event Id Error

Contents

Experts Exchange Advertise Here 884 members asked questions and received personalized solutions in the past 7 days. Maybe it was because the Switch was too cheap. The problem can be caused by having an invalid or unreachable Preferred DNS server address in the Internet Protocol (TCP/IP) Properties. This could be caused by a name resolution failure. have a peek here

I don't see any other relevant errors in the event logs. x 1 Anonymous If you're using DHCP, make sure the DNS Server option (006) is set in your scope options. The client did not have a profile in Document and Settings. See ME816045 for information on how to change the default setting (2048 bytes) in system registry. https://technet.microsoft.com/en-us/library/cc727331(v=ws.10).aspx

Event Id 1030 1054

so if to try different nic, i will call the tech support first. 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 From a newsgroup post: "I solved the problem. Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry.

Your logon process may also be very slow. Thanks. 0 LVL 77 Overall: Level 77 Windows XP 17 Message Active 2 days ago Accepted Solution by:Rob Williams2006-04-17 Seems this most often occurs when the network connection fails or Because each processor maintains its own TSC and these counters are not sychronized with one another, QueryPerformanceCounter may return inconsistent results. Event Id 1054 Dns If the TCP/IP protocol registers with NDIS before the network adaptor driver, for a short time it prompts higher user mode networking components that network connectivity is not available.

This means the spanning tree cycle is never initiated. Helped anyway. If you allow ICMP-traffic for the local network (or just the DC), the error will go away. https://social.technet.microsoft.com/Forums/office/en-US/4061ae7b-b692-4df4-bcca-95a7c8c86330/gpupdate-fails-event-id-1054-windows-could-not-obtain-the-name-of-a-domain-controller?forum=winserverGP Click All Programs and then click Accessories.

x 105 Anonymous In our case, the problem was in the limitation of the ICMP packet size to less then 2048 bytes by our ISP. Event Id 1054 Group Policy I have look at support.microsoft.com/kb/326152/en-us, it doesn't solving this problem. Your Windows Server 2003 domain controller System event log records event ID 5774? 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.

Event Id 1053 1054

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 Group Policy Processing aborted. Event Id 1030 1054 I thought that was dynamic, but apparently not. Event Id 1054 Userenv Thanks in advance 0 LVL 6 Overall: Level 6 Windows XP 6 Message Expert Comment by:Antunb2006-04-17 take it off the domain add it to a workgroup reboot then add it

Each return all three DCs, and thecorrect IP addresses,when queried for _ldap._tcp.dc._msdcs.domainname. http://rlegsoftware.com/event-id/140-dns-error-event-id.php This could be caused by a name resolution failure. Windows XP records Event ID 1054 in the Application event log - 'Windows cannot obtain the domain controller name for your computer network'? Group Policy Infrastructure Group Policy Group Policy Preprocessing (Security) Group Policy Preprocessing (Security) Event ID 1054 Event ID 1054 Event ID 1054 Event ID 1052 Event ID 1053 Event ID 1054 Event Id 1054 Userenv Windows Xp

If this is the case, I would recommend proceeding like that: Make sure that each DC has only one IP address in use and ONLY one NIC card enabled (Other NICs x 97 Anonymous In my case, this problem occurred because a traditional ping between this server and the DC was stopped by the firewall. This is a Win7 x86 client on a domain with three 2008/2008R2 DCs. Check This Out Windows could not obtain the name of a domain controller.

Why? Event Id 1054 Group Policy Windows 2008 This problem is related to the initialization rate on the NIC vs. If spanning tree is enabled it will take a minimum of 30 seconds before that port is capable of traffic.

x 199 Anonymous On our server, I removed the logon script in the GPO and this fixed the problem.

User policy could not be updated successfully. I have several HP Proliant DL 385 G2 as AD\GC\DNS. Featured Post The Complete Ruby on Rails Developer Course Promoted by Experts Exchange Ruby on Rails is one of the most popular web development frameworks, and a useful tool used by Event Id 1054 Source Userenv So far this problem only happenning to this type of laptop with Broadcom gigabits nic.

This could be caused by a name resolution failure. read more... 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 this contact form Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System] "GroupPolicyMinTransferRate"=dword:00000000 This has reduced the frequency of the errors to a few times a day and the GPO seems to be updating correctly.

The reason you do not see a problem with all NICs is because some never perform a reset. x 1 Anonymous Also had this problem on machines with Gigabit NICs. Group Policy processing aborted. We appreciate your feedback.