|
|
 |
|
|
Pages: 1
Persistent mapped network drive
(Click here to view the original thread with full colors/images)
Posted by: Dream
On one Windows 2000 Pro computer in a Windows 2000 network, I have a peculiar problem with a network drive. Normally mapped drives are unique to individual users but this one is coming up for all users and with a red cross to mark that connection has failed. If you click on it, though, you still get into the network folder it's supposed to point to. I don't want this drive to appear for all users but I can't remove it because it claims not to be connected. Any ideas how it might have got where it is and how to get rid of it?
Posted by: Kdr Kane
The red X on the connection merely indicates the connection has timed out. When you click on it, the red X goes away because the connection is re-established using the user's credentials.
I can't really tell you why the drive is mapping since I don't have enough information. It's probably due to a logon script or something in the users' account profile. Dunno if you're using Active Directory or not.
I don't really want you to post information that could compromise your network (assuming it's work related). But, you need to identify how your drives are normally mapped.
Posted by: Dream
Actually this happens as soon as the machine is booted. I don't think the drive is being mapped by a log on script (not one of mine anyway). It is actually mounted for all users (it's listed as a mount point in the registry). I don't want it to be. Only the users who need this folder should get it. It The drive letter U: is mapped to a folder on the server. I don't think the connection has timed out. I can connect to the folder via the drive link, I can read from it and save to it, but the red cross stays. If I try to disconnect from the folder to free the drive letter, Windows won't let me because it claims there is no connection.
The computer is an old 400 MHz Pentium 2 with 256 MB memory and a 3COM network card and running Win 2000 Pro. There's not much more I can say about it. It's just used as a workstation and people save their work on the server in a folder mapped to the drive U:.
I think what I want is to stop the computer trying to mount this as a drive at boot up but I can't figure out how to do it.
Posted by: Dream
Oh yes, I do use Active directory but I don't think that's a factor. All the other computers in the network do what I want.
Posted by: Kdr Kane
You keep mentioning that the computer is mapping the drive. However, it's not the computer mapping the drive, it's the user logon. The machine has to be using some user account to bring up Explorer.
Check the homedrive mapping in the user profile in AD.
Run the command "set" at the command prompt to determine if there is something in there that is mapping the drive.
Posted by: Dream
Sorry about my stumbling descriptions. I put it that way because ALL the users have this coming up on this machine (and only on this machine) even though it isn't in their profiles. Where I have a map to U: in a profile, the user gets Error 85 - Local drive already exists.
I haven't tried the set command yet, though. Thanks for the tip. I'll try that out tomorrow (I'm in Europe and it's coming up to midnight).
|
|
|
|
|
