I was able to resolve the launch delay issue by changing the IP Address in my DNS for the old retired server to one of my new domain controllers. If you have any sort of multi-core or multi-processor system, have your server ping itself. Join our community for more solutions or to ask questions. The problem can be caused by having an invalid or unreachable Preferred DNS server address in the Internet Protocol (TCP/IP) Properties. http://discusswire.com/event-id/event-id-1054-group-policy.html
Canada 5. But it does not hold any responsibility. This can be beneficial to other community members reading the thread. Is the behavior consistent? https://support.microsoft.com/en-us/kb/324174
Then stop logon service, flush DNS and register DNS again with IPCONFIG /registerDNS". Currentlly I am a Administrator for Viettel group's LAN office, and user a domain server with win server 2008 r2 OS. The solution I came up with was to include “localhost” (127.0.0.1) to be a trusted IP on both machines.
Powered by WordPress. All DNS settings were correct, and NIC drivers updated. x 2 Anonymous I was running ZoneAlarm and it had denied access to the Windows Logon Module. Event Id 1054 Dns UNC-names were resolved right, but I could not search the network environment.
Texas 5. Event Id 1054 Error Code 58 Marked as answer by Sal-IT Thursday, November 04, 2010 3:51 AM Thursday, October 28, 2010 10:16 AM Reply | Quote Moderator 0 Sign in to vote Hello, Finnaly i have resolved 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. Copyright © 2006 - 2014, JustSkins.com 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
If you allow ICMP-traffic for the local network (or just the DC), the error will go away. useful source Thanks, Guy Thursday, October 28, 2010 5:08 AM Reply | Quote 0 Sign in to vote Hey guy, i just ran gprsult gpresult INFO: The policy object does not exist. Event Id 1054 Cannot Obtain The Domain Controller Name Thanks 0 LVL 6 Overall: Level 6 Windows XP 6 Message Expert Comment by:Antunb2006-04-17 its like it loses its membership info, but not really because the machine still does everything Event Id 1054 Windows 2008 R2 Windows XP records Event ID 1054 in the Application event log - 'Windows cannot obtain the domain controller name for your computer network'?
x 207 Anonymous In my case, this was caused by the firewall on my WinXP machine. his comment is here x 2 Anonymous I had the same error message on my Windows XP client. x 6 Dave B I have this problem with a Wireless LAN card. l At the command prompt, type gpupdate, and then check Event Viewer to see if the Userenv 1054 event is logged again. Event Id 1054 Group Policy Windows 2008 R2
Covered by US Patent. This firewall was blocking all the connections via 127.0.0.1, so the Netlogon service was not able to communicate. Any solution that works? http://discusswire.com/event-id/event-id-11-disk-controller-error.html If not, there are processes to manually remove a DC from your domain if replication can't be fixed, but it will require you to rebuild the second DC since you won't
DNS settings is correct, w2k client has no problem. 2) 15 minutes lan work fine, after this time lan is down, with "Access denied" for all remote resources, not for connected Event Id 1054 On Domain Controller Go to Command Prompt --> Copy Paste the below lines cd /d %windir%\system32 regsvr32 /n /I userenv.dll cd wbem mofcomp scersop.mof gpupdate /force gpresult I did this on the DC. Changed the File System of "C:\" from FAT32 to NTFS (wanted to do this on this machine for a long time, so even if it may have nothing to do with
Current, only a few of them are actualy loading the group policy from the DC (Windows 2003 std + latest updates) This is the error that appears on the XP SP3 A race condition may occur between the TCP/IP protocol and the network adaptor driver when they try to register with the Microsoft Network Driver Interface Specification (NDIS). I have a very small Windows Domain in my house. Event Id 1054 Server 2012 i have a problems: 1) Domain is not found with error 1054 by UserEnv in windows xp application log.
Thursday, October 28, 2010 5:33 AM Reply | Quote 2 Sign in to vote Hi, According to my research, this issue also can be caused by the slow link detection. This behavior may occur if the address for the configured preferred DNS server on the client is invalid or unreachable. Monday, August 06, 2012 7:12 AM Reply | Quote 0 Sign in to vote Hi All I am also having same issue mentioned by Ngobinh. http://discusswire.com/event-id/the-dns-server-encountered-an-invalid-domain-name-in-a-packet-from-the-packet-will-be-rejected.html Most switches will run the Spanning Tree Protocol (STP) to detect network loops and shut down any ports with a loop.
Guest July 5th,05:33 AM #2 Re: Windows cannot obtain the domain controller name (userenv, id = 1054) For the first problem, try to take a look at: http://www.eventid.net/display.asp?eventid=1054&eventno=1393&source=Usere nv&phase=1 Hope that JoinAFCOMfor the best data centerinsights. Same problem.. Regards, Arthur Li TechNet Subscriber Support in forum If you have any feedback on our support, please contact [email protected] remember to click â€śMark as Answerâ€ť on the post that helps
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 x 97 Anonymous In my case, this problem occurred because a traditional ping between this server and the DC was stopped by the firewall. The machines which are on the local network subnet 192.168.1.* load the group policy fine as they are in the same building. I think that kerberous or/and ipsec problem.
thanks david Wednesday, October 27, 2010 10:13 PM Reply | Quote 0 Sign in to vote Hi, When you run gpresult, which DC is listed at the top? 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 1 Jeff Thomes ME326152 refers you to ME239924 to disable DHCP Media Sensing in the registry. x 1 Anonymous Also had this problem on machines with Gigabit NICs.
Theme by Press Customizr.