Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
network drives showing up as local
- Thread starter Andronium
- Start date
- Thread starter
- #3
I tried that... doesn't work because for some reason it sees it as a local drive, not a network drive. Net use will only work for network drives. If you look in Expolorer, these drives show up with local drive icons, not with the shared network drive icon.
Network mapped drives need not be shared. My 10 or so network drives all show up as regular drive-icons. They are all mapped to hidden shares - not shared drives with the "hand" underneath them.
Is there a script that mapped them or something?
Take a screenshot in explorer, and email it to me - I cant picture what else you may be seeing..
JT@nserv.net
Is there a script that mapped them or something?
Take a screenshot in explorer, and email it to me - I cant picture what else you may be seeing..
JT@nserv.net
- Thread starter
- #5
I'm not talking about the "shared" icon with the hand. I'm talking about the network drive icon that has an icon of a drive with a cable connected below it. All network drives I've seen in the past have this icon. The ones in question do not have the cable on the bottom of the icon, thus indicating that they are local drives. However, I know they are network drives due to the drive letters and the contents. I try "net use /delete" with the appropriate letter, but it comes up with "network connection not found" just the same as if I was trying to do "net use c: /delete".
Have you logged in as administrator - and are they still there? After a reboot - are they still there?
It almost sounds like they were originally mapped with the AT command. Can you remap the same network drive, and delete it after that?
Sounds like you're OS is all corrupted.
It almost sounds like they were originally mapped with the AT command. Can you remap the same network drive, and delete it after that?
Sounds like you're OS is all corrupted.
- Thread starter
- #7
They only come up when logged on as the user who uses this WS. They didn't come up logged on as admin, but they don't go away with a reboot.
I can't remap it, because I can't disconnect/delete it to begin with. If I try to map over it I get "local device name already in use."
I'm starting to think the OS is messed up too. Oh well, it's not affecting the ability to work. I guess I'll just leave it alone until the drive letters have to be used for something else, which probably won't happen for a while.
I can't remap it, because I can't disconnect/delete it to begin with. If I try to map over it I get "local device name already in use."
I'm starting to think the OS is messed up too. Oh well, it's not affecting the ability to work. I guess I'll just leave it alone until the drive letters have to be used for something else, which probably won't happen for a while.
If the problem is local to the user, and not to all users, why not delete his/her profile, and log back on as the person so it rebuilds itself? Any previous profile corruption will then be eliminated - but you'll have to redo some of their settings (no big deal), and make sure you have them save everything they need 1st.
On NT, this has been the case many times with our users here. And most often the cause was renaming their accounts to a different naming convention. After a while, they became corrupt because the profile was named one way, but the username was named another way...NT wont rebuild a profile after renaming an account.
Give it a shot - It's a lot easier/quicker than re-installing the OS!
On NT, this has been the case many times with our users here. And most often the cause was renaming their accounts to a different naming convention. After a while, they became corrupt because the profile was named one way, but the username was named another way...NT wont rebuild a profile after renaming an account.
Give it a shot - It's a lot easier/quicker than re-installing the OS!
Boy does this sound familiar...
Exactly as you have described, but on my backup domain controller.
The fix for me:
I found an errant entry in the registry that locked the drive letter associated with the mapping. In my case I had mapped M: to a share (Fshift on D, on the local machine. All was OK until one day, after some software updates were installed, the M: began showing up as a LOCAL drive. M: did NOT show up in Net Use, I could not delete the mapping, nor could I Map M: again.
Found the errant entries (2):
HKLM\SYSTEM\CONTROLSET001\CONTROL\SESSION MANAGER\DOS DEVICES
and
HKLM\SYSTEM\CONTROLSET003\CONTROL\SESSION MANAGER\DOS DEVICES
The entry was M: \??\D:\FSHIFT
After deleting the keys, and rebooting the server, all returned to normal.
Please post if this was successful for you.
Exactly as you have described, but on my backup domain controller.
The fix for me:
I found an errant entry in the registry that locked the drive letter associated with the mapping. In my case I had mapped M: to a share (Fshift on D
, on the local machine. All was OK until one day, after some software updates were installed, the M: began showing up as a LOCAL drive. M: did NOT show up in Net Use, I could not delete the mapping, nor could I Map M: again.Found the errant entries (2):
HKLM\SYSTEM\CONTROLSET001\CONTROL\SESSION MANAGER\DOS DEVICES
and
HKLM\SYSTEM\CONTROLSET003\CONTROL\SESSION MANAGER\DOS DEVICES
The entry was M: \??\D:\FSHIFT
After deleting the keys, and rebooting the server, all returned to normal.
Please post if this was successful for you.
- Thread starter
- #10
Hi David- I checked those entries in the registry and didn't find any abnormal entries. How did you find these entries in the first place? Is there some way that I can search for bad entries that could be causing this problem in another location?
Andy
Andy
- Status
Similar threads
- Locked
- Question