anyone know a fix for this? Microsoft doesn't.
on my windows 10 systems [three of four], all Windows 10 HOme x64, we have shared resources mapped from a windows 10 Pro machine acting as server. everything works fine except that the connection will not be present after the client sleeps or restarts or whatever. Red X through the shared mapped drives. any accessing of the resource manually invoked will immediately re-establish the connection.
I saw an interesting tutorial that claims to solve this by adding a registry key to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem . Problem is, there is no such group on my registry[s]. Is this because there is no Group Policy Editor feature on Home edition?
tutorial here: Fix: - YouTube
is there a way to get happiness here? the huge downside to this ongoing problem [since xp days] is automated backups... the one I use, Macrium, will not awaken the re it sees the 'drive' as unavailable and errors out.
pls clue me in
BUMP
this thread explains, by way of example, why this is important, and why workarounds must be employed [thank you Microsoft]
So are you telling us how to fix your problem, even though it is in the tutorials for those who need the info? If you have solved your problem on your own, you need to mark the thread as solved.
I must be doing something wrong, when mapping a network share I simply select Reconnect at sign-in:
Map Network Drive in Windows 10 - Windows 10 blog
The share is OK every time I sign in to Windows.
I'm impressed, Kari. I have 3 systems using a common share [all 4 windows 10], and all 3 "clients" have the resources mapped that way and all will dismiss the connection when idle a long time [I don't know the interval.]
Actually, Windows 10 production versions do default "Reconnect" active.. on. so one would have to deliberately UNcheck to miss it.
Bro - that particular thread actually has several different scenarios being described without aid of common terms - So it is easy for people to assume the other contributors are talking about the same behavior but .. not so. for instance some are speaking of drives that simply disappear, as though the mapping was dropped altogether, while others are speaking of 'disconnected' resources [timed out].
The simple at-startup script approach does make the drive live just after logon but it will still drop when idle for some period of time. [and, I like to leave such links for future fellow-travelers who are searching the issue before posting. the threads can help a lot]
I'm trying out the map-as-internet-resource suggested by one person. all my test-dummy systems busy for now so will watch over the next 48 hours or so as they go un-busy.
for others with a Server/workstation arrangements [i.e. SBS2011 & win10 workstations] in play and policies thereof, this thread discusses such. The group policy edit seems to have some converts in some situations. that is not what I'm dealing with but others vary
cognus if you have solved this issue, you need to mark it as such. The information you are pointing out is already in a Tutorial on this site.
@cognus, you are looking at the wrong end of the connection - the clients. It is not any of your three W10 Home systems that are dropping the connection. It is your W10 Pro server. This is by design to stop servers wasting resources on connections that are unlikely to ever be used again. You can configure your server to never drop connections, apparently....on my windows 10 systems [three of four], all Windows 10 HOme x64, we have shared resources mapped from a windows 10 Pro machine acting as server. everything works fine except that the connection will not be present after the client sleeps or restarts or whatever. Red X through the shared mapped drives. any accessing of the resource manually invoked will immediately re-establish the connection.
I saw an interesting tutorial that claims to solve this by adding a registry key to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem . Problem is, there is no such group on my registry[s]. Is this because there is no Group Policy Editor feature on Home edition?You can find the LAN Autodisconnect parameter in the registry under the subtree HKEY_LOCAL_MACHINE under the subkey: SystemCurrentControlSetServicesLanmanServerParameters
NOTE: The preceding entry must be located on the computer that has the share or shares.
The purpose is to disconnect idle sessions after a set number of minutes. The number of minutes can be set at a command prompt using the net config server command.
For example, to set the Autodisconnect value to 30 minutes, you would run the following command line: net config server /autodisconnect:30
The valid value range is -1 to 65535 minutes at the command line. To disable Autodisconnect set it to -1.
...
NOTES:
- It is preferable to modify the LAN Autodisconnect directly in the registry.
