Your issue is a Windows one, not a ReadyNAS one, but you are refusing to accept that. In addition, I believe much of it is of your own making, but I can't tell for sure just what it is because you keep resisting our efforts to determine that. If I'm diagnosing right, it's not really even a "Windows Problem" per se, it's just a lack of knowing how Windows works (and sometimes doesn't work as you'd like/expect it to). Nonetheless, we are trying to help you. If you search the Synology forum, you will find similar issues reported.

Once we use the command prompt to figure out what causes the problem, we can likely tell you how to fix it such that you don't continue to have to use it. But the GUI does not give the tools necessary to do the diagnosis.

This is my diagnosis so far: You have mapped multiple drives on the ReadyNAS using either one or two sets of credentials, which are not the Windows user's credentials or NAS admin credentials, and you are trying to access the NAS with those credentials. That makes it two sets of credentials for the same device, whihc simply is not allowed by Windows -- it has nothing at all to do with the ReadyNAS. You have not done the same on the Synology, so you don't yet have the problem there.

And this is the basis of my diagnosis: Your error message is that the device name is already in use (how you have interpreted that to mean it may be misspelled, I have no idea). Your NET USE command shows that both the NAS name and IP are, in fact, in use in drive mappings. I assume that's from network mappings you've made using the options to map using a different account and the checkbox to remember it (thus, it's of your own making). I do not know if you are using the same credentials for those mappings, but it's pretty clear that it's not the Windows user's credentials (which are presented automatically when you type the share name into the Windows Explorer address window) or NAS admin account (which you used in a NET USE mapping) since your attempts to use those credentials now fail. Whether the credentials for the mappings by IP and by name are the same or different from each other, I do not know, but we have a way to find out. The message Windows gives when you try to use a second set of credentials to access a device that's already connected (aka In use) is exactly the one you are getting.

I would still like to see what happens when you clear out all the existing connections. I believe it will make your new connection work and will be the next pointer to the root cause. This is what you can do next to better diagnose the problem. If you've already run the command to delete the existing connections, re-boot to re-establish them. Then, enter this command in the windows CMD prompt for each mapped drive: wmic netuse where LocalName="M:" get UserName /value. Run it for M, then replace M with each of the drives in the NET USE list and post the results here. If you are concerned about the user name given being posted publicly, you can replace it with something generic. But use the same generic name for each instance of the real one. E.G., replace every instance of "Tom" with "Jerry".

While you are not a technology company, expecting technology to "run itself" is a naïve position. When your whole IT infrastructure comes tumbling down and you can't fix it because you have no idea how it works and you cannot conduct business as usual, you will wish you'd learned more about it. If you choose not to learn yourself, there are consultants who can help. Unfortunately, many are not willing to work with what you have, so you may have to replace some of the hardware (the ReadyNAS likely being one, since it's no longer supported by Netgear). Trust me that it's far cheaper than calling in a "strike team" to fix a major problem while your employees' productivity is reduced but they are still getting paid.

Forum Discussion

Accessing remotely RBK 50