title: Powershell, NAS access & Permissions? issues
body: <p>I have recently run into the &quot;Guest access in SMB2 &amp; SMB3&quot; issue outlined by Microsoft <a href="https://docs.microsoft.com/en-US/troubleshoot/windows-server/networking/guest-access-in-smb2-is-disabled-by-default" rel="nofollow noreferrer">here</a>, and I am trying to understand the full scope of the issue.
  So far as I can tell, this only impacts NAS access or the like, because a share on a domain member computer is not accessed as a guest. However, I have an account on my NAS, with matching name and password, and permissions are handled properly. Meaning, on a Windows build that doesn't have the outlined problem, I CAN access folders that user has permissions for, and I can't access folders that user doesn't have permission for. Which seems like I am NOT accessing the NAS as a guest, but rather with user credentials. So, can someone explain what is actually happening under the hood?</p>
  <p>Also, I was alerted to the issue because a customer was seeing this behavior, and the &quot;fix&quot; outlined by Microsoft is not working for them. Their scenario is slightly different in that they are using Azure in a way that I am not familiar with, basically syncing Group Policy, or at least permissions, with Azure. But Microsoft's information linked above makes no mention of Azure at all, so not sure what the Azure based version of Group Policy is capable of.</p>
  <p>And finally, on my Windows 10 Enterprise VM, accessing a Synology NAS, I lose not only PowerShell access to the NAS, but Explorer as well. I get the error mentioned in the link.</p>
  <blockquote>
  <p>You can't access this shared folder because your organization's
  security policies block unauthenticated guest access. These policies
  help protect your PC from unsafe or malicious devices on the network.</p>
  </blockquote>
  <p>But for this customer, the issue is not showing up in Explorer, only (so far as we have seen) in PowerShell. And in PowerShell it manifests as Test-Path failing on a valid path, that we can access in Explorer. Does that suggest some other problem, and my Google-Fu has led me astray?</p>