Home > Windows Cannot > Userenv Windows Cannot Determine The Computer Name

Userenv Windows Cannot Determine The Computer Name

Contents

See ME277741 for details on how to do that. x 4 Anonymous We got this error every 5 minutes after we changed the DNS entry for the server. Web of Trust collects data [Security] by ZZZZZZZ351. After some digging and searching I checked local services on the DC and found that the "Netlogon" services was paused - not stopped. navigate here

I've rebuilt the DNS from scratch, making DC1 the primary, and DC2 the secondary, but it doesn't seem to make a difference. I had to delete zone and recreate the reverse lookup zone manually. See ME325356. 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).

Windows Cannot Determine The User Or Computer Name 1053

We opened the firewall to allow client authentication and the problem was solved. Register Login Posting Guidelines | Contact Moderators Ars Technica > Forums > Operating Systems & Software > Windows Technical Mojo Jump to: Select a forum ------------------ Hardware & Tweaking Audio/Visual In another post: "Apparently, the user of this machine configured his TCP/IP settings with static addresses and did not include the proper IP address of the domain controller for his DNS You will know when you have the right set when you get the advanced tab on the connection properties page.

  1. The cause was traced to an Anti-Virus/Firewall program (AVG 7.5 Server) running on the DC.
  2. x 5 Anonymous In my case, increasing the Kerberos Token size worked on my W2K3 standard server.
  3. 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.
  4. So true.
  5. x 4 Nick Garrett - Error: "Access is denied" (Error code 5) - If you have multiple DCs, check your AD replication.
  6. As per MSW2KDB, a network connectivity or configuration problem exists.

I did play around with the Security Policy a bit to try and get a Windows 98 machine to authenticate with the new domain but never got it to work properly, At which time I've stopped/restarted the netlogon service, as well as registering the DNS again. x 5 Craig Curtis Error: "The specified user does not exist" (Error code 1317) -Verify the DNS Settings. Event Id 1053 Error Code 1722 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).

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 Windows Cannot Determine The User Or Computer Name Not Enough Storage x 4 Anonymous - Error: "An internal error occurred" (Error code 1359) - In my case, the Workstation was running all the time and the user had time restriction on his Both comments and pings are currently closed. Parts advice for a DIY router? [Networking] by Onaran381.

The following articles addresses this issue: ME938457, ME942564 and ME823659. Event Id 1053 Group Policy I also tried gpupdate with the firewall switched off to no avail. How does Windows determine computer names? x 113 Anonymous In my case this event was a result of the server pointing to an incorrect DNS server.

Windows Cannot Determine The User Or Computer Name Not Enough Storage

I was able to fix this issue when I realized that my "wkssvc.dll" file, which normally resides in "C:\WINDOWS\system32" got mysteriously deleted. x 5 EventID.Net - Error: "Access is denied" (Error code 5) - See ME262958. - Error: "There are no more endpoints available from the endpoint mapper" (Error code 1753) - See Windows Cannot Determine The User Or Computer Name 1053 The DC event viewer did not show any relevant information. Windows Cannot Determine The User Or Computer Name Access Is Denied It was a domain controller that that had been restored from an image for testing purposes.

You can use the links in the Support area to determine whether any additional information might be available elsewhere. check over here The Intel PRO 1000 MT series must be teamed in order to work properly with Server 2K3. I've tried deleting the zones on DC2, uninstalling the service and then reinstalling, recreating the zones. We found that restarting the Site Server Content Deployment (CRS) service fixed the problem. Windows Cannot Determine The User Or Computer Name 1326

When the DC was rebooted, Windows Server 2003 was setting the Crash On Audit Fail registry key (HKLM\System\CurrentControlSet\Control\Lsa\crashonauditfail) to 2. 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. Generated Fri, 11 Nov 2016 00:49:43 GMT by s_hp90 (squid/3.5.20) Home Error 1053 Windows Cannot determine the User or Computer Name by Melman on May 18, 2009 at 2:26 UTC | his comment is here AD will not work otherwise.

We had the following group policy enabled in the Security settings "Audit: Shut down system immediately if unable to log security alerts". Windows Cannot Determine The User Or Computer Name The Rpc Server Is Unavailable I'm stumped!Thanks,Mike · actions · 2006-Jan-28 10:34 pm · BillRolandPremium Memberjoin:2001-01-21Ocala, FL BillRoland Premium Member 2006-Jan-28 11:01 pm I'm sure you already tried this, but just in case,»www.eventid.net/display. ··· &phase=1 · If so, delete it.

Review your DNS servers." If the error occurred when you attempt to join a Microsoft Windows 2000-based client to a Microsoft Windows NT 4.0-based or Windows 2000-based domain see ME256083.

Example: Event Type:    Error Event Source:    Userenv Event Category:    None Event ID:    1053 Date:        4/13/2012 Time:        3:49:01 PM User:        NT AUTHORITY\SYSTEM Computer:    SERVER Description: Windows cannot determine the cannot determine the user or computer name. 7 posts Pangenitor Ars Tribunus Militum Tribus: ENU Registered: Apr 15, 2002Posts: 1505 Posted: Wed Oct 04, 2006 5:28 pm XP client, newly joined Follow any responses to this post through RSS 2.0. Event Id 1053 Dhcp BulkRate Ars Scholae Palatinae Registered: Sep 9, 2003Posts: 740 Posted: Thu Oct 05, 2006 9:48 am This can be caused on client machines by not having option #15 (DNS Domain Name)

Creating your account only takes a few minutes. See MSW2KDB for details on troubleshooting this problem. DHCP registers DNS.For testing purposes, I set DC2 to point to itself for primary DNS. http://bovbjerg.net/windows-cannot/userenv-error-windows-cannot-determine-the-user-or-computer-name.php Group Policy processing aborted.

Massachusetts question 4 passes, not happy [InTheNews] by IowaCowboy285. TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from Windows servers and workstation via the Splunk Universal Forwarder. In another post: "Apparently, the user of this machine configured his TCP/IP settings with static addresses and did not include the proper IP address of the domain controller for his DNS An example of English, please!

See WITP76098 for information on how to troubleshoot kernel-mode memory leaks. Using gpupdate (ME823659), I was able to reproduce the error. After reconfiguring this rule to work only on the external interface the problem was solved". - Error: "No mapping between account names and security IDs was done" (Error code 1332) - Win98 lives -- now in your browser! [Microsoft] by aurgathor398.

I applied that fix prescribed in the article but it didn't seem to help, so I'm guessing that is not the issue either. · actions · 2006-Jan-30 6:04 pm · mjn

x 4 Anonymous When logging onto a 2k3 terminal server, we would get the "The RPC server is unavailable" message. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. Comments are closed.

After trying other solutions, I was able to resolve the issue by removing the ''Client For Microsoft Networks'', rebooting, then adding the client back in, and rebooting again.