Home | Recovery | Cisco How To Net How To | Blog | Search | Forums | Services | Setup Guide | Chicagotech MVP | IT Exam Practice  |  About Us | Contact Us|

Chicago Area Laptop for rent: $35 per day plus $10 for additional day
rental

 

Event ID: 1053 - Windows cannot determine the user or computer name

Q: | I have 2 subnets in my environment.  One subnet is 192.168.4.  The other
| subnet is 192.168.8.
|
| SBS 2003 box has two nics.
| The first nic is 192.168.4.3.  The second nic is 192.168.8.6.
|
| There is windows xp workstation with ip 192.168.8.23.  I was able to
| successfully join it with the domain and login.
|
| Also, there is a windows server 2003 EE server.  It's | address is 192.168.4.2.
|
| With the above configuration I was able to successfully make windows
server 2003 EE member of SBS2003 domain.
|
| When I try to login, I get ....
|
| Event Type: Error
| Event Source: Userenv
| Event Category: None
| Event ID: 1053
| Date:  5/25/2005
| Time:  2:39:36 PM
| User:  NT AUTHORITY\SYSTEM
| Computer: WIN2K3SERV
| Description: Windows cannot determine the user or computer name. (The specified domain
| either does not exist or could not be contacted. ). Group Policy processing aborted.

A: Based on my research, this behavior occurs because the computer to which
the user is logging on does not have the "Access this Computer from the
Network" permission at the validating domain controller. The Everyone group
was removed from the list of groups that are granted the "Access this
Computer from the Network" permission.

RESOLUTION
===============

In an appropriate Group Policy Object at the Domain Controllers container
(most likely the Default Domain Controllers Policy),   ensure that the
appropriate groups are listed in the "Access this Computer from the
Network" permission. You can find this permission in the following folder:

Computer Configuration\Windows Settings\Security Settings\Local
Policies\User Rights Assignment

The following groups have the "Access this Computer from the Network"
permission on domain controllers by default:

Administrators

Authenticated Users

Everyone

NOTE: Include the Everyone group in the list of groups because certain
operations involve accounts that may not have been authenticated to the
domain yet. Examples of these operations include when a user changes an
expired  password at logon, or when a user in a trusting domain needs to
anonymously enumerate users and groups to apply Access Control Lists (ACLs)
in the trusting domain (for Microsoft Windows NT 4.0 or inter-forest
trusts).
 
More detailed information for your reference:
262958 Lookup of Permissions on ACLs Shows Only SIDs
http://support.microsoft.com/?id=262958

More information for your reference:
883271 Event ID 1053 and 1058 appear in the Application log after you
upgrade
http://support.microsoft.com/?id=883271

Hope the information helps. If there is anything that is unclear, please
feel free to let me know.

Thanks & Regards,

Jason Tan

Microsoft Online Partner Support
 

Post your questions, comments, feedbacks and suggestions

Contact a consultant

Related Topics

 

Bob Lin Photography services

Real Estate Photography services 

 

  This web is provided "AS IS" with no warranties.
Copyright © 2002-2018 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.