Troubleshooting this can be difficult - I would start with running some persistent pings (perhaps saving them to a log file) to see if the network drops completely, even for a moment.
#Netdrive remove speed limitation update
Update will make the drive if it doesn't exist, and replace it if it does. Replace will only put in the settings you want if the drive letter itself already exists, but will not map a drive that does not yet exist. You want that policy to run every time it can to verify that the settings are correct. For the record, I use Update for drive mapping all the time, and I never check apply once. This would indicate that the problem is not being caused by the group policy, as it would be a lot more consistent and would generally happen right away. The mapped drives would work while on the correct subnet, and fail when switching to the other (as expected), but would not always reconnect when switching back to the correct subnet, forcing me to restart.Īlso, from your description it sounds like this happens randomly while working, and not typically right after a logon or reboot. I was working with a system a few days ago where I was switching a system back and forth between two subnets on the same physical network (there was a reason for this, but that's another story). It may not even be a complete disconnect, but either a failure to connect to an authentication server, or a DNS issue, especially if mapping via UNC path. If the network drops for a period of time, I have seen many times that network drives may disconnect, and will not reconnect again until a reboot. I know that you said you don't think it is a network problem, but from what you are describing I think that is what you are experiencing. Does anyone know of any Window update changes or anything else that might be causing this issue with our drive disconnecting intermittently? We started seeing a lot of these troubles starting around 3 months ago. These were recommended settings when we first setup this mapped drive a long time ago. We have the mapped drives configured through group policy with the action "Update" and to "Apply Once" It doesn't seem like a network issue because I have verified the user has a network connection and can ping the server that hosts the drive from the users computer and the fact that I don't see the red "X" on the drive, it just gives that error when trying to access it. It doesn't seem like a permission issue because I can re-map it and access is restored. It's tough to isolate this because it does not happen with all people, just randomly to random people. Usually the user either has to sign out then back in, or reboot their computer, and sometimes the only thing that works is re-mapping the entire drive.
Users are getting disconnected from a shared network drive with the error: We have been having a trouble recently that has been coming up often.
0 kommentar(er)
