Event ID 1053

  • Thread starter Thread starter Tony
  • Start date Start date
T

Tony

Guest
I have a new server (actually two identical servers) that are receiving an
Event ID 1053 error message on boot.

The error says:

Windows cannot determine the user or computer name. (The specified domain
either does not exist or could not be contacted. ). Group Policy processing
aborted.

I can successfully run gpupdate /force from a command line. I also see in
the log that policies are being successfully applied later. This seems to be
only during boot. I've tried several things thinking that it might be trying
to establish communication before the NIC team is ready.

I have disabled another NIC on a different network (this machine is intended
to be a cluster and I had the other interface configured as the heartbeat
connection). The only interface left is the team. I have also applied the
"wait for network" group policy and applied the reg key from kb202840 among a
number of other things while troubleshooting this.

I can connect to \\mydomain\sysvol\mydomain successfully.

I have worked through an issue in DNS where for some unkown reason it was
querying an incorrect DNS though ipconfig showed it to be configured
correctly. DNS is now resolving correctly and the DNS entry for the server
is showing up correctly after removing it from the domain and rejoining it.
In addition, watching the network traffic no longer shows the errant query.

This is just a pesky startup error that makes me hesitant to put product
clustered resources on the box (es).

I appreciate any suggestions.

Thanks
 
Re: Event ID 1053

Hello Tony,

To get the cluster run properly enable again the heartbeat. Please post an
unedited ipconfig /all from both cluster nodes and the DNS server. Also think
about posting to: microsoft.public.windows.server.clustering

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> I have a new server (actually two identical servers) that are
> receiving an Event ID 1053 error message on boot.
>
> The error says:
>
> Windows cannot determine the user or computer name. (The specified
> domain either does not exist or could not be contacted. ). Group
> Policy processing aborted.
>
> I can successfully run gpupdate /force from a command line. I also
> see in the log that policies are being successfully applied later.
> This seems to be only during boot. I've tried several things thinking
> that it might be trying to establish communication before the NIC team
> is ready.
>
> I have disabled another NIC on a different network (this machine is
> intended to be a cluster and I had the other interface configured as
> the heartbeat connection). The only interface left is the team. I
> have also applied the "wait for network" group policy and applied the
> reg key from kb202840 among a number of other things while
> troubleshooting this.
>
> I can connect to \\mydomain\sysvol\mydomain successfully.
>
> I have worked through an issue in DNS where for some unkown reason it
> was querying an incorrect DNS though ipconfig showed it to be
> configured correctly. DNS is now resolving correctly and the DNS
> entry for the server is showing up correctly after removing it from
> the domain and rejoining it. In addition, watching the network
> traffic no longer shows the errant query.
>
> This is just a pesky startup error that makes me hesitant to put
> product clustered resources on the box (es).
>
> I appreciate any suggestions.
>
> Thanks
>
 
Re: Event ID 1053

I'm not worried about the clustering actually. I just want to eliminate the
1053 error message on startup.

Thanks

"Meinolf Weber" wrote:

> Hello Tony,
>
> To get the cluster run properly enable again the heartbeat. Please post an
> unedited ipconfig /all from both cluster nodes and the DNS server. Also think
> about posting to: microsoft.public.windows.server.clustering
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > I have a new server (actually two identical servers) that are
> > receiving an Event ID 1053 error message on boot.
> >
> > The error says:
> >
> > Windows cannot determine the user or computer name. (The specified
> > domain either does not exist or could not be contacted. ). Group
> > Policy processing aborted.
> >
> > I can successfully run gpupdate /force from a command line. I also
> > see in the log that policies are being successfully applied later.
> > This seems to be only during boot. I've tried several things thinking
> > that it might be trying to establish communication before the NIC team
> > is ready.
> >
> > I have disabled another NIC on a different network (this machine is
> > intended to be a cluster and I had the other interface configured as
> > the heartbeat connection). The only interface left is the team. I
> > have also applied the "wait for network" group policy and applied the
> > reg key from kb202840 among a number of other things while
> > troubleshooting this.
> >
> > I can connect to \\mydomain\sysvol\mydomain successfully.
> >
> > I have worked through an issue in DNS where for some unkown reason it
> > was querying an incorrect DNS though ipconfig showed it to be
> > configured correctly. DNS is now resolving correctly and the DNS
> > entry for the server is showing up correctly after removing it from
> > the domain and rejoining it. In addition, watching the network
> > traffic no longer shows the errant query.
> >
> > This is just a pesky startup error that makes me hesitant to put
> > product clustered resources on the box (es).
> >
> > I appreciate any suggestions.
> >
> > Thanks
> >
>
>
>
 
Re: Event ID 1053

In news:7C2ADB1A-40EB-4804-8C9E-FA0F03CD4E9D@microsoft.com,
Tony <nospam4tony@nospam.postalias> typed:
> I'm not worried about the clustering actually. I just want to
> eliminate the 1053 error message on startup.
>
> Thanks

