Share via

Multiple Users Accessing NAS -- Error Message States "Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed."

Anonymous
2010-02-09T18:29:10+00:00

I have just installed a new NAS device, the NetGear ReadyNAS Duo, firmware v. 4.1.6. There are four "Users" set up on the NAS, and, commonly, two laptops using the home network. One is a Vista 32-bit Dell, the other a Windows 7 64-bit Sony. I have set up several shares on the NAS, all but two of which are "public," i.e. , anyone with access to the network has access to the shares. The other two shares have access limited to two of the NAS "Users." I have been able to map the "public" drives on both computers without incident. I was also able to map/connect to the "private" shares from one of the two laptops, but not from both. I have been able to do this, after a factory reset suggested by NetGear tech support, from either laptop, but each time, I cannot access the "private" files from the other laptop. I receive the error message:

"\[NAS NAME][SHARE NAME] is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permission.

Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again."

I have looked at the following articles: http://home.bott.ca/webserver/?p=346 and http://home.bott.ca/webserver/?p=275 , and have tried (a) making the User name on the NAS the same as those for a user account in Windows; (b) making the User name on the NAS different from those for a user account in Windows; (c) logging in to the "second computer" (i.e. , the computer that cannot access the "private" shares) as the same User as on the "first computer" (i.e. , the one that can access the "private" shares); and (d) logging into the second computer as a different (but also authorized) User as on the first computer, and nothing seems to work.

Several sources, including the "Bott Blog" article, suggest a workaround involving either (a) having one user log in using the host name for the NAS server, and the other using the IP address, or (b) creating a series of aliases for the host server. I can't use (a), both because the folks at NetGear tech support have said that I should use DHCP to set the IP address (so it will change periodically) and because I have more than two users. I'd like to try (b), but all the posts seem to assume that "everyone" knows how to set up this series of aliases, and unfortunately I fall outside of "everyone." I've tried, so far without success, to find on line how one might set up such "alias" names.

By way of example, the Microsoft Support article posted at the end of the Bott Blog article states:

"Create a different Domain Name System (DNS) alias for the remote server, and then use this alias to connect to the network share.

After you use one of these methods, you can use different user credentials to connect to the network share. In this situation, the computer behaves as if it is connecting to a different server."

The problem is that is doesn't tell you how to create such aliases. Any help here would be appreciated. 

DJ

Windows for home | Previous Windows versions | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

  1. Anonymous
    2010-02-11T02:55:39+00:00

    Swati:

    Thanks for the reply.  I had already tried updating the firmware, for both the NAS and the router, to no avail.  It turns out the the issue was likely one of naming/DNS conflict.  When I re-mapped the password-protected network drives using the IP address rather than the NAS name, the problem seems to have been corrected.  Thus, mapping the network drives, either via the net use command or through Windows 7's drive mapping, to \ip address\share name was successful, but mapping to \NAS name\share produced the "multiple connections" error identified above.  One note:  this solution requires reserving an IP address on the router for the NAS drive, so that the mapping remains correct.

    For more detailed discussion, please see the following:  (http://www.readynas.com/forum/viewtopic.php?f=23&t=38659).

    Thanks again.

    DJ

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Anonymous
    2011-03-09T15:11:41+00:00

    Hi DJ - I'm with you on "netspeak"!  They assume you know how to do it!  Thanks to you though I managed to access my NAS (after receiving the same error message as you when trying to connect two PCs simultaneously) by entering the IP address in the "Run" bar.  I checked by opening the same Word file on both PCs - but I need up to 3 PCs to use the NAS simultaneously!  Swati Keni's advice was no good as the NAS isn't in Device Manager so drivers can't be updated. I'm on Win XP SP3.  I am networked through the Router and an ethernet switch.  No fixed IP address for any of it.  I tried using the IP address on the PC that was already connected to the NAS by name but that doesn't work. I've your other link too - still in dark! Cheers, Lionel

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-02-10T18:29:34+00:00

    Hi,

    I suggest that you update the NAS drivers and check. Post us the results.

    Update Drivers:

    1. Open Device Manager by clicking the Start button, clicking Control Panel, clicking System and Maintenance, and then clicking Device Manager. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
    2. In Device Manager, locate the NAS, and then double-click the device name.
    3. Click the Driver tab, and then click Update Driver and follow the instructions.

    Now try to follow the below provided link to Update a driver for hardware that isn't working properly and check for the issue.

    http://windows.microsoft.com/en-us/windows7/Update-a-driver-for-hardware-that-isnt-working-properly

    Thanks and Regards:

    Swati Keni- Microsoft Support Engineer

    Was this answer helpful?

    0 comments No comments