Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have a NAS device, it has 3 shares. On one computer I have access to all 3 of the shares. On another computer I keep getting this error when try and add a 2nd one.

The Network folder specified is currently mapped using a different user name and password [...]

That is the message I keep getting. What causes that?

EDIT: Every share has it's own username and password.

EDIT: NET USE on the one running 3 from the same NAS device

New connections will be remembered.


Status       Local     Remote                    Network

-------------------------------------------------------------------------------
OK           T:        \\192.168.2.5\SHARE1      Microsoft Windows Network
OK           X:        \\Nas-1dsho-abc\SHARE2    Microsoft Windows Network
Disconnected Y:        \\192.168.2.9\backups     Microsoft Windows Network
OK           Z:        \\Nas-1dsho-abc\cbackups  Microsoft Windows Network
The command completed successfully.

NET USE on the other:

New connections will be remembered.


Status       Local     Remote                    Network

-------------------------------------------------------------------------------
OK           Y:        \\192.168.2.5\SHARE1  Microsoft Windows Network
Unavailable  Z:        \\192.168.2.5\SHARE2    Microsoft Windows Network
The command completed successfully.

EDIT:

I have been using the 'connect using different credentials' option.

share|improve this question
1  
Perhaps the network folder specified is currently mapped using a different user name and password :-). What does NET USE show? –  Chris McKeown Oct 29 '13 at 0:38
    
What share is the one that is giving the error? Does this error come up after a reboot? –  SpiderIce Feb 28 at 23:01

2 Answers 2

NET USE does not allow you to connect to the same server with different credentials. This is because it reuses the same relationship to map additional shares on the same server. You can work around this by making windows think it's a different server either by creating DNS aliases for the same NAS with different names or editing the hosts file on the clients.

A better solution would be to change your account structure. Don't create an account on the NAS for each share. Create an account on the NAS for each client and give those accounts permissions to the shares.

share|improve this answer
    
Thank you thank you thank you! –  Karl Morrison Jun 27 at 14:29
    
Agreed this has been pissing me off! Thanks! –  slashp Oct 10 at 13:16

It doesn't have to be the same network folder that's mapped. It could be a different folder on the same server, a subfolder of the folder already mapped (which qualifies as my first guess). Not sure how you pulled it off on the first machine, but the best course of action is to check the box that say 'connect using different credentials'. There is an answer already here, no screenshots though as they are command line answers, but effective nonetheless.

share|improve this answer
    
Yea, I have been using the connect using different credentials option ;/ –  Frank Thornton Oct 29 '13 at 22:37
    
You can check what accounts Windows is using to connect to remote shares by doing Start>Run>**control userpasswords2**. Switch to the Advanced tab then click Manage Passwords, then select Windows Credentials and look for the resource you're trying to connect to. Windows won't let you connect to the same server with different credentials. I'd double check on how you're connected to Nas-1dsho-abc from the first computer, I'd wager it's the same credentials for both connections. –  RobbieCrash Feb 13 at 21:04

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.