XP pro workstations disconnecting from server

[jrl01]

New SBS 2003. Having problems with Windows XP Pro Systems, 2 with sp1 and one with sp2. We are experiencing the following three messages on each of theseworkstations. We have used Microsoft Knowledge Base Article 310461 for the Autoenrollment issue, but still receiving disconnects. Any suggestions?
------------------------------------------------------

Small Business Server 2003 Environment:
Problem: Operating System
Operating System: Windows XP

1. Problem Description: DescriptionEvent Type: Error
Event Source: AutoEnrollment
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.

2. Event Type: Error
Event Source: Userenv
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.


3. Event Type: Error
Event Source: W32Time
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 29 minutes. NtpClient has no source of accurate time.

 

[ChicagoTechNet]

I wish you posted the event id #. Any way, they sound like DNS issue. what do you get is using nsloonup? can you ping the DNS server by name?

Robert Lin, MS-MVP, MCSE & CNE
Windows, Network, Internet, VPN, Routing and How to at

http://www.ms-mvps.com

 

[jrl01]

Thanks for your response.

The event IDs# were:

1) Autoenrollment, event ID #15
2) userenv, event ID # 1053
3) W32Time, event ID # 29 & 14


When we use nslookup, the name of our isp provider name shows and not our local server.

All of our Windows 2000 OS computers are working great.... it is just the XP Pro OS computers that we are receiving these errors.

 

[ChicagoTechNet]

thank you for the details. what you need to do is installing an internal DNS. this may help. quoted from

http://www.chicagotech.net

Why is XP running slower while logon 1

When I login into a Windows 2000 active directory from a new xp pro machine the login in is extremely slow. After logged on, everything works fine. But other windows versions don't have this problem.
A: This is almost like name resolution issue. Comparing with previous versions, XP is heavily dependent on DNS to find DC. If the DNS is configured incorrectly, XP will take longer time waiting for it to timeout before it tries using NetBIOS. Make sure
1) The DNS setup correct and have the server information.
2) XP clients can find the DNS server.
3) XP machine's DNS server is pointed to your internal DNS server rather than your ISP's DNS server.
4) Make sure no errors on logon scripts or GPO's that could be causing the delay.
5) Check any errors on event viewer.
6) Disable NetBIOS on the interfaces that client will not use.

Robert Lin, MS-MVP, MCSE & CNE
Windows, Network, Internet, VPN, Routing and How to at

http://www.ms-mvps.com