Discussion Locked

Mapping drives on NT 4.0

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

Hi. I have 3 network drives from my NT server mapped to drive letters on my
desktop. They are F:, G:, and H:. I have these drives set up to re-map on
login. However, the drive mappings seem to be multiplying. Now I:, J:, K:,
L:, and so on toZ: are all mapped to one of the 3 network drives. Has
anyone ever seen this problem before? Might someone be able to provide me
with a solution? Thanks!

9 replies

by bschorr

Do you, by any chance, have a batch file running that maps network drives? Perhaps in the login-script?

Once you've set those drives to remap on login, you don't have to manually (like in a script or batch file) remap them each time.

Aloha,
-Ben-
http://home.hawaii.rr.com/schorr

by gat0r

try this :

net use j: \\server_apps1\apps /PERSISTENT:NO

This will tell it to be a non persistent connection. Then you can map drives in your login script based on groups like ifmember then map this drive, etc.

I have also seen this problem with a corrupt version of Netware Intranetware Client. Had to remove it and the problem went away.

by loc

If you are only using the login script to ease server migrations in the future, you can try this:

Disconnect the drives letters each time before mapping them. Here is a sample:

IF EXIST F:\NUL NET USE F: /d
NET USE F: \\servername\share name

We use something similar to this and we never had any problems.

by trs suresh

Are you sure that you are not using

Net use * \\servername\sharename

because * using the next available drive letter.

In your script, are you checking for existing connection like if F:\ is already exists then delete f: kind of stuff..

This discussion is closed to new replies.