net use persistent:no

Custom / CUSTOM
January 28, 2010 at 06:19:20
Specs: Microsoft Windows XP Professional, 2.401 GHz / 2047 MB
I'm using the below command to setup a connection to another computer:

net use K: \\machine002\sharename /PERSISTENT:NO

I can make the connection, no problem. But, when I restart the computer that has this mapping, and the computer to which this mapping refers to, is down ... the connection is still listed in Explorer.

Obviously, when you click on it then, it'll say it cannot view the content.

But my question is, I did specify PERSISTENT:NO ... so, I don't expect the drive to be there, if the network connection isn't there on moment of booting. Secondly, when you click on it (in explorer) after stating the mapping cannot be viewed, he does not remove it automatically (he could), and also, he does NOT show the mapping symbol (the one to the left of the name of that drive) with a red cross (to indicate the network drive is not valid).

It seems like someway he still thinks the drive is there ... ?!

What is wrong ?

See More: net use persistent:no

Report •

January 28, 2010 at 16:40:05
The "Persistent:No" switch only disables automatic log-on after a reboot or log-off. It does not hide the connection when it's down.

Report •

January 30, 2010 at 03:23:03
I don't 100% understand that ... it means that if you choose "persistent:no", it still is persistent ... because if I do not do anything, BUT while the server I map to IS active, it will just show as available.

Which is exactly the same as what happens with "persistent:yes"

If I get it right, I need to manually delete the mapping myself, after checking that it is NOT available, because the persistent parameter does not do what it proposes to be doing ...

Report •

February 1, 2010 at 09:06:33
The mapping seemed to be made (earlier) with persistent:yes, and I thought it was been reset, with the No-option, but it wasn't. It's working correctly now.

Report •
Related Solutions

Ask Question