Sometime, I got an issue that client’s windows os lost the connection of Mapped Drive to File Server… So I did a research on google for this problem… And today, I gonna try this troubleshot and see if it gonna be ok or not…
Here is some of result from the internet:
Mapped Drive Connection to Network Share May Be Lost:
https://support.microsoft.com/en-us/help/297684/mapped-drive-connection-to-network-share-may-be-lost
So, I have followed the above instruction, and tried to run this setting on my server:
net config server /autodisconnect:-1
Now, just let’s see how it’s going on after couple of weeks later…
If then, everything’s still the same situation, I will be mind on this article:
So I have one Windows 7 user, out of about 40 that seems to continually lose connection to mapped network drives. As I am not as up to snuff on network troubleshooting as I am on programming, I would appreciate some of your expertise in helping me to see what steps you would take to isolate and resolve this issue. I have already tried clearing the credentials and remapping but that doesn’t seem to be working.
At first, the user said that when trying to attach a file from the network drive to an outlook message, all of her drives would show the red x and say they were unavailable. So after running office diagnostics and remapping that problem appeared to not occur, but now she says it’s just happening by itself and not just Outlook. Hoping someone can enlighten me on this subject. Thanks.
Summary (edit): Here’s a summary of this thread.
1) Check the cabling run first as suggested by John White and Elgin8949. Try a whole new cable run if possible. (it’s good practice anyways and who doesn’t like a good cable run).
2) Check the power settings as mentioned in the post by Victor7655. This is the post that fixed my issue. It may not fix yours and is more likely to work with laptops.
3) Try the utility mentioned by GeoffOz.
If you have tried the above troubleshooting steps and are still having issues, I would suggest to open your own thread in the community to get fresher troubleshooting ideas.
https://community.spiceworks.com/topic/249929-mapped-network-dives-disconnect-at-random
Another found is here that I would like to try sometime:
After quite a good deal of research, I discovered that the actual source of the problem has nothing to do with the Credentials Manager, but instead relates to how the default group policies for SMB shares are set up when Windows 7 is installed. The default value is that the relevant policy is left unset, and that creates this problem when you wish to automatically log in to some SMB shares. This of course is how OS X drives are seen by Windows when they are set as mapped drives within your system, and that is why this problem seems to occur.
Fixing the problem requires editing the group policies. Not a difficult task, but it does entail changing some registry settings. If you are not comfortable with doing getting your hands dirty in the registry, stop now, or find someone who can do this. And be sure that you back up your registry before you start. If you screw up your registry, you might not be able to restart and use your system, so consider yourself warned.
To edit the Group Policies, we need to run the Group Policy Editor program. Press the Windows and R keys together to bring up the Run Program dialog, and then, in the Run dialog, enter gpedit.msc and press the OK button.After a few moments the Group Policies Editor will open.
In the Group Policies Editor, open each of the following items in turn:Computer Configuration/Policies/Windows Settings/Security Options:
Now, right-click on the “Network security: LAN Manager authentication level” policy item, and then, from the context (pop-up) menu, select “Properties”.
Now select the “Local Security Settings” tab, and then, in the dropdown box, locate and select “Send LM & NTLM – user NTLMv2 session security if negotiated”.
Now click the OK button, and then finally, you may close the Group Policies Editor window.The problem should now be fixed, and your mapped drive logins should now be persistent through multiple reboots of the system.
OR something like here:
Look like a DFS issue : Microsoft KB 983620
OR
1. Click ‘Start’ and Type Run
2. In the Run ‘Open’ box type Regedit to open the windows registry.
3. Navigate to the following registry folder:
HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> Mup -> Parameters
4. Right Click in the right hand pane and Select New -> DWORD (32 Bit) Value
5. Give it the following name: EnableDfsLoopbackTargets
6. Modify the newly created DWORD by right clicking it and selecting Modify or giving it a double left click
7. Enter 1 and click OK
8. Close the Registry and Reboot Windows
Let’s see…
