One XP Pro cannot find domain

[Andy Dyble]

Hi

I network is configured like :

2000 Server AD SP4.
All clients XP Pro DNS points to 2000 Server

There is one Laptop that every time it is restarted cannot find the domain
controller. There 3 ways it gets fixed :

1. Sometimes works - Log onto local pc's domain as Adminsitrator, then Logg
Off and back in as Domain Administrator, then Log Off and back in as the
nomal user.

2. Restart Server, then restart the PC

3. If the above doesn't work, then demote to workgroup and reconnect to
domain.

This only happens on one PC.

Has anybody any ideas ?

Thanks

Andy

 

[Cary Shultz [A.D. MVP]]

Andy,

Do you have the latest Drivers for the Network Card? If yes, have you tried
replacing the Network Card? If that is not an option have you tried a
different Cat5 ( Cat5e ) cable from the NIC to the wall jack? From the
patch panel to the Switch? How about a different port on the Switch. Do
you have a managed Switch where you can check to see if that particular port
is 'bad'?

This is just the hardware side of things which may not apply as you seem to
have found some rather 'different' ways to work around this. Do you have
any event ids on the computer. Right click My Computer, select Manage and
then open up the Event Viewer.


HTH,

Cary

 

[Andy Dyble]

The System event says :

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 21/03/2004
Time: 09:00:46
User: MIDSOFTDOMAIN\adyble
Computer: MIDSOFT-4
Description:
The server {520CCA63-51A5-11D3-9144-00104BA11C5E} did not register with DCOM
within the required timeout.

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

and

Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40961
Date: 21/03/2004
Time: 09:00:28
User: N/A
Computer: MIDSOFT-4
Description:
The Security System could not establish a secured connection with the server
DNS/midsoft-server.midsoftdomain.local. No authentication protocol was
available.

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

Thanks

ANdy

 

[Andy Dyble]

And this one in Application :

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1054
Date: 21/03/2004
Time: 09:00:09
User: NT AUTHORITY\SYSTEM
Computer: MIDSOFT-4
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.

Thanks

Andy

 

[Andy Dyble]

Thanks for the info :

Latest drivers are for card and has been working OK for last 18 months.
Same problem using new wireless card.
Replaced cable to server and PC, also wireless changes it as well.
I can overcome the problem now by pulling out the wireless card(or
disconnecting cable) before PC starts, then insert it after logging in. I
have deleted DNS cache, removed/added PC name from AD.

Any other ideas ?

Thanks
Andy