Enrollment Issue Win2k Domain WinXP Client

Our domain Controller, Win2k Server, crashed and died.

We reloaded the OS

set up the Domain again (with the same domain name)

removed all the WinXP clients from the domain

and added them to the domain again.

the following event logs keep occuring, and I think it is causeing network issues.

Event Type:      Error
Event Source:      AutoEnrollment
Event Category:      None
Event ID:      15
Date:            11/28/2003
Time:            9:16:00 AM
User:            N/A
Computer:      ABNSYDPC004
Description:
Automatic certificate enrollment for local system failed to contact the active directory (0x8007054b).  The specified domain either does not exist or could not be contacted.
  Enrollment will not be performed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

==============================

Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1054
Date:            11/28/2003
Time:            9:15:00 AM
User:            NT AUTHORITY\SYSTEM
Computer:      ABNSYDPC004
Description:
Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

======================

Event Type:      Error
Event Source:      Application Hang
Event Category:      (101)
Event ID:      1002
Date:            11/27/2003
Time:            2:25:54 PM
User:            N/A
Computer:      ABNSYDPC004
Description:
Hanging application , version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 48 61 6e 67   ion Hang
0010: 20 20 20 30 2e 30 2e 30      0.0.0
0018: 2e 30 20 69 6e 20 68 75   .0 in hu
0020: 6e 67 61 70 70 20 30 2e   ngapp 0.
0028: 30 2e 30 2e 30 20 61 74   0.0.0 at
0030: 20 6f 66 66 73 65 74 20    offset
0038: 30 30 30 30 30 30 30 30   00000000


These messages are continious.

I really need some help as I have tried Technet and dont seem to be able to get a straight answer.

Thanks in Advance
LVL 2
RaybansTechnical ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bhoehneCommented:
A think all the above errors occur on the clients?

Some questions
- Your Server is also DHCP and Active Directory Integrated DNS Server? If so, are you shure DNS & DHCP is setup correctly? (i.e. authorising DHCP, etc.)
- You setup your Domain Controller and added the clients to the new identically named domain manually on the "AD Users and Computers" or did you make a "real" domainjoin from the client?
   If the first: Delete all XP Client Computer Accounts from AD again and make a client side domain-join. Did this solve your problems?
   If the second: You haven't done anythink to the XP clients, despite making a domainjoin to the new domain?

You can play around with the "netdiag.exe" tool (Win2k server support tools). See Q247811 for more details.

Two other places to look at: Q260371 - "Troubleshooting Common Active Directory Setup Issues in Windows 2000" and Q237675 - "Setting Up the Domain Name System for Active Directory".
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RaybansTechnical ManagerAuthor Commented:
I removed each PC from the domain, to work group, using the network wizard

and then run the wizard again to add to the new domain

0
RaybansTechnical ManagerAuthor Commented:
Problem Solved

DNS on client (and server) in an Active Directory has to be pointing at the AD Server, otherwise this problem will occur and the network actually lags a lot.

DNS issue resolved now, including the forwarding correctly setup

thanks for the help, but I still had a lot of testing and research to find the problem.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.