When working offline we've found that our Windows 7 Pro machines will occasionally (is not a consistent behavior or that can be easily replicated) receive the error "there are currently no logon servers available to service the logon request" (and this only occurs on our Windows 7 Professional machines as other Windows XP SP3 machines do not experience this issue). When logging on the domain there is no issue and the next few subsequent offline logons work without an issue. However, we still see this issue arise from time to time and would like to get a handle on it. The following key value is set to 10 on both the Win7 and XP machines: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon\CachedLogonsCount I've tested incrementing this value to 25, 50, etc, but the issue still occurs. I have seen a few other posts related to this, but nothing outside of what we've already tested. Has anyone else experienced and found a fix for this issue? Thanks, B

Hi, Please refer the following link which might be useful to you : http://technet.microsoft.com/en-us/library/cc978903.aspx I suspect that some programs are trying to connect to DC when the issue occurs. If you want to find the culprit, you could perform a clean boot. Regards, Alex ZhaoPlease 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.

Thanks, but that article is irrelevant and was generated for Windows Server 2000...We do not use local accounts outside of the local administrator account, so it's not a valid alternative. Even if creating new local accounts was a solution (and thus managing local + AD accounts, which would not really be an option) they would be unable to access their profile from their domain accounts as they are logged in as standard users. The issue is the cached credentials for the domain accounts are occasionally not working. This issue is hit-or-miss, but only on Win 7 machines. The XP machines do not encounter this issue when working offline, so it's not a generic issue as the link above suggests.

Hi, Based on your description, the reason may be the computer is physically removed from the network. And you are right, Windows 7 is different from Windows XP, thus I suspect there are certain programs are trying to connect to DC when your computer is offline. In order to verify this, it’s a good way to perform a Clean Boot. Regards, Alex ZhaoPlease 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.

Hi I've got almost the same issue, where in my case i don't have any rights on my profile after logging off the network. The error message says that i don't have permissions on \\servername\%username%$\desktop. That's odd because I don't wanna change anything there when I'm not logged in on the network. My Outlook doesn't work normal, Word comes up with errors that they cannot find network files. It doesn't matter if I use roaming profiles or not. Tried to clean up the registry etc... nothing helps. The users were former XP users... that could be a problem, but a new profile is written on the server with V2. So I assume that it won't disturb eachother. Please let me know what to do. I use a Server 2003 (DC) and Win7 Pro notebooks.

We have this problem with our Windows 7 laptops as well. If they are in the office and connected to the domain, they authenticated without issue. When outside the office they will sometimes get the error "There are currently no logon servers available to service the logon request". I suspect the problem lies in the bad habbits of the users not logging off the network when they leave the office, aka, they just leave multiple files open and close the lid, putting the computer to sleep. This does not help the end user when outside the office, however, and it is not always convienient for them to come back to the office to connect if they are out of the country. Can anyone help with this cached credentials issue?

Possible solution. I have exactly the same issue with a remote Laptop with 13 profiles cached (including the local administrator.) The users have to log on to the local machine and then connect to the domain through a VPN. It seems the last three users added to the machine are the ones that lose their credentials. I have never seen this with XP SP3 or Windows 7 Pro desktop systems (although they usually have fewer cached profiles.) Also I have not seen this with single-user laptops on Win 7. I tried the registry hack above changing the value to 20. After rebooting, I re-authenticated each of the problem users to the domain. I then ran through all 13 users logging into the local machine without issue. So far they all worked. I want to give this a few days before saying it is solved for me. If others try this, please let me know how it works for you. regards, Dave (Wilmington, Delaware)

I have this exact problem. We have a small Windows 2008 x64 Server network with 16 users, 4 of whom are remote and not office based. Until recently all client machines used Windows XP and this problem did not raise its head! Users would logon to the laptop/domain while disconnected, only connecting the VPN later when needing to access EXchange. Recently we have issued replacement laptops to two remote users. These machines use Windows 7 Professional and were configured in the office and attached to the domain. Users are able to login to the laptops with domain credentials when in the office and when away BUT after a period these users are not able to login to their laptops getting the error message: "There are currently no logon servers available to service the logon request". If the user then comes in to the office and connects via ethernet or wireless to the network they can then logon and whatever counter is used to block access is reset as they are then able to login remotely again for a period. It would appear that this is a problem with Windows 7 Professional, but is there a setting that needs to be changed on the server?