Event id 40960 and 40961 windows xp

Come for the solution, stay for everything else. Welcome to our community! The failure code from authentication protocol Kerberos was "No authority could be contacted for authentication.

No authentication protocol was available. This profile contained no login scripts and does not roam. In an attempt to isolate the problem I connected the SBS box to a seperate switch and then attached 1 workstation to this switch. In effect, I had the SBS box and a workstation sitting in their own little sandbox. Again login times are 4 - 12 minutes.

This test hangs here and never results in any output. I'm not sure if this has anything to do with the original problem but I thought I'd mention it just in case. Join our community to see this answer! Come for the solution, stay for everything else. Welcome to our community! Although I did not migrate accounts to the new domain it is a new install with new accounts and AD , the problems I am experiencing occur in the new network as well as the old.

For this reason, I suspect that one or all of the 20 clients are having issues. I have implemented several of the relevant suggestions at both sites, to no avail. The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request.

No authentication protocol was available. At the end of the workday, around PM , several clients lose connectivity to the server network shares and record these error messages. I do occasionally receive a W32Time error on some of the clients. Network logon at the clients is somewhat slow mins , and I have found that a reboot of ANY client on the domain clears up the problem. Also, I have created a reverse lookup zone on the server. I am running a single server for now , syncing to an external time source.

I have checked the server and all clients for running processes AV downloads, sweeps, etc. I have installed a network sniffer Ethersnoop to see if there are broadcast storms happening, and all traffic seems normal. Verify the necessary SPNs are registered, based on the information in the event description.

Clear cached credentials. Based on the information in the event description, verify that the SAM account name of one account is not the same as the UPN of another account. Thank you for your reply. Right-click "Dhcp", and then click "Permissions".

Click Add, type network service Best regards, Cameron Ye. Thank you for your update. I am glad to hear that the information I provided is useful for you. It is my pleasure to work with you in this post. If you encounter any difficulties in the future, please submit the post to the newsgroup.

We are glad to be of the assistance. Again, thank you for using Microsoft newsgroup. Have a nice day. Event ID and Reply to author. Report message as abuse.