Windows 10: Server won't go back to sleep once accessed by Win 10 client

This was tricky to summarize in the title so:-

I have a Win 7 pc running as an ftp server and NAS on my network plugged into one of the LAN ports of my router. Normally this is in hibernation mode and I use WOL from clients to wake and acccess the shares etc. After a few minutes of inactivity the pc goes back into hibernation as per the power profile settings.

This was initially set up on an all Win 7 network and has always worked as expected.

I now have a Win 10 device which (after a long slog) works with this setup, with the exception that once the remote server is woken from this device it never goes back into hibernation, even after shutting down the Win 10 PC. I have to manually force it at the server from whence it behaves normally until the next Win 10 client access.

The hibernation works normally when the clients are win 7.

I realise it may be a Win 7 issue but any insights regarding what Win 10 might do differently would be appreciated.

:)

 

Using win 10 and a Hyper-V virtual client

Thank you. Can I open one application from the host client(win 10) and another application from the guest client (win xp) at the same time? Can I access and use the open windows displayed from the two applications on the fly?

The host client AND the guest client are accessing the same server to retrieve data.

 

New Outlook bugs 7/13/2016

I am still unsure what you are using. If you are not using a browser to access your email that is the native win 10 app (called mail), if you are using a browser it is called Outlook mail.

You do not have to use the native mail app if you dont like it. You can always get your mail in a browser.

If you are using a browser (outlook mail) once an account is migrated there is no going back to the previous format

You can also use an email client (like windows live mail) which has the added benefit of backing up your data (the online servers are not backed up)

 

Some running task is causing Windows 7 to do that. If you are just going to use it for FTP file shares and Samba, there are products out there like Zentyal and Nethserver that do a lot better job than Windows will ever do.

 

No there's not.

 

I would tend to agree , it's likely just a difference in the OS's and how they handle this situation , Win10 maybe leaving a port open or something to keep the Connection "live" or it maybe a bug? I am not sure.

Is netbios enabled on the Win10 PC ? the Default setting does not work on all Win10 PC's I have found

Any reason not to put 10 on the Server Too?

 

Umm yes there is. If you want help, you need to not come back and tell someone that your problem is not what they state that it is. If Windows or any OS is not going back into S3 state, that means there is a running task or hung process that is causing it to stay awake. The other is that there is a IRQ conflict from a device that is not releasing, so you end up once again a machine that stays awake.

If you want the machine to run for only FTP or media sharing, use a proper OS that is created for that, not a desktop OS.

 

Well I guess it depends a bit on what you call a "Task" but TCP has timeout values or "keep alive" settings etc, I think FTP has similar features , no matter what M$ says there always seems to be issues using different versions of Windows to Network over the LAN.

https://support.microsoft.com/en-ca/kb/813827

Tuning Windows for TCP/IP performance


Things that you may want to know about TCP Keepalives nettracer

 

Microsoft does not state anything other than what it could be, but not what it can be. They can only tell you about their OS, not what happens if you are trying to use it for what it is not meant to do. A desktop OS is not meant to be used as a Server. Once again if you want to run a FTP server and one that is very secure, use Zentyal or Nethserver, which are very user friendly for those who do not want to take the time to do it from the Command Line Interface or use a web interface like Webmin to set up.

Also a Headless server running Zentyal or Nethserver is going to be a whole lot lighter on resources and not get hung up because of some piece of code garbage that Microsoft's software engineers left in and did not delete.

I have a Raspberry Pi 3 that I run a SSD on for a file storage server when I need it. Three computers pulling files off of it, barely even makes the little sucker break a sweat.

 

Yeah, I assumed it was something of this nature. However I have gone through every Lanmanserver/workstation, TCPIP,NetBios,NetBT and SMB setting I can think of/find out about with the same result :-/

Actually the ftp server hasn't been running during this time, I've simply been accessing shares between two networked PC's.

I have disabled Cortana and indexing on the win 10 client and offline files on the Win 7 box to no effect.

The only thing that made a difference was turning off the "Computer Browser" service on the win 10 client, in which case the Win 7 machine went into hibernation after about 15 mins (not timed) which is the default (i think) for remote connections although I'd already configured every possible setting for 1 minute for testing purposes.

Although some part of me wants to know the answer, I think I'll quit whilst I'm behind ;-)

 

Perhaps the Win10 Comp. thinks it is the Browser Master being the only Win10 Comp on the Lan , so it is always busy trying to negotiate that with the other members of the Workgroup ?

Time to make the Win7 Comp a member of the New World Order *Smile

 

That has nothing to do with it. SMB/CIFS does not cause this kind of behavior. It is a hung process when it wakes up but never gets a task request to go back to sleep.

 

@Onum , what version of Win10 are you using ? there were issues with SMB in some versions and disable SMB 2 and 3 fixed it temporarily but I thought they had fixed that ?

Solved Samba Shares don't show up in Windows 10 Network - Page 2 - Windows 10 Forums

https://support.microsoft.com/en-us/kb/2696547

More info on the Synology website , and one post saying it was his Win7 computer causing the issues

Windows 10 Version 1511 and SMB3 - Page 7 - Synology Forum

main thread: Windows 10 Version 1511 and SMB3 - Synology Forum

 

Well, it only seems like I've gone and bloody fixed it *Biggrin

To cut a long story short, the one thing I hadn't tried was running the "turning on the SMB client protocols" CMD line entries detailed in the MS KB article on the win 7 machine. After all AFAIK they are enabled by default and I've never disabled them, the SMB issues were on the win 10 side.

Since doing that the behaviour of the Win 7 box when accessed from the Win 10 client is as desired, ie the system drops into hibernation shortly after the shares are no longer being accessed.

 

Great ! *Smile did you enable SMB 1 or 2&3 though? You used the Server Fix for Win7 I guess ? (or the Client fix?)

KB