sglee
asked on
Can't Map Network Drive
I have a situation where I can't create a mapped drive (G:) pointing to user's default network folder.
This morning the user said that he could not connect to his network folder - G drive.
G drive is in the login script (net use G: \\server1\%username%).
When I looked at his "My computer" this morning, it says "G drive ... disconnected". I right clicked on G drive and chose "disconnect", but I would not work. So I ran "net use G:\ /DEL" in Command Window. After several trials, G drive was gone from "My Computer", but I logged off and logged back in, it fails to create the G drive in "My Computer".
So I run Command Window again and run "net use G: \\server1\"username", it says "it is in use". For testing I log him into the Terminal Server using his remote desktop, all the drive letters work just fine including G drive. So I ended up creating a short cut on this desktop "\\server1\"username" temporarily.
Do you have any suggestions other than deleting current profile and created it?
This morning the user said that he could not connect to his network folder - G drive.
G drive is in the login script (net use G: \\server1\%username%).
When I looked at his "My computer" this morning, it says "G drive ... disconnected". I right clicked on G drive and chose "disconnect", but I would not work. So I ran "net use G:\ /DEL" in Command Window. After several trials, G drive was gone from "My Computer", but I logged off and logged back in, it fails to create the G drive in "My Computer".
So I run Command Window again and run "net use G: \\server1\"username", it says "it is in use". For testing I log him into the Terminal Server using his remote desktop, all the drive letters work just fine including G drive. So I ended up creating a short cut on this desktop "\\server1\"username" temporarily.
Do you have any suggestions other than deleting current profile and created it?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
And when I try to map it again after deleting the entry in registry, I get this.
is the logon script still running for this user? try disabling it, delting the reg entry again and rebooting see if it comes back. did you flush netbios?
if you do "net use g: -delete" can you then re-use the letter
if you do "net use g: -delete" can you then re-use the letter
ASKER
it was false alarm. Here is what happened.
Apparently his Motorola cell phone occupies two drive letters. In a typical senario, his "My Computer" would look like this:
HD (C:) CD/DVD (D:) External USB (E:) Motorola Phone (F:) Motorola Phone (I:)
<Login Script>
net time \\Server1 /set /yes
net use L: \\Server2\Ron
net use G: \\Server1 \%username% <------ G drive
net use H: \\Server1 \folder1
net use K: \\Server1 \folder2
net use M: \\Server1 \Music
net use P: \\Server1 \Photos
Now what happened this moring was:
(1) Last night I logged onto his computer remotely using administrator account.
(3) The user restarted his computer this morning and found out his G drive was "disconnected".
(4) Apparently he plugged his Motorola phone to the computer in order to charge it. That is when it took over the driver letter G instead of normal letter "I" which is next drive letter in order.
First of all, my bad. I should have paid attention to each drive letter on his "My Computer". Now I could see that G drive as taken up by Motorola. I simply missed it. Once I had the user remove USB and his Motoroal phone, log off and back in to let login script to be executed, and replugged them back in one at a time, all was ok with G drive pointing to his network folder.
I am sorry about wasting your time and again I should have paid attention to the top portion of "My Computer" first thing. I only looked at network drive section of "My Computer".
No wonder the G drive came back in registry (MountedDevices) came back even after I deleted it and restarted the computer...
Thank you all.
Apparently his Motorola cell phone occupies two drive letters. In a typical senario, his "My Computer" would look like this:
HD (C:) CD/DVD (D:) External USB (E:) Motorola Phone (F:) Motorola Phone (I:)
<Login Script>
net time \\Server1 /set /yes
net use L: \\Server2\Ron
net use G: \\Server1 \%username% <------ G drive
net use H: \\Server1 \folder1
net use K: \\Server1 \folder2
net use M: \\Server1 \Music
net use P: \\Server1 \Photos
Now what happened this moring was:
(1) Last night I logged onto his computer remotely using administrator account.
(3) The user restarted his computer this morning and found out his G drive was "disconnected".
(4) Apparently he plugged his Motorola phone to the computer in order to charge it. That is when it took over the driver letter G instead of normal letter "I" which is next drive letter in order.
First of all, my bad. I should have paid attention to each drive letter on his "My Computer". Now I could see that G drive as taken up by Motorola. I simply missed it. Once I had the user remove USB and his Motoroal phone, log off and back in to let login script to be executed, and replugged them back in one at a time, all was ok with G drive pointing to his network folder.
I am sorry about wasting your time and again I should have paid attention to the top portion of "My Computer" first thing. I only looked at network drive section of "My Computer".
No wonder the G drive came back in registry (MountedDevices) came back even after I deleted it and restarted the computer...
Thank you all.
No worries, we all do that every now and then and get panicked about things not working!
glad its all sorted
glad its all sorted
ASKER
sgsm81, Thank you for pointing out the problem.
Neal58, I learned something new (regarding MountedDevices in registry) and thank you.
Neal58, I learned something new (regarding MountedDevices in registry) and thank you.
ASKER
I saw "\DosDevices\G:" in Registry. So I deleted it and restrated the computer, but it came back.