guys i'm pretty experienced with windows stuff and this is actually an old Microsoft-fail that still haunts us in the age of windows 10. looking for a cure:
We have shared resources living on a server in a small LAN: accessed by everything: Droids, IOS, windows 10 [three clients and counting]. The resources we need are successfully mapped in the 3 clients and work pretty much flawlessly, as long as the connections are manually "provoked". If the client sleeps [windows 10 style], or turns off, or restarts, the mapped "drives" will be marked with the big red X, meaning they are disconnected. Unfortunately, almost no app [such as your life-saving automated backup routines] will wait on such a condition: they'll just exit with an error.
anyone know a SURE/tested solution? even 3rd party?
-
Are those Wi-Fi connections?
-
Can you open my computer and refresh to bring the mapped drives back?
Sent from my iPhone using Tapatalk -
Yes, that's the drill. try to remember that they're disconnected, open something, manually provoke the connection.
both wifi and wired. it is an old problem afflicting millions copied over from 7 to 8 to 10
Some say it is a timing problem at login which MS declines to remedy.
others say it is a builtin group policy default issue [I don't understand: but there are defaults in windows clients that assume that if one is on a LAN, one is on a Domain... go figure] -
Have you tried with a different switch in between the clients and file server? Maybe it's closing the connection when the client is asleep or off?
-
no, again, it is a longterm windows issue on the client end. non-use = disconnect no matter what, except for an intervention requesting something on the mapped drive [that is disconnected]. the best answer seems to be to write a script that will request/inquire of something on the mapped drive at intervals. otherwise, no go
what is more bothersome is that the application providers [like the backup applications] must know this is a risk... one would think they would have an option to toggle that would make a request at the other end, rather than just bailing with an error when it sees a disconnect condition.
Any fix for failed-reconnect to mapped drives? win10
Discussion in 'Networking and Wireless' started by cognus, Sep 28, 2016.