Event ID 1053 (Access is denied)

[jokes54321]

We are running a Windows 2000 AD domain. Three DC's, and two in house DNS
servers. Any and all Win2K boxes work fine. We are now trying to add a
Windows 2003 Server to host our websites. This server constantly logs the
following.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 11/7/2003
Time: 1:28:43 PM
User: NT AUTHORITY\SYSTEM
Computer: NETWORK-ADMIN
Description:
Windows cannot determine the user or computer name. (Access is denied. ).
Group Policy processing aborted.

After checking our Windows XP boxes we've found these are logging the same
event (above event from an XP box). Everything else works, the Windows 2003
Server as well as the XP boxes have registered themselves with our DNS
server, running AD Users and Computers successful queries the AD and allows
us to add, edit and delete users. How can I get rid of this error. I've
found several articles but none seem to apply. I checked the Default Domain
Controller Policy to see if the SMB problem was it but the four items were
all set to No Specified.

 

[Ace Fekay [MVP]]

In

We are running a Windows 2000 AD domain. Three DC's, and two in house
DNS servers. Any and all Win2K boxes work fine. We are now trying to
add a Windows 2003 Server to host our websites. This server
constantly logs the following.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 11/7/2003
Time: 1:28:43 PM
User: NT AUTHORITY\SYSTEM
Computer: NETWORK-ADMIN
Description:
Windows cannot determine the user or computer name. (Access is
denied. ). Group Policy processing aborted.

After checking our Windows XP boxes we've found these are logging the
same event (above event from an XP box). Everything else works, the
Windows 2003 Server as well as the XP boxes have registered
themselves with our DNS server, running AD Users and Computers
successful queries the AD and allows us to add, edit and delete
users. How can I get rid of this error. I've found several articles
but none seem to apply. I checked the Default Domain Controller
Policy to see if the SMB problem was it but the four items were all
set to No Specified.

A number of things can cause this. Read this:
http://www.eventid.net/display.asp?eventid=1053&source=

One major cause is using your ISP's DNS address in your DC and/or client's
IP properties. Ensure that your machines are ONLY pointing to your internal
DNS server. This is because that's what AD and the clients use to "find"
domain stuff and for communication. Otherwise it will ask your ISP and it
can't answer that and this and numerous other errors WILL occur. Configure a
forwarder for efficient Internet resolution.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory