Re: Event errors
- From: "Richard G. Harper" <rgharper@xxxxxxxxx>
- Date: Wed, 2 Aug 2006 21:07:12 -0400
What's happening on the domain controller? Event logs show anything
interesting? If every client is having problems then you almost surely have
a sick domain controller.
--
"Ed May" <EdMay@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BBA9E21F-9EF4-487D-B35D-71122246A77C@xxxxxxxxxxxxxxxx
I support a domain that is using Active Directory on Windows 2000. Recently
all the computers started logging Event errors 1053 Userenv(1000 on the 2k
systems), 15 AutoEnrollment and 11163 DnsApi. The systems are a mix of
2000
and XP Pro and were not logging these events until just this past month.
Has
anyone run in to this I have tried the solotions KB262958, KB256083,
KB263693, KB839880. All systems have been unjoined from the domain their
accounts deleted from AD and rejoined to the domain. I have pasted the
events
from on of the XP systems below.
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 8/2/2006
Time: 3:41:11 PM
User: NT AUTHORITY\SYSTEM
Computer: PLANNING1
Description:
Windows cannot determine the user or computer name. (Access is denied. ).
Group Policy processing aborted.
Event Type: Error
Event Source: AutoEnrollment
Event Category: None
Event ID: 15
Date: 8/2/2006
Time: 11:56:15 AM
User: N/A
Computer: PLANNING1
Description:
Automatic certificate enrollment for local system failed to contact the
active directory (0x8007052b). Unable to update the password. The value
provided as the current password is incorrect.
Enrollment will not be performed.
Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11163
Date: 8/2/2006
Time: 12:47:54 PM
User: N/A
Computer: PLANNING1
Description:
The system failed to register host (A) resource records (RRs) for network
adapter
with settings:
Adapter Name : {89D554AF-DBC8-4065-80F2-77F75E2C43DF}
Host Name : Planning1
Primary Domain Suffix : ui-ny.local
DNS server list :
10.10.1.1
Sent update to server : 10.1.1.1
IP Address(es) :
10.10.1.3
The reason the system could not register these RRs was because the DNS
server failed the update request. The most likely cause of this is that
the
authoritative DNS server required to process this update request has a
lock
in place on the zone, probably because a zone transfer is in progress.
You can manually retry DNS registration of the network adapter and its
settings by typing "ipconfig /registerdns" at the command prompt. If
problems
still persist, contact your DNS server or network systems administrator.
Data:
0000: 2d 23 00 00 -#..
.
- Follow-Ups:
- Re: Event errors
- From: Ed May
- Re: Event errors
- References:
- Event errors
- From: Ed May
- Event errors
- Prev by Date: Re: Adding An Windows XP To a LAN
- Next by Date: Re: Workstation service is slowing down the boot up of the profile
- Previous by thread: Event errors
- Next by thread: Re: Event errors
- Index(es):
Relevant Pages
|
