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 This means the spanning tree cycle is never initiated. 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 x 184 Anonymous In my case, I resolved this by updating the network card driver to the latest version, despite the fact that I had done that only 3 months ago. have a peek here
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 Applied new SID to the PC. 3. Also, when i log into the client xp machine with Administrator on the local machine, gpresult works, if i log in with the user account, gpresult does not. Join the IT Network or Login.
The reboot is very important!!!! l Check to see whether other computers on your network are having the same problem. l At the command prompt, type gpupdate, and then check Event Viewer to see if the Userenv 1054 event is logged again. Share Flag This conversation is currently closed to new comments. 13 total posts (Page 1 of 2) 01 | 02 Next + Follow this Discussion · | Thread display:
x 1 Anonymous In my case, ZoneAlarm (personal firewall software) caused this problem. XP did not apply group policy until I stopped the IPSec service. 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. Event Id 1054 Error Code 58 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
It has to be the firewall on the DC 0 LVL 3 Overall: Level 3 Windows Server 2008 1 Active Directory 1 MS Server OS 1 Message Accepted Solution by:msincorp Join the community of 500,000 technology professionals and ask your questions. Set the /usepmtimer switch in boot.ini and reboot the system. if I think of anything else I'll post. 0 Message Author Comment by:Sleestack90 ID: 341226922010-11-12 There were rules in the Windows firewall settings that could not be deleted.
This can be beneficial to other community members reading the thread. Windows Cannot Obtain The Domain Controller Name For Your Computer Network 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. any ideas? Some of the XP (All have latest updates)machines load the group policy sucessfully, butothers do not.
The client must be pointing at this server. If you are not a registered user on Windows IT Pro, click Register. Event Id 1054 Cannot Obtain The Domain Controller Name Login Join Community Windows Events Userenv Ask Question Answer Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Event 1054 Event Id 1054 Windows 2012 x 2 Anonymous I had this problem on two Win2k3 member servers and resolved it by disjoining the domain, then re-joining the domain.
Solved Userenv Event ID 1054, Windows cannot obtain the domain controller name for your computer netowkr. navigate here Joined the domain again & rebooted properly. 5. I've seen this behavior when AD DNS is not set up correctly. There is another DC, both on subnet 192.168.1.*. Event Id 1054 Group Policy Windows 2008 R2
Wednesday, November 03, 2010 4:33 AM Reply | Quote Moderator 0 Sign in to vote Hello, Currently i am still having issues. Can't imagine too many users needing Gigabit. Please also run the command: ipconfig /all on a problematic and a good Windows XP client, and then post the outputs. Check This Out x 3 EventID.Net See the link to ME291382 for DNS troubleshooting.
Since I was not using IPSec I changed this on the server and solved the problem. Windows Could Not Obtain The Name Of A Domain Controller Server 2012 Group Policy settings cannot be applied until the problem is fixed. Register Now Question has a verified solution.
The problem was caused by the fact that the server's NIC was configured for IPSec. Something odd was happening in the DNS configuration. The Group Policy application stack executes before the negotiation process is completed and can fail because of the absence of a valid link." See ME326152. Event Id 5719 thank so much!
I can ping the domain without difficulty and access sysvol no problem. We would like to check if there are any network connectivity issue. You suggestion re-joined domain, I have done that with static IP or DHCP configuration. this contact form Right-click Local Area Connection, and then click Properties.
I also set each NIC to 1000\FULL. Windows XP records Event ID 1054 in the Application event log - 'Windows cannot obtain the domain controller name for your computer network'? We would like to check if there are any network connectivity issue. Group Policy settings cannot be applied until the problem is fixed".
Regards,Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. On most switches, this takes about 30 seconds after starting STP initialization. It appears that at some point in the conversation, the client computer trys to send an ICMP packet of 2048 bytes. On the other hand rejoining solves the problem (thanks to MikeRuralElectric).
Some machines may have been cloned in the past (while i was not with the organisation), so i ran newsid and changed the sides on all the client machines. I checked application event log and found event id 1054. Jun 11, 2002 Jerold Schulman | Windows IT Pro EMAIL Tweet Comments 0 Advertisement Your Windows XP Application event log contains: Event ID: 1054 Source: Userenv Type: Error Description: Windows cannot let me see if I understand.
In our case, the problem occured due to Group Policy settings pulled across a VPN. Serrano Mar 15, 2011 ipcm Manufacturing, 101-250 Employees Sometimes just check the cables like i do. There is a windows update specific to this issue that may correct this and or links to the utility at http://developer.amd.com/wordpress/media/2012/10/TSC_Dual-Core_Utility.pdf.