How to disable automatic drive mapping?

[MikeCoyle]

Maybe I'm just stupid - I have one W2k laptop and a number of PC's (various OS's), only the laptop automatically assigns a drive letter when it connects to a dafualt C drive share on another PC. This is causing a program to hang (ie launch ACT program - Dbase is on PCx, connects to
PCx with next avialable drive:- ie E and doing a net use shows E: \\pcx\share name).
On all other PC's net use only shows that the connection is open with no drive mapping....
Any ideas.
Many thanks.

 

[bcastner]

net use /persistent:no

 

[MikeCoyle]

I've deleted the old mapped drive (say, E: for example). I've also tried assigning a few other mapped drives (say E: F: and G: to other locations), when the program launches, my PC still assigns the connection the NEXT available drive letter mapping, (ie H
So it's not a persistent connection, (ie it's gone on next boot).... What I need to do is find out why it assigns it a drive letter.

 

[bcastner]

I am a little confused. If the reference in the shortcut is to a FQDN, there does not need to be an assignment.

If you are using NET USE there has to be a device assignment.

There is a difference between:

\\server_name\share_name\file_name.ext

and the use of:

net use \\server_name\share_name

I note too that you are referring to the use of the Administrative shares (the default drive$), and there are local policy as well as Group Policy considerations that can possibly lead to your differences.

Can you repeat the behavior under a different logon profile from the same machine? The difference would clearly be a policy object.