That's why Meinolf was asking for an ipconfig /all. It gives us a starting
point to eliminate basic configuration errors. The whole thing may be able
to be cleaned up in a single response.

1053's are indicative of a failure to contact the domain. THey may or maynot
be associated with 1058's. They can also be associated with LSASRV 40961
errors as well. The basis to 'finding' the domain is DNS. However there's
more behind that, such as are the SRV actually registered in DNS, is the AD
DNS domain name a proper name or a single label name, is the Primary DNS
suffix correct and matches the domain name, what DNS servers is the machine
(or each node) using, subnet masks correct, are you using WINS, are the
nodes as well as the cluster name registrered in WINS and DNS (for the
LdapIpAddress and GcIpAddress, etc) and many many others.

So you see, there are many factors. 1053's can be difficult to diagnose
without configuration info and a knowledge of the infrastructure.

Here's a peek at what I am talking:
http://eventid.net/display.asp?eventid=1053&eventno=1584&source=Userenv&phase=1



--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Infinite Diversities in Infinite Combinations
 
Re: Event ID 1053

Hello,

Thanks for your post.

From your description, you receive the Event 1053 only after the reboot of
the server. After that, you can access the \\mydomain\sysvol\mydomain share
and run "gpupdate /force" properly without the Event 1053 logged.

Yes, first of all, please try to run "ipconfig /all" to verify all
settings. Considering that Event 1053 is only logged right after a system
reboot, I suspect that the Winlogon service is starting before the network
initializing. This prevents Winlogon and netlogon from accessing the DCs
properly. Do you have a 1 GB NIC on the server?

Please go through the steps below, then reboot twice and check if 1053 was
logged again:

1. Click Start, click Run, in the Open box, type regedit , and then click
OK.
2. In Registry Editor, locate the following registry subkey

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

3. Add "WaitForNetwork" Dword with Value 1 if it is not there.
4. Quit Registry Editor.


Meanwhile, could you please send me the Directory Service MPS report?

You can get this tool from the link:

Microsoft Product Support's Reporting Tools (MPSRPT_DirSvc.EXE)
http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-
88B7-F9C79B7306C0&displaylang=en

-----------------------

Please send the MPS report CAB file to tfwst@microsoft.com

Note:

a. Please include the following three lines for this issue in the email
body:

Event ID 1053
# 41955363
Miles Li - MSFT

b. We will continue to discuss the issue here in newsgroup and will NOT
reply via emails.

c. Pease post a quick note in the current thread to inform me after sending
the email.

Thanks.



Sincerely,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Re: Event ID 1053

Hi Miles,

Thanks for getting me on the right track. I created the registry key that
you suggested then rebooted. I did not receive the error on the following
reboot. I rebooted a second time and received the error again.

It definitely led me in the direction that the domain communication was
trying to happen before the network was ready. I talked with my network guy
and we set "portfast" on the switch. That appears to have resolved the
issue. I've done three reboots with no errors!

Thank you again,

Tony

"Miles Li [MSFT]" wrote:

> Hello,
>
> Thanks for your post.
>
> From your description, you receive the Event 1053 only after the reboot of
> the server. After that, you can access the \\mydomain\sysvol\mydomain share
> and run "gpupdate /force" properly without the Event 1053 logged.
>
> Yes, first of all, please try to run "ipconfig /all" to verify all
> settings. Considering that Event 1053 is only logged right after a system
> reboot, I suspect that the Winlogon service is starting before the network
> initializing. This prevents Winlogon and netlogon from accessing the DCs
> properly. Do you have a 1 GB NIC on the server?
>
> Please go through the steps below, then reboot twice and check if 1053 was
> logged again:
>
> 1. Click Start, click Run, in the Open box, type regedit , and then click
> OK.
> 2. In Registry Editor, locate the following registry subkey
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
>
> 3. Add "WaitForNetwork" Dword with Value 1 if it is not there.
> 4. Quit Registry Editor.
>
>
> Meanwhile, could you please send me the Directory Service MPS report?
>
> You can get this tool from the link:
>
> Microsoft Product Support's Reporting Tools (MPSRPT_DirSvc.EXE)
> http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-
> 88B7-F9C79B7306C0&displaylang=en
>
> -----------------------
>
> Please send the MPS report CAB file to tfwst@microsoft.com
>
> Note:
>
> a. Please include the following three lines for this issue in the email
> body:
>
> Event ID 1053
> # 41955363
> Miles Li - MSFT
>
> b. We will continue to discuss the issue here in newsgroup and will NOT
> reply via emails.
>
> c. Pease post a quick note in the current thread to inform me after sending
> the email.
>
> Thanks.
>
>
>
> Sincerely,
> Miles Li
>
> Microsoft Online Partner Support
> Microsoft Global Technical Support Center
>
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
 
Re: Event ID 1053

Hello Tony,

I am very glad that the problem has been successfully solved, and I
appreciate your sharing that will help others a lot. Base on the case
status, I will go head to close this case.

Sincerely,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top