JMO Posted July 10, 2015 Share Posted July 10, 2015 6.0 beta 12 3 private shares, one for each of three different users. Each user has read/write to their own share and no access to the other users shares. Using a common windows 7 computer, once one user has logged into their share, no other user can log into a different share (on that same machine) unless I first run "net use * /delete". What am I missing? Link to comment
Kir Posted July 10, 2015 Share Posted July 10, 2015 This is how Windows works - it caches the username/password access to the server. Link to comment
JMO Posted July 10, 2015 Author Share Posted July 10, 2015 This is how Windows works - it caches the username/password access to the server. A pure windows network does not suffer from such issues. EDIT: Well, actually, it might. However, prior to unraid I was running WHS and never had this issue with controlling share access. IS there no solution? Link to comment
Kir Posted July 10, 2015 Share Posted July 10, 2015 Do you access different shares on the same server using different credentials in pure Windows network? Link to comment
JMO Posted July 10, 2015 Author Share Posted July 10, 2015 Do you access different shares on the same server using different credentials in pure Windows network? Yes. I am attempting to emulate that very thing in unraid. Link to comment
Kir Posted July 10, 2015 Share Posted July 10, 2015 As I said, this is by design... See this MS knowledge base article on the subject. Ignore the Windows XP warning, the article applies to all versions of Windows (list at the bottom). Link to comment
gundamguy Posted July 10, 2015 Share Posted July 10, 2015 You can try changing windows policy to stop caching of credentials. https://social.technet.microsoft.com/forums/windows/en-US/3161c68f-a6e2-4a8c-ac85-f6bf332ee35b/how-to-disable-credentials-manager Link to comment
JMO Posted July 10, 2015 Author Share Posted July 10, 2015 As I said, this is by design... See this MS knowledge base article on the subject. Ignore the Windows XP warning, the article applies to all versions of Windows (list at the bottom). It's completely shit. I did not have this issue in WHS 2011 (which is not is MS's list). Go figure. Such a pain in the butt. Thank you for the information. You can try changing windows policy to stop caching of credentials. https://social.technet.microsoft.com/forums/windows/en-US/3161c68f-a6e2-4a8c-ac85-f6bf332ee35b/how-to-disable-credentials-manager Again, thanks for the info. I will have to give this some thought. I'm not sure if I am quite ready to disable or uninstall the credentials manager. Link to comment
Kir Posted July 10, 2015 Share Posted July 10, 2015 Why not use one of the workaround methods given in MS article? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.