I'm somewhat to linux, I've managed people who work on linux but rarely used it myself. I cannot connect to shares marked private in unRAID.  When the shares/disks are public I have no problem connecting from a Win10 machine, when I change them to private the connection is refused. I've created a user/password, given it read/write access to each share and each disk.  I can see the Tower computer on the network, I can see the shared folders, when I double click on one I'm asked for the login info. I type "bottom" (user name) and the password but the connection is refused. I've also tried "\\tower\bottom" as the username also refused. After getting refused a few times I get a message "\\TOWER\Photos is not accessible. You might no have permission to use this network resource. Contact the adminstrator of this server to findout if you have access permissions. 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 ot the server or shared resource and try again."

So does that message mean that I cannot access both a public folder (without typing a user/password) and a private one at the same time?

help.... thanks

Everend

 

 

 

So does that message mean that I cannot access both a public folder (without typing a user/password) and a private one at the same time?

help.... thanks

Everend

You've got it, exactly. However, the credentials that allow you access to a private folder will also let you use the public one. You just need to make sure to clear any saved credentials, reboot, and log into the private folder first, then you will be able to access the public one. Another option is to refer to the tower by its IP address, windows is stupid and thinks it's talking to a different machine, and will allow a second set of credentials.

Oh that's funny.

 

I've been fighting this for a couple of days. I started off with all shares as public then while transferring to one I tried to make the others private. Since I've got 7TB of data to transfer I've had something copying almost non-stop since I created the unRaid server.  It wasn't until copying the error message to this post that it occured to me that could be part of it. But since I still had 6 hours left on tera-copy I haven't had a chance to clear credentials.

 

Thanks!

So after the last files finished transferring to the public share, I restarted the Win10 machine. Opened Windows Explorer, pointed to one of the private shares and it opened, without prompting for a password at all.  I connected to the web interface to confirm the share is set to private. The web prompted for the root login and confirmed the share I just accessed and started writing to is marked private, no guest access.  So did Win10 or unRAID remember all my failed login attempts before restarting Win10 and authenticated me without prompting for user/password?

So after the last files finished transferring to the public share, I restarted the Win10 machine. Opened Windows Explorer, pointed to one of the private shares and it opened, without prompting for a password at all.  I connected to the web interface to confirm the share is set to private. The web prompted for the root login and confirmed the share I just accessed and started writing to is marked private, no guest access.  So did Win10 or unRAID remember all my failed login attempts before restarting Win10 and authenticated me without prompting for user/password?

Is the user name and password for your local windows user account the same as the user/password you set on unRAID?

No, windows user is completely different.  The key here was knowing that only one unraid account will work at a time.

 

thanks

No, windows user is completely different.  The key here was knowing that only one unraid account will work at a time.

 

thanks

Actually, the key is knowing that Windows will only allow one login per network machine. If you refer to the machine by name, then you can fool Windows into letting you login again by referring to it by IP

trurl, thanks for wording it correctly