XP Pro loses network connection

[techjulie]

I am having problems in an 2003 AD Domain with an XP Pro client
losing the ability to authenticate. A user will logon successfully to the
domain, and after a few hours, seem to lose their credentials. One minute
the user will be able to authenticate, the next, authentication will fail regardless of user account.
Specifically, a user who could access a network share one minute, will get
a time out when they try to print to a network printer or access network shares. Try to log in with any account and it fails.

Several times I have had to remove the client from network and add him back in. Once had to remove computer from domain from server,too. Sometimes, just rebooting works.

Errors in the event log:

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5790

Description:
No suitable Domain Controller is available for domain
x. An NT4 or older domain controller is available but it
cannot be used for authentication purposes in the Windows
2000 or newer domain that this computer is a member of.
The following error occurred:
There are currently no logon servers available to service the
logon request.

Also
Event Type: Warning
Event Source: LSASRV
Event Category: None
Event ID: 40961
Security System could not establish a secured connection with the server RECEPTIONIST. No authentication protocol was available



Thanks for any help!
-Julie

 

[itfellow]

techjulie,

I have experienced similar problems with my XP clients on Windows 2000 domain. The problem seemed to be related to connectivity with the domain controller. As far as I could tell, I only had this problem with the workstations that had full internet connectivity, and thus had multiple DNS servers (one for local domain and one for internet), and had the domain controller as the secondary DNS server. I placed the Windows 2000 domain controller as my primary DNS server in each client and the problem so far has seemed to go away.

 

[bofhrevenge2]

This is the case Windows XP it requires the primary DNS server to be your own internal DNS server as your ISP's DNS is not aware of your network IP addresses.

 

[techjulie]

Thanks!
Primary and Secondary DNS were ok (and in correct order). There was a 3rd DNS pointed at the ISP but I have removed that now. Will look more closely at machine's HOST/LMHOST settings because it's the only one having a problem.

Will Post when I have solution.
-Julie