How to get the command Net Use to work? 1

[jsteph]

I'm on a WinXP machine, trying to map a drive on an Win2k workstation. I get the error:

"The network folder specified is currently mapped using a different username and password...blah, blah"

I'm doing Net Use at the command line and there is nothing mapped from the target machine at all--not under any alias or anything else. Nothing in Windows Explorer either.

In the Share properties on the other machine, there is no limit on the shares. So why am I getting this error? Is there an undocumented switch for Net Use that will show all the folders mapped?? What's up with this? Thanks,
--Jim

 

[ChicagoTechNet]

This is the XP credentials issue. quoted from http;//

http://www.chicagotech.net

The network folder specified is currently mapped using a different user name and password

Symptom: If you use the Map Network Drive Wizard to connect to a network share by using different user credentials and you use the browse functionality to locate the network share, you may receive the following error message: The network folder specified is currently mapped using a different user name and password. To connect using a different user name and password, first disconnect any existing mappings to this network share.

Resolutions: 1. Disconnect the existing mapped drive. 2. Apply latest SP.


Robert Lin, MS-MVP, MCSE & CNE
Windows, Network, Internet, VPN, Routing and How to at

http://www.ms-mvps.com

 

[linney]

812793 - Cannot Map a Network Drive Under Different User Credentials

http://support.microsoft.com/?kbid=812793

 

[jsteph]

Robert, Linney
Thanks much, but I'm not using the Browse to locate the share, and I have no drives at all connected. I have the latest service pack, at least as far as that KB article was concerned.

I'm typing in the network path directly in the 'Folder' section. I think this is a bug that MS doesn't fully understand yet...maybe it'll be fixed in the next service pack. Unfortunately the only way around it now is to weaken security and give rights to yet another user. Fun fun...
Thanks anyway,
--Jim

 

[bcastner]

Try the mapping using the IP form of net use:
e.g. net use h: \\192.168.1.100\Library

It is likely applying Service Pack 2 will provide some relief for you.

 

[nlm9802]

try opening the command line (start, run, cmd) and type net use
does anything show up?

sometimes i see open sessions that can keep drives from being mapped. if you see the server you are trying to connect to, just type net use /delete \\server\share

 

[jsteph]

nlm9802,
As I'd stated in the subject line and first post, Net Use is what I'm using and nothing shows up, I was thinking there might be some undocumented switch where the 'behind-the-scenes' mappings would show up.

This is what seems to be the case--when I go to map the drive--regardless of whether I use the 'Browse...' button or hand-type the path--Windows seems to make a connection to that drive just to verify it's existence, then, without disconnecting that temporary mapping, Windows tries to do the 'real' mapping with the different username, and that generates the error. During testing MS probably only tested mapping a drive, but not the 'log in with a different username' option, so they never saw their blunder in the coding of this wizard.

That's only my guess as to why the error occurs, but I think it's a reasonable one, knowing the general caliber of MS's product team and the type of mistakes they tend to make.
--Jim

 

[ghost807]

actually no it doesn't.

what you should do FIRST
right click on my computer click on disconnect networkdrives.
you will probably see serveral in the list that are mapped but with no drive letters. (hence they are mapped already)
with out drive letters they will not show up in my computer or using net send command line.

retry your command again.

also of value would be the actual command line string you are using.

 

[jsteph]

No--that list shows exactly what Net Use does (at least for my machine).

If there is no Drive Letter, the 'Local' column in the Net Use output is blank, but the mapping still shows and I can delete it by typing the path instead of the letter, the /delete.

After more careful reading--there is indeed a bug where connection is made at the time of mapping but not removed, causing the error. When I first read that KB, it looked as if it were saying the Jan 2003 files were the ones that were needed, so I thought that was the date of new new files--which I already had. But at the bottom, it says this is a bug which was first fixed in XP SP 2, which I do not have yet.

So I'll live with it until the first Service Pack for Service Pack 2 comes out.
--Jim

 

[marc91215]

try using net use delete and get rid of any admin shares

 

[jsteph]

What I meant to say in re: "After more careful reading--there is indeed a bug "... was that that was from the link in linney's post, hence the star.

That kb article confirms the bug (and seems to support my hypothesis about pre-mapping behind the scenes and not disconnecting), but it's an SP2 fix, and I'm not ready to take that plunge, so I'll live with it for a while.
--Jim