NotMrSavvy

Thank you for your help Frank1940. For this particular array, I'm indeed in a business environment, and while the array is reasonably secure, my main concern is with keeping it that way, especially if one of our systems that connects to the array were to ever unknowingly be compromised in some way.

Hi, I'm a new UnRAID user running a mixed macOS/Windows environment, and I was running into this exact issue on my Windows 10 machines. This is sort of my first question about UnRAID, (and almost definitely not the last,) but from what I can tell, it looks like I'm trading one security vulnerability for another with this solution. This is good, as it's exactly what I wanted to avoid from Spaceinvader One's awesome videos as a result of security concerns. Naturally, I was thrilled when I first saw this thread, until I saw this wording in step three: If I'm enabling insecure guest logons, doesn't that mean I'm potentially opening my network up to additional security vulnerabilities? If so, what are the advantages of using this method over enabling SMB1? Are their any advantages of enabling SMB1 over using this method to make my UnRAID server visible to Windows 10? Any assistance is greatly appreciated.