I have a couple windows 7 x86 boxes that lose authentication to windows 2003 file shares and network print services after waking from sleep. I have 10 others that work as expected all of the time. It's just these three that are unable to access these resources when they awake from sleep mode. I see no errors in the event log yet they are unable to access files shares or printers hosted from server 2003 servers. They are able to access file shares and printer services hosted from Windows 2008 servers during this time. If we reboot the workstation the user again can access the windows 2003 file shares and print server functions of the windows 2003 server as well as the 2008 server shares and printers. Any thoughts would be greatly appreciated. Tom

Do you use persistent status in mapping? Do you let sleep drives too? What is the sleep setting for NIC? Regards Milos

Thanks for looking at this. They are file shares accessed via an application, not so much like a mapped drive. When the aplication is opened, it acceesses the shared file folder as a repository. We also have issues accessing the shared printers hosted on this 2003 server after waking from sleep but no issues reconnecting to 2008 file and printer shares. Yes I beleieve the drives go to sleep as well. My experience with sleep has been, if the computer goes to sleep it puts 'everything' to sleep, hence the network card setting 'allow this device to wake the computer' is only available if the 'allow the computer to turn this device off to save power' is checked. Without the save power option checked you cannot wake the computer once it has gone to sleep even thought the 'save power' option is not enabled. I believe this option is moot??? The NIC card settings are as above, 'allow power save' and allow to wake the computer. Magic packet is turned off as we want them to wake with a standard ping opposed to a WOL packet (just an extra step we would like to avoid when working remotely after hours). To me it looks as though it's not refreshing it's ticket or authentication for the 2k3 server like it should, once we log off then back on everything is fine. Unfortunately we are knee deep into 5-6 applications before we realize we are having the issue, just inconvenient. Thanks again for looking at this,

Hi, Have you got any failure information about this phenomenon , I mean it should give you some error information when you failed to reconnect shared printer. Also, can you ping the Windows Server 2003 after Windows 7 wake from sleep? Alex Zhao TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Alex Zhao TechNet Community Support

Thanks again for your time. The only failure information is an unable to print document message (pop-up). When we try to access the share directly we get a message that the server is not available. We can ping the server both by ip and hostname. We can network browse the server, but the shares are not visable. It is very,very odd to me. Thanks

Hi, I suggest you try to check the PRC(Remote Procedure Call) service, I suspect there is something disrupt the network traffic. Also, you could refer to the following article to see if it is helpful to your situation: Troubleshooting "The RPC server is unavailable" http://social.technet.microsoft.com/wiki/contents/articles/4494.troubleshooting-the-rpc-server-is-unavailable.aspx] Alex Zhao TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Alex Zhao TechNet Community Support

Thanks again for your time. I see what you are trying to say but I don't 'believe' this is it. During these events we do not have any trouble reaching a Domain Controller, browsing or executing something in the netlogon or sysvol shares. Also everything works as expected for a day or so, then once the computer goes to sleep and awakes >5 hours later this ONE servers features are not available. An immediate log off then back on clears the issue. Other workstations are able to access the features of this server during this time. Typically this user does not log out, they wait for the computer to sleep and that locks the session, when they return the following day and log in and the issue occurs. My concern is that it may not be refreshing it's Kerberos ticket or something else for this server and the old one is no longer valid, but for whatever reason it is not going out to get a new one. Access to all other servers functions just as it should. During this time all other workstations can access the server that this workstation cannot. There are no errors to speak of in the event logs but we do see Kernel_General messages that change the system time occur a number of times. There are also plenty of successfult Time-Service messages where the computer is synchronizing with a DC. The system time has changed to 2012-06-04T11:24:34.589000000Z from 2012-06-04T11:24:34.589588600Z.-early this morning 6:24AM local The system time has changed to 2012-06-04T11:53:52.500000000Z from 2012-06-04T11:24:38.192606300Z.-resume from sleep 6:53AM local The system time has changed to 2012-06-04T12:24:04.773000000Z from 2012-06-04T12:24:04.773436700Z.-Off to sleep again 7:24AM Local The system time has changed to 2012-06-04T12:59:25.500000000Z from 2012-06-04T12:24:09.219007800Z.-resume from sleep 7:59:25AM local The system time has changed to 2012-06-04T12:59:33.643000000Z from 2012-06-04T12:59:33.643214300Z.-resume from sleep 7:59:33AM local I have no other proof for my concept other than possible attempted network activity before the system updated the time at 7:59:25AM. There are no other questionable entries in any of the event logs anywhere. Unfortunately my security logs do not go back that far, but also are no error/failure events noted on the server either. Thanks again,

Hi, For checking the symptom, it seems a bit weird about it. I guess if the issue was caused by the kerberos authentication or not. In order to check this, we need to do the test below: When your client are awake after the sleeping, please access the shares by \\IPaddress, such as \\192.168.5.35. then to see if you can access that. By doing this, we could force the authentication status from kerberos to the NTLM. If IP works properly, then we could define if this is the kerberos issue or not. If the issue is related with kerberos, please try changing your kerberos etypes. For this, please refer to the article: http://support.microsoft.com/kb/978055 Thanks. Best Regards, Annie

Sorry for the delay, I was not alerted to your post. This is a DC, file server and print server. Normal UNC/IP viewing (\\ipaddress \\192.168.5.35) displays everything: restricted shares printer names redirected shares for all users my document folder NETLOGON and SYSVOL shares When this issue occurs we can ping the ip and when we attempt to network browse to the server the only thing we can see is: redirected shares for all users my document folder Yet we are unable to access any of folders or documents inside this share folder. This folder has the same share/ntfs permissions as the NETLOGON and SYSVOL folder. I would expect to see those as well. We are not using encryption (at least not intentionally) but if you feel the hotfix may help (or not hurt) I'd be happy to try it. But there are ne entries in the event log that point me in this direction only a theory, based on the events. Thansk for your time and sorry for the delay, Tom