Event errors

G

Guest

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 -#..
 
R

Richard G. Harper

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.
 
G

Guest

I'm getting one odd error that nobody can explain. It is pointing to a domain
name on the network that does not and has not existed on our network. "JRA"
is not anything that we can find traces of to remove. I have checked DNS and
DHCP for anything pointing to this domain name and have not been able to find
it, I have also looked in the sysvol folder on the DC and there was noting
there either.

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 8/3/2006
Time: 8:29:30 AM
User: N/A
Computer: UPTURN
Description:
No Windows NT or Windows 2000 Domain Controller is available for domain JRA.
The following error occurred:
There are currently no logon servers available to service the logon request.
Data:
0000: 5e 00 00 c0 ^..À
 
G

Guest

That error is coming from the event logs of the DC.

Richard G. Harper said:
Where are you seeing this error? On what computer(s)?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


Ed May said:
I'm getting one odd error that nobody can explain. It is pointing to a
domain
name on the network that does not and has not existed on our network.
"JRA"
is not anything that we can find traces of to remove. I have checked DNS
and
DHCP for anything pointing to this domain name and have not been able to
find
it, I have also looked in the sysvol folder on the DC and there was noting
there either.

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 8/3/2006
Time: 8:29:30 AM
User: N/A
Computer: UPTURN
Description:
No Windows NT or Windows 2000 Domain Controller is available for domain
JRA.
The following error occurred:
There are currently no logon servers available to service the logon
request.
Data:
0000: 5e 00 00 c0 ^..À
 
R

Richard G. Harper

At this point I don't know that I have any useful information for you. If
the DCs are looking for a domain that does not exist and you don't have any
idea how that could have happened you either have someone on your network
with "happy fingers" or a serious security problem. Either way you are in
need of a serious professional overhaul of your network, domain and security
policies.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


Ed May said:
That error is coming from the event logs of the DC.

Richard G. Harper said:
Where are you seeing this error? On what computer(s)?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


Ed May said:
I'm getting one odd error that nobody can explain. It is pointing to a
domain
name on the network that does not and has not existed on our network.
"JRA"
is not anything that we can find traces of to remove. I have checked
DNS
and
DHCP for anything pointing to this domain name and have not been able
to
find
it, I have also looked in the sysvol folder on the DC and there was
noting
there either.

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 8/3/2006
Time: 8:29:30 AM
User: N/A
Computer: UPTURN
Description:
No Windows NT or Windows 2000 Domain Controller is available for domain
JRA.
The following error occurred:
There are currently no logon servers available to service the logon
request.
Data:
0000: 5e 00 00 c0 ^..À


:

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.

--
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 -#..
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top