Connection to server dropped

[SteveDingle]

Hello All,

PC: Windows XP SP2
Server: Windows 2003

I have been having this problem with my home network for a coupla years now, haven't gotten it resolved yet but have more information so hoping that someone might have new ideas.

I have a server and a coupla PCs attached to it at home. Randomly my PC looses its connection to the server (i.e. I can't access network drives or printer) and the only way I can get back in is to reboot. It usually last at least 1 day but have also had it last multiple days

I created a small program that checks for a file on the a server drive every 30 seconds and if it can't find it ((lost connection) tell me and records the time. Using that I was able to find the following to "security events" which occurred at the same time. I don't know what they mean, hoping someone else will.

*****************
Source: LSARV
Category: SPNEGO (Negotiator)

The Security System detected an attempted downgrade attack for server cifs/Antec2Server. The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request.
(0xc000005e)".

Next event............

Source: LSARV
Category: SPNEGO (Negotiator)

The Security System could not establish a secured connection with the server cifs/Antec2Server. No authentication protocol was available.
*****************

I should add I'm quite the novice when it come to networking and have even tried to get professional to out to help but I live out of the way and job is just "too small" so never any takers

Thanks
Steve

 

[linney]

Can you supply the exact Event: ID number from the Event Viewer? Are there any errors recorded on the Server too?

In the meanwhile have you looked around these?

http://www.google.com/search?q=lsasrv+spnego+xp&ie=UTF-8&oe=UTF-8&sa=N&tab=gw

http://groups.google.com/groups?q=lsasrv+spnego+xp&ie=UTF-8&oe=UTF-8&

 

[CAPPBC]

Are you running a DC? If so, check Firewall settings? Deployed firwall, one pc could not retrieve domain list. Issue was firwall policy did not update to the pc. Once updated, everything was fine.