Discussion Locked

Drive Mappings Disappearing

0 helpful
29 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Can anyone tell me why drive mappings disappear on Windows NT 4.0. Also we have Windows 98 laptop users who loses their drive mappings too. What can cause this to happen.

Thanks,
Gerri

29 replies

by tim

When you mapped the drives for the first time did you put the check in the box to map the drive the next time you logged in?

by bdg

If you want to map from the Explorer in the 'Map Network Drive' dialog box you have to check the checkbox 'Reconnect at Logon'.
Second way is to type something like this in command prompt :
net use m: \\server\my_drive /persistent:yes

by kevin_b

I had something similar, but on a novell network witn NT4 clients. Turned out it was bad cables that lost connectivity and the user ended up getting logged out and lost thier network mappings. For the laptops, check screensavers and power/sleep modes to make sure they aren't messing up the network connectivity.

by hjs

I have had this happen. We use windows scripting host and for what ever reason it just stops working. I just reinstall scripting host and it work fine.

by jimkennedy1

I recently (past 30 days) in one of the weekly computer magazines read about a site that had the same problem for some 6 months. The Network Manager even had a Microsoft Engineer working with him for awhile. Then he finally found out (but not fromMicrosoft) that it was a Win NT bug and a fix was going to be available. I experienced similar disappearances on my NT and UNIX network at my previous job and we never could determine the cause. Best of luck.

by bonnie.mcnamara

We have had the same problem with NT, where the network links disconnect themselves if they are not used for a certain period of time. Although we have not determined the cause, we have just created a batch file that relinks the drives for now.

by fxia

When you map the driver make sure that you login as a domain user, and click the box labled "connect to driver when the next time you logon". Next time you should still log on as a domain user account. Then you will not lose the drivers unless you are not connected properly to the server.

by cyril

Don't you use mandatory profiles with no mappings defined? It prevents reconnecting mappings at logon...

by cyril

Don't you use mandatory profiles with no mappings defined? It prevents NT from reconnecting mappings at logon...

by vperrin

We have had this problem as well, primarily on laptops. When the user returns to the office from traveling, we continually have to remap the drives. Am interested in this "patch" that MS says they will have for this problem. Any other suggestions?

Thanks

by reggie

I have seen the same thing. WE use scripts to map shares. One thing that has seemed to resolve this is to use:
NET USE * /DELETE /YES

Example:
NET USE * /DELETE /YES
NET USE H: /HOME
NET USE O: \\SERVER\SHARE
NET USE S: \\ETC\ETC

at the beginning of the script. Remember you can use scripts in the startup folder if you are not connected to a domain.

by i_need_help

We had this problem. We were mapping drives from a login script. The replication of the login script was not working correctly...therefore if anyone was authenticated by and server except the PDC their login script didn't run and therefore they didn't get their drive mappings. We manually copied all the login scripts across to the other servers and that corrected the mapping problem. We are still working on the replication problem. Hope this helps.

This discussion is closed to new replies.