• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 415
  • Last Modified:

Mapped Drive No Longer Works

We have a user whose network drives, mapped through group policy, no longer work on his computer (Could not reconnect all network drives).
When he logs on to another computer the drives connect normally.
When another user logs on to his computer, their drives connect normally.
We tried manually mapping an additional drive to the same share, but that failed.
We can successfully map a drive to another server.

We believe that deleting his user profile and rebuilding it will probably fix the problem, but we’re interested to see if there may be other solutions available.
0
pmdadmin
Asked:
pmdadmin
  • 6
  • 2
1 Solution
 
Seaton007Commented:
Have you tried deleting all of the old mappings first?

If there is a logon script that maps the drives, then you can run the following command to remove all drive mappings:
net use * /delete

Then log off and back on and see if the mappings work.

As another option, here is a script you can use to remove all the old mappings and then map new drives:
'***************************************************************************
' Script Name:	MapDrives - Remove All First.vbs
'      Author:	Seaton007
'     Created:	July 2012
'
' Description:	Removes all network drives and then maps new
'				network drives.
'***************************************************************************

' Remove all currently mapped network drives
Set objShell = WScript.CreateObject("WScript.Shell")
objShell.Run "NET USE * /delete", 2, True

' Map new network drives
Set objNetwork = CreateObject("WScript.Network")
objNetwork.MapNetworkDrive "DRIVE_LETTER:", "\\SERVER_NAME\SHARE_NAME", True
objNetwork.MapNetworkDrive "DRIVE_LETTER:", "\\SERVER_NAME\SHARE_NAME", True
MsgBox "Finished mapping drives.", vbOKOnly+vbInformation+VbMsgBoxSetForeground, "Finished"

Open in new window

Paste the code in a text editor, then replace DRIVE_LETTER with the correct drive letter and replace \\SERVER_NAME\SHARE_NAME with the correct path, then save it as a .vbs file and run it.
0
 
pmdadminAuthor Commented:
We disconnected the drives in Windows Explorer and removed the registry entries at HKEY_CURRENT_USER\Network\, but we did not try “net use * /delete”.

Unfortunately, this is happening on a laptop (probably the source of the problem) and the user is out of the office for a few days.  I’ll ask him to establish a VPN connection and try this when he can.  Thanks for the suggestion.
0
 
JeffBeallCommented:
how about removing the problem pc from the domain, then re-joining it? maybe there's something goofy in the group policies.
I had some computers that acted really strange, it seemed like some policies where applied and others weren't. I think it was local policies interacting with domain policies.
I know that domain policies over-ride local, but it seemed to help some of my weird pc problems.
0
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 
pmdadminAuthor Commented:
Thanks, Jeff.  We tried that, too.  No luck.
0
 
JeffBeallCommented:
I can't help but think it's something with group policies.

when you say that the shares "no longer work on his computer" do you get a error? do you click on the shares and it says something like "access denied"?

also, when you said

"We believe that deleting his user profile and rebuilding it will probably fix the problem"

I'm not sure because his profile works on another machine. I think that would suggest that the profile is fine, but the computer is the problem

How about resetting the local security settings?
0
 
pmdadminAuthor Commented:
I’m referring to the Windows user profile on the laptop.  I think the problem is somewhere in that profile since it only happens when he logs on to that particular computer, and only when he is logged on to it – not when anyone else logs on to the same computer.

The drives are mapped, but won’t connect.
0
 
pmdadminAuthor Commented:
The "net use * /delete" technique did not work.
0
 
pmdadminAuthor Commented:
I'm not sure what caused the problem, but recreating the user profile fixed it.
0
 
pmdadminAuthor Commented:
This was the original solution that we had.  No alternative ideas worked.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 6
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now