We have been having problems with some remote users logging into their laptops. They get the error “No logon servers available to service the logon request” at Windows logon even though they have previously logged on and should have their credential cashed. The problem has occurred after we replaced their Windows XP laptops with new Windows 7 Pro 32 bit laptops. Also there are now using their AD accounts for local logon for the first time. One user logged on successfully connected to our network. When home logged on again, connected to his wifi, used our Cisco VPN, worked etc and then turned off his laptop. Next day he got the error. One strange aspect is that only some users are affected. We do not yet understand why this problem occurs. It could be that the cashed credentials get lost, corrupted or expire? Or some weird names resolution issue due to our configuration. For example we have turned off ‘Off line files’ but the users have a dive mapped to the fileserver only accessible with the VPN enabled. Also these users do not have local admin rights (I tried upping the rights to local admin but maybe as the problem has already occurred there was no point) I need to know two things: 1. Why does this happen so we can prevent it happening in the future 2. How can we get remote users to authenticated with an AD domain controller during logon.

Hi Chris Brown, Thanks for the post! Please temporarily remove all the security software to check if it works. You can also try force Kerberos to use TCP instead of UDP, refer to: http://support.microsoft.com/kb/244474 Here’s a similar thread as yours: http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/bcc5f99a-d3bf-4b2f-9168-bc265fdd4f8d Regards, MiyaThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.