Up until yesterday my network shares were all visible and usable. Today I see that both network shares have red X's in Windows and I can no longer access them. I also can not access Tower (Unraid Server Name) in Windows Network.

 

Windows is giving me this error.

 

An error occurred while reconnecting Z: to \\192.168.1.221\Media
Microsoft Windows Network: The local device name is already in use.
This connection has not been restored.

 

Any help?

Also get this from Windows Network Diagnostics
Problems Found (The remote device or resource won't accept the connection)

I was able to add them back in via IP address but the host name no longer works.

 

9 hours ago, Lucky3058 said:

I was able to add them back in via IP address but the host name no longer works.

 

My recent experience mirrors yours.  You can use either IP addresses or the 'host' name but not both.  Not sure what is going on unless it is related to MS's requirement that only one client connection is permitted to each server.

 

One thing to check are these two settings: 

 

Note that Windows (now) by default will not longer use SMBv1 protocol.  (SMBv1 is a security risk-- Primarily for home users. This is one of the few instances where the corporate world is at a lower risk than the typical Unraid user.)

Looks like those are set to on for both. I didn't change anything over the weekend so don't know why this got dropped yesterday. Attached is a screenshot of SMB configuration and logs are also attached.

unraid1-syslog-20240611-1215.zip unraid1-diagnostics-20240611-0810.zip

Edited June 11, 20242 yr by Lucky3058
Attached logs

So found this previous forum entry....

Followed everything in top post and the PDF for it, until page 9. There I noticed is when everything is back to normal now for my SMB shares. YMMV.

Shout out to @Frank1940 that post was a freaking lifesaver today!!