Network drive folder keeps closing with no error or warning

Posted by VarmintLP@reddit | sysadmin | View on Reddit | 5 comments

Hey guys, I'm facing a strange issue where people are "randomly" disconnected from their network drives as far as I know. The setup is the following. Server 1: Department Drives & Personal User Drives Server 2: General / Public Company wide Drive Both are running Windows Server 2019 Datacenter, are VMs and every user has access to their own Personal Drive, the public company drive and normally 1-2 Department drives. Now the issue is strange because I've never seen something like this before. The windows explorer windows just close. No error of being disconnected or connection closed plus there is no sign (yet) that the network adapter disconnected or has issues. When I test with a computer provided by the customer with the same setup I open the main shared folder and 6-8 random selected folders and keep them idle in the background. I noticed that they had disappeared when I switched between windows with Alt + Tab. I got a few rough timestamps but I would like to get some help to troubleshoot this issue. I'm currently looking at the Event Viewer but I'm not sure what event to look for and where to find it. I'm basically at the start of my investigation

5 Comments

[-]

Unable-Entrance3110@reddit

We had similar issues start to crop up within the last few months. It wasn't a widely reported problem but it was happening enough that it was annoying. During my last server maintenance window a month ago, I changed the SMB server's "AutoDisconnectTimeout" parameter to 60 minutes from default (15 minutes) using the Set-SmbServerConfiguration PS cmdlet. We haven't had the problem since, but I am not sure whether or not that was the root of the problem.

kammerfruen@reddit

How are you mapping the drives? Are you using GPO? If so, are you using create, replace or update? I encountered this issue many years ago where changing the action from 'replace' to 'update' solved it.

BuffaloRedshark@reddit

>I encountered this issue many years ago where changing the action from 'replace' to 'update' solved it. we changed to Update a few years ago too, I think for this same reason

VarmintLP@reddit (OP)

You know that, that might be actually the solution. I will look into this.

MrYiff@reddit

Yep, replace will delete the mapping regardless of any change causing any open files/folders to close (I've also seen it sometimes bug out and refuse to then recreate the map too). Update will only change the map if it differs to what is defined in the policy. My general rule with all the Group Policy Preference settings is that Update should be used as the default.

Reply to Post

5 Comments