Error 1053 Windows Cannot Determine The User Or Computer Name
Contents |
additional information might be available elsewhere. Thank you for searching on this message; your search helps us identify those windows cannot determine the computer name 1055 areas for which we need to provide more information. If the product or version you are looking for is not listed, you can use this search box to search TechNet, the Microsoft Knowledge Base, and TechNet Blogs for more information. Enter the product name, event source, and event ID. For example: Vista Application Error 1001.
your account only takes a few minutes. Join Now I had a user this morning try to log into her machine and noticed after a few reboots that she was not being logged into the network - event id 1053 userenv So what I have done is I renamed the computer - unjoined the domain then
Event Id 1053 Group Policy
rejoined the domain - restarted - and I still get the same error message -- Check my dns and see the file for
Windows Cannot Determine The User Or Computer Name 1326
the new manchine name, i renamed the machine thinking the dns could have gotten corrupt.. No server updates have been done... I have done gpupdate /force and still can not connect to the network Reply Subscribe RELATED http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=1053&EvtSrc=Userenv&LCID=1033 TOPICS: Error 1053 when trying to run a windows servicee Help, SW Error 1053. Computer Name   13 Replies Poblano OP Shadowwyrm May 18, 2009 at 2:34 UTC Unjoin from the domain, restart, then check the machine name. Then check active directory to make sure the machine's name is no longer listed in the Computers list. If so, delete it. Then rejoin the domain. If the problem persists, rejoin the domain with a slightly https://community.spiceworks.com/topic/38164-error-1053-windows-cannot-determine-the-user-or-computer-name different computer name 0 Poblano OP Melman May 18, 2009 at 3:09 UTC Did that - no go - same error 0 Poblano OP Shadowwyrm May 18, 2009 at 3:14 UTC I suppose the next question would be, how large is your network? If you're checking for the computer name on a Primary Domain controller, and the user is logging in on a subnet at a different site, make sure the domain controller at the user's site shows that the computer name has been deleted there. I've seen replication take up to half an hour depending on health of the domain and the quality of the copper between sites. If it's a single location, however, I'll have to admit I'm stumped, unless you have multiple subnets and DCs in the one location. 0 Poblano OP Melman May 18, 2009 at 3:17 UTC What I am going to do is log off and have it sit over night -- this is a single location I guess I just need to be patient and wait for replication to take effect. 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 it out of the domain, reboot. Rename it, reboot. Rejoin the d
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom views/filters Servers list, organized in http://www.eventid.net/display-eventid-1053-source-Userenv-eventno-1584-phase-1.htm groups Integration with EventID.Net Consolidated view for all logs Free for subscribers Event ID: 1053 Source: Userenv Source: Userenv Type: Error Description:Windows cannot determine the user or computer name. (
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Event 1053 Userenv error Want to Advertise Here? Solved Event 1053 Userenv error Posted on 2012-09-13 Active Directory Windows Server 2003 Windows Networking 3 Verified Solutions 4 Comments 2,895 Views Last Modified: 2012-09-17 Hello - we have a server that was recently DCPROMO demoted from a DC, down to a member server, and has successfully been reconnected and rejoined to the same domain on our network. We have several applications on the machine that are working, except for one application that runs unattended jobs in Windows 2003 Server, that appears to have trouble now. I don't see any errors related to the application jobs, however, but am having to run these job tasks manually to get them done. The main error I see is this one below: Event Id 1053 Userenv User=NT AUTHORITY\SYSTEM Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. I don't know if this is the cause of the jobs not running correctly, but it definitely is a new error. 0 Question by:Damian_Gardner Facebook Twitter LinkedIn Google LVL 38 Best Solution byChiefIT You are going to have to control your Windows Firewall to allow for Domain Operations. For this specific error, you have to enable "file and print sharing" . 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 You should have removed the IP of demoted DC from DNS search order of client systems 0 LVL 18 Overall: Level 18 Active Directory 8 Windows Server 2003 6 Windows Networking 3 Message Active 3 days ago Assisted Solution by:Sushil Sonawane2012-09-14 Ple