This has been a thorn in my side for over a month now. I have once again decided to fix it for good. Server is Debian 6.0.1 running Samba 3.5.6 running in VirtualBox on a Debian 6.0.1 host. 15~20 or so client computers connecting to the samba server. A bunch Win XP (some virtual) a couple Win 7, ubuntu, and 3 Windows 10 from hell boxes. Everything works perfect except the Win 10 boxes which drop the connection now and then. I think I might have 2 of the 3 win 10 boxes mostly stable but I would not bet on it. The drives were all mapped using "net use" to a static IP I am not entirely sure what is causing the drives to become disconnected. The drive will show a red X in file manager. "net use" from a dos window will show the drive mapping with "disconnected" next to it. If you click on the drive in file manager it reconnects without question or issue. It's fine as long as all that you want to do is access it from the GUI by clicking on the drive. However, that's not all we need to do. I have made so many tweeks and adjustments to the Win 10 machine I can't begin to tell you everything I have done. I will say I have made a number of registry changes with regard to timeouts (however I don't see a fixed amount of time before it fails), I have turned off all firewalls, anti-virus, and any other security items I can find. I have disabled IPV6. I have turned off every power saving feature I can find related to networking or not. And a few other things that slip my mind right now. The application that is an issue for us is a FoxPro data base app. However, I see this happening without the app running. The Win 10 machines that seem to be working are 1 win 10 pro 64 bit & 1 wifi laptop (always plugged in power) win 10 pro home or some such thing. The consistent fail (given time) is another win 10 pro 64 bit. All of them started out with the same issue, but, I have been able to fix two of the 3. Also of note is that last fall I tested a the same kind of win 10 pro 64 bit box on the network and it worked perfect without any tweeks. I suspect this is all related to some Microsoft security "enhancements" or the infamous November update (1511). I have done a fair amount of searching the internet on this and have found a ton of people having issues with win 10 drive mapping disconnects but no hard and fast fix. Just a bunch of "This worked for me" answers and a bunch of other people saying it did not help them. Does anyone have a step by step procedure oriented process that consistently works to resolve these disconnects? I have a bunch more of this type of upgrade that I will have to take care of in the next few months. Any 3rd party network clients/protocols I could try?

The biggest item that has helped me with Windows 10 mysteries is ‘regedit’. Just use the registry (Run as administrator), mostly in ‘HKEY_LOCAL_MACHINE’, to make the logged in user or ‘everyone’ owner and with full privileges of the challenging software. I also have found it useful that anyone or anything outside the Win10 box (that needs access); should have an account with full privileges on said Win10 box. Later, JohnA