Arbadacarba

Just found those instructions myself and jumped over here hoping to find that the @ symbol have been fixed or was about to be fixed... Guess not. Any hint on where I would look to find the reason the @ symbol is verboten?

Could it be that the current version of windows refuses to connect to anoymous shares? I had to enable insecure guest access in Group Policy settings: Computer configuration\administrative templates\network\Lanman Workstation "Enable insecure guest logons" https://support.microsoft.com/en-ca/help/4046019/guest-access-in-smb2-disabled-by-default-in-windows-10-and-windows-ser I did this and was happy with the result.

Just a quick note that there is anther solution to this problem without enabling SMB1. Microsoft has replaced SMB with "Function Discovery" (in a manner of speaking) and there is a daemon / script that enables that for Linux. I have "Instructions" in the thread here: forums.unraid.net/topic/82765-solved-windows-network-working-with-no-smb1/ Kevin

I'm a new user who is still on his 30 day trial... So far the flexibility of Unraid has been perfect for my needs as both a home media server, and as a learning tool for Linux and even ESXi