At which time I've stopped/restarted the netlogon service, as well as registering the DNS again. I tried 'gpupdate /force' and the eventid in the title appeared in the event log. If the issue persists, please briefly describe the configuration of the group policy which failed to apply on client. x 4 Peter Hayden - Error: "A socket operation was attempted to an unreachable host" - In one case, this Event ID appeared at boot up on a computer running on useful reference
I will let you know in the morning if this is a go - thank you :-) 0 Mace OP Martin9700 May 18, 2009 at 4:12 UTC Take Join & Ask a Question Need Help in Real-Time? If the issue persists, please briefly describe the configuration of the group policy which failed to apply on client. Get 1:1 Help Now Advertise Here Enjoyed your answer?
Something really odd was happening in the DNS configuration. Go to Solution 4 Comments LVL 18 Overall: Level 18 Active Directory 17 Windows Server 2003 9 Windows Networking 3 Message Assisted Solution by:sarang_tinguria2012-09-13 check DNS setting on that machine x 5 Anonymous In my case, increasing the Kerberos Token size worked on my W2K3 standard server. The problem was corrected by updating the Intel Gigabit NIC driver on the server.
If it isn't than that's your problem. I'm going to take a look at the two other links and see if they help. Verify that you can access the domain controller by using tools such as the Active Directory Users and Computers snap-in. 4. Windows Cannot Determine The User Or Computer Name 1326 The PC had internet connectivity but was not able to authenticate with the domain and therefore was not able to access network resources.
x 70 Rafael Castro I found this problem in a network which lost performance every time this event occurred. In my case, this was happening for roaming notebook users when they were not connected to the domain in the office. I had a set of backup servers (ghost images of the live servers) so I booted them up and conneted my laptop to them. https://support.microsoft.com/en-us/kb/937535 Once I replaced the missing "wkssvc.dll" file by copying it from another XP (Professional) machine and rebooted all went back to normal.
Group Policy processing aborted.) After trying rejoining the domain and checking OU etc, I called Microsoft. Windows Cannot Determine The User Or Computer Name Access Is Denied If any error is showed in the event log, please paste the whole event here for research. Solved Event 1053 Userenv error Posted on 2012-09-13 Active Directory Windows Server 2003 Windows Networking 3 Verified Solutions 4 Comments 2,956 Views Last Modified: 2012-09-17 Hello - we have a server It turned out that the application needed to have the Windows task jobs recreated to fix the jobs problem, and then the User event error went away after running Sysprep, and
The issue turned out to be slow link detection with the domain controllers. http://www.eventid.net/display-eventid-1053-source-Userenv-eventno-1584-phase-1.htm Same error.That should have fixed it if it were a corrupt DNS table, but it didn't, so I'm not sure where to go from here. Windows Cannot Determine The User Or Computer Name Server 2003 x 8 Alex Rogachevsky This error was showing up on our Windows XP clients; users were not able to authenticate in the 2003 AD domain. Event Id 1053 Group Policy x 5 Craig Curtis Error: "The specified user does not exist" (Error code 1317) -Verify the DNS Settings.
How does Windows determine computer names? Login. How does Windows determine user names? http://introbuilder.net/windows-cannot/windows-xp-userenv-error.php x 128 Anonymous This happened on two different Win XP Pro SP3 computers.
x 149 Martin P. Windows Cannot Determine The Computer Name. (access Is Denied. ) I deleted all the GPOs (most were for testing purposes anyway) I had, did a gpupdate /force and the problem disappeared, group policy applies fine now on all the workstations. x 4 Mike Pastore We received this event along with event 40960, 40961, and 1219 in the application log.
If any error is received, please fix it first. 4. Privacy statement © 2016 Microsoft. This can be beneficial to other community members reading the thread. Windows Cannot Determine The User Or Computer Name. The System Detected A Possible Attempt 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. 5.
Join Now For immediate help use Live now! Thank you for your efforts. 0 Featured Post How your wiki can always stay up-to-date Promoted by Quip, Inc Quip doubles as a “living” wiki and a project management tool that What is the role of Userenv? http://introbuilder.net/windows-cannot/windows-xp-userenv-error-1030.php x 4 Anonymous We got this error every 5 minutes after we changed the DNS entry for the server.
I disabled lmhost and netbui over tcp/ip." Error: "The specified domain either does not exist or could not be contacted" (Error code 1355) - From a newsgroup post: "Make sure that AD will not work otherwise. When I put the server's switch port into portfast mode on my Cisco 6500 series switch, the issue was resolved". With this registry key set to 2 only administrators can log on to the DC.
Marked as answer by Nina Liu - MSFTModerator Friday, May 06, 2011 3:34 AM Thursday, April 14, 2011 9:08 AM Reply | Quote Moderator All replies 0 Sign in to vote As you finish projects in Quip, the work remains, easily accessible to all team members, new and old. - Increase transparency - Onboard new hires faster - Access from mobile/offline Try See ME277741 for details on how to do that. Beside that I reconfigured our login script (changed the users home directory and our folder redirection group policies from dns-unc-shares to ip-unc-shares as a temporary workaround).
Return value (1317)", on Windows 2000 servers, and event ID 1053 (Userenv) with message "Windows cannot determine the user or computer name. (The specified user does not exist). Join & Write a Comment Already a member? Follow any responses to this post through RSS 2.0. x 113 John Currie In my case it was the "Receive Side Window Scaling" issue that crops up with Windows Server 2003 SP2 & Broadcom NICs.
Group Policy settings cannot be applied until the problem is fixed. This will occur if your DNS server is unable to resolve information about your domain. Covered by US Patent.