Windows 10: Cannot access a secured share on a NAS

From my main comp, back to square one. Same error. Absolutely ridiculous that we can't seemingly use a private share.

 

I found a little more information on this (from the web, so I'm sure it's accurate *Smile).

The Windows limitation seems to be one connection between a Windows user and NAS server - not just one set of network credentials. If you establish a connection to a public share (i.e., not credentials needed) you cannot establish a connection to a private share on that same server. And vice versa - if you establish a connection to a private share you cannot also establish a connection to a public share. Whichever you establish first is all you get.

I'm not sure about connections to multiple public shares. Windows may consider that one connection since this limitation seems to be based on network credentials.

I read posts saying that it would work if you use the IP address instead of name for a second connection. That would not work for me. Windows still new I was trying to get to the same server.

I read another post saying that it would work if added additional network names to the Windows etc\hosts file . That also would not work for me. Windows still new I was trying to get to the same server.

Perhaps it would work if alias DNS names could be added to the little DNS server in my router, but I don't know how to do that.

I'm almost sure I'm trying to go down the wrong path. I can't believe that Windows developers think it is reasonable to disallow a user to have connections to multiple shares on a NAS server.

 

Success. Sort of. Maybe. I'm not sure how to apply this, and whether or not this will help anybody else, but I've gotten a bit farther (and uncovered some real stupidity on my part).

In my testing I was accessing the various shares incorrectly.




Under Network I was clicking on MYBOOKLIVE, clicking on name of one of the secured shares - "Secure" in this case - And then trying to enter the credentials. In order to try using the IP address for access I was trying 192.168.1.234\userid. Dumb!

Instead, I should have been putting \\192.168.1.234 in the panel's pat field. Then I would get:



Now I am using the IP addr to access the NAS server and Windows will accept the appropriate credentials.

However, Windows then have a connection using that IP addr for that share. I cannot access another secured share that requires different credentials. (I probably can access a different secured share that required the same credentials. I'll have to try that.) There is probably some way to tell Windows to clear the connection so I can establish a different one, but I haven't found it. Logging off of Windows clears the connection but is not very convenient.

In my case I want my backup software to access the secured share. I'd really like to find a way for this to work without telling it to use the IP address rather than the name. If it uses a hard-coded IP addr, I'd better give the NAS a static addr. I really don't like doing that.

 

I feel your pain. No idea why we have to have this problem. We both know how it should work!

I tried to see just what was returning that error by using a notebook that had been switched off for weeks. Still got the error so I thought it must have been triggered by the NAS. Then I reset the NAS and it was OK for the first access then the error returned. Does this also mean the NAS is more involved than thought?

I seem to have cracked the backup to the secure folder, though. I have created a separate user and given that user full rights to 'secure'. Then, while logged on with that user, I created the backup and scheduled it weekly. This schedule can be seen in Task Scheduler.

Even when logged into my standard user, that backup schedule runs and backs up to the secure folder with no problem. I am resigned to logging into the backup user to access the secure folder when I want to check it.

Hope this helps as a viable work around.