This is the second Bump post for the section labeled "EDIT:  December 4, 2024"  to the first post of this thread. 

After many attempts i have found this solution.

 

Run Powershell as administrator and type this:

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true -Force

this will allow insecure guest logins which were deactivated with the past windows updates

 

https://learn.microsoft.com/de-de/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell

1 hour ago, SLoeffler said:

After many attempts i have found this solution.

 

Run Powershell as administrator and type this:

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true -Force

this will allow insecure guest logins which were deactivated with the past windows updates

 

https://learn.microsoft.com/de-de/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell

However, this is a security risk.  It allows unsecured and unverified connections to malicious servers.  This is a particular hazard for laptops connecting to public WIFI hotspots.  

 

I normally ignore these posts about doing this type of thing but since this is my thread and it about setting up a secure network that works with Unraid, I am calling you out on it.  Doing this type of thing should not ever be considered to be a recommended practice!

Thank you for all your work on this.  I finally decided to replace my old W10 system with a W11 system as W10 is not going to be an option as of later this year.  I was able to get my unRAID shares available thanks to you.  I'd love to see an update using W11 terms and screenshots someday, as some of the locations, and verbiage are different in W11.

 

I still also have a problem where \\TOWER is seen on the Network, but it won't connect. I was able to get the share I wanted accessible by using the IP address of TOWER, however.  So far, so good there.

 

Kevin

1 hour ago, kolepard said:

I still also have a problem where \\TOWER is seen on the Network, but it won't connect.

This is a problem which I  have had in the past.  But mine was that the \\{server_name} was accessible but \\{server_IP_address} was not.  But recently, both ways appear to work on my current LAN setup.  I can't explain why except I think the router got a firmware update.

 

1 hour ago, kolepard said:

I was able to get the share I wanted accessible by using the IP address of TOWER, however.  So far, so good there.

I would say pick the one that works and use the “An Alternative Method to Network Neighborhood.PDF” to set up a Quick Access shortcut in Windows File Manager/Explorer.  (You can rename the Desktop shortcut to show the Unraid Server name rather than the IP address.)   My experience has been that if it is not showing up in   Network  in the file manager, it will after clicking on that quick access shortcut.  Just in case, you think this is just an Unraid-Windows issue, I can tell that I have more problems with my Windows Clients computers setup in a peer-to-peer networking configuration not showing under  Network  heading in the file manager than I do with my Unraid servers!

Thank you for the reply and suggestions.  After following the steps earlier in the guide, (I suspect most significantly making sure unRAID had a user/password combination that matched the one on the W11 box and changing it to a Private network) I was successfully able to use the drive mapping feature to assign drives to the shares I wanted.

 

Your guide was invaluable, so thank you.

 

Kevin