Hello everyone. Running Unraid 7.0.0-rc1. Aside from a couple of small issues, it's running rather well. Today's issue is this:

 

I set up a share (can either be a share hosted on the Unraid array (which in my case is only used for containers and their respective data) or through an SMB share - mapped SMB shares from my NAS). Once I set up the user, then it's as simple as mapping the drive in Windows / macOS with the required authentication and I hit the ground running.

 

There's only one problem. Those mapped drives only work for an unspecified amount of time, and the only way to regain access to these SMB shares is to disconnect the share and reconnect. Sometimes I need to reboot to remap the drive. I've had to reboot both Unraid as well as my Windows system to resolve this. I can't find a common denominator to this madness. This leads me to think this is some kind of authentication issue, but I don't know how to figure this out. It's super annoying and basically pointless to map a drive, as I can't get them to 'stick'. 

 

Things of note:

1. I don't know what logs here may be beneficial, so please let me know.

2. I'm utilizing compatible 10G SFP+ ports between Unraid and my system with the drive mappings. Not sure if there's something in the configuration that may be causing the issue, but I also experience this in Wi-Fi connected devices, so I think I can rule that out.

3. The normal error I get once this happens is (Error 1 photo attached) Microsoft Windows Network: The local device name is already in use."

4. The other error I sometimes get is (Error 2 photo attached) Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed."

5. Sometimes, I have to reboot either the client OS or Unraid in its entirety to resolve.

6. This happens with both drive mappings between the Unraid array as well as a SMB share within Unraid.

7. This does not happen if I map a SMB share directly to my NAS. It's strictly related to Unraid.

 

The way I have shares structured is with only 2 accounts. I've created 1 user called "unraid" so I can map the NAS shares to Docker containers. I do not have any problems with drive mappings within Docker. The other is called "joe" and this is the one I have consistent issues with. I've also created another user to see if the problem occurs, and it does.

 

What am I doing wrong? Any help is greatly appreciated!

https://docs.unraid.net/unraid-os/release-notes/7.0.0/#new-windows-changes-may-result-in-loss-of-access-to-public-shares

I'll give this a shot and report back, thank you for your reply!

This seems to have fixed the issue, although a silly workaround. Now I have an additional profile on all of my Windows devices just to access shares on Unraid. 

2 hours ago, jo3see said:

This seems to have fixed the issue, although a silly workaround. Now I have an additional profile on all of my Windows devices just to access shares on Unraid. 

 

This the result of a security update to Windows SMB from Microsoft.  It is how Microsoft wants Windows to be configured.  They do not want to allow Windows client computers to be able to willy-nilly log onto rogue servers on public WIFI access points.   It is not a workaround!