I have look at support.microsoft.com/kb/326152/en-us, it doesn't solving this problem. At the command prompt, type gpupdate, and then check Event Viewer to see if the Userenv 1054 event is logged again. Join Now For immediate help use Live now! 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. click site
All rights reserved. The only thing i can think of is that my nic hasn't finished initializing. 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. Anyone got any ideas?Cheers in advance,Molenski RE: event id 1054 userenv Windows cannot obtain the domain controller name itsp1965 (IS/IT--Management) 22 Sep 11 09:56 Have you tried DCDIAG and NETDIAG to
x 1 Jeff Thomes ME326152 refers you to ME239924 to disable DHCP Media Sensing in the registry. Join the IT Network or Login. Close Box Join Tek-Tips Today! Andy GoodmanSBS-MVP, MCP, MSA Small Buiness Specialistfor SBS reated tips see www.SBS-Rocks.com (in reply to Bif) Post #: 8 RE: Constant event 1054 errors on SBS2003 - 13.Mar.2006 7:43:35 PM
Setting the registry key “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\DisableDHCPMediaSense” to “1” as per ME239924 solved it. 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. Combofix, fixed the issue then i was able to re-add it to the domain. Event Id 1054 Dns 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
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 The solution I came up with was to include “localhost” (127.0.0.1) to be a trusted IP on both machines. See TB727055 - "Troubleshooting Common Active Directory Setup Issues in Windows 2000" and ME237675 - "Setting Up the Domain Name System for Active Directory". https://support.microsoft.com/en-us/kb/326152 Solved Userenv Event ID 1054, Windows cannot obtain the domain controller name for your computer netowkr.
MSPAnswers.com Resource site for Managed Service Providers. Event Id 1054 Server 2012 x 2 Mark Casemore I was having this problem on a Win2k3 member server using a static IP address. At the command prompt, type gpupdate, and then check Event Viewer to see if the Userenv 1054 event is logged again. 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.
Used Novell servers back then so not much experience on MS servers. https://community.spiceworks.com/windows_event/show/49-userenv-1054 Turned off media sensing (have 2 gigabit nics in the server). Event Id 1054 Group Policy Windows 2008 R2 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 Event 1054 Group Policy 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
w2k client - no problem How resolve this problems? get redirected here What this does is disable the Windows XP Fast Logon Optimization, which causes XP to check cache credentials for logon information and does not wait for the network state to be JSI Tip 7919. Gpresult said that the GPO that contains the login-script was applied. Event Id 1054 Group Policy Error Code 58
See Dell Support Forum for more details. Since I was not using IPSec I changed this on the server and solved the problem. x 2 Anonymous In our particular environment we had a 2003/XP computer separated from the 2003 DC over a VPN. navigate to this website This error was among several.
The reason you do not see a problem with all NICs is because some never perform a reset. Windows Cannot Obtain The Domain Controller Name Server 2003 See MSW2KDB for more information about this event. I used Group Policy Object Editor (Gpedit.msc) to modify "Group Policy slow link detection" on the server at both "Computer Configuration\Administrative Templates\System\Group Policy" and "User Configuration\Administrative Templates\System\Group Policy".
x 2 Anonymous I had this problem on two Win2k3 member servers and resolved it by disjoining the domain, then re-joining the domain. Those errors usually have to be resolved before Group Policy processing can continue. x 3 Anonymous The problem is not with the NIC or DNS, but rather with the Microsoft XP OS. Windows Could Not Obtain The Name Of A Domain Controller Server 2012 This scenario might work for some.
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 This laptop is geting DHCP ip and DNS registered on server. Check to see whether other computers on your network are having the same problem. http://wx2me.com/event-id/server-2003-vss-error-7001.php 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
Red Flag This Post Please let us know here why this post is inappropriate. x 199 Anonymous In my case, this problem was caused by the "AEGIS Protocol (IEEE 802.1x) v 220.127.116.11" driver that was probably installed together with the ASUS WLAN driver. Here's Why Members Love Tek-Tips Forums: Talk To Other Members Notification Of Responses To Questions Favorite Forums One Click Access Keyword Search Of All Posts, And More... Hints have 13 listed, a-m Deleting the dns cache...
The error was caused by Norton Internet Security, which is installed on both. x 2 Anonymous I had this error on several laptops, Dell Latitude C600, they were not processing group policy for software installation.