Hello everybody,
As nobody answered to https://social.technet.microsoft.com/Forums/en-US/2b83691e-8cee-4950-96e2-a08c5ebce1c6/mapped-network-drives-disconnect-after-some-time?forum=winserverfiles for months now, I re-post here:
A customer is running Windows Server 2019 Terminal and File servers. The terminal servers map network drives to a file share on the file server. We have problems with two applications, because the network drives are in a disconnected state after some time:
- One has an Access database residing on the file server, accessed from several users. Access crashes on disconnect because its file handles to the database file do not work any longer.
- A .net desktop application is used and its .exe and .dll reside on the file server. The users start the .exe from the mapped drive. When the mapped drives goes into the disconnected state, and the application needs to load something from one of its DLLs, the application crashes with an unhandled exception. The event log says that the .net runtime could not continue because the network connection was disconnected.
We have followed https://support.microsoft.com/en-us/help/297684/mapped-drive-connection-to-network-share-may-be-lost and set the LanManServer parameters to disconnect after 5000 instead of 15 minutes (on the file server), and set the LanManWorkstaition parameters to disconnect after 65535 instead of 600 seconds (on the terminal servers). But this did not help.
I guess we do not need to discuss whether Access databases are fantastic or file servers are fantastic or running .exes from file shares is fantastic ;-) The question is simple: What can we do to keep the network drives connected, please?
We have already tried net config server /autodisconnect:-1 but it did not solve the problem.
Best Regards,
Stefan Falk