net use - "net use" for Azure File Services fails depending on OS type -


anyone know why below "net use" command gets varied results depending on machine os though logged on admin in cases? fails or works based on os within powershell or cmd whether shell run administrator or not. share setup in azure file services , can accessed on win10 machine fine using azure powershell cmdlets.

# mount azure share drive net use x: \\[myaccount].file.core.windows.net\davesdata /user:[myaccount] [my secondary key] 
  • runs fine on server 2012
  • gets “access denied” on server 2008
  • gets “path not found” on windows 10

azure file storage supports following windows / smb variants: windows 7 smb 2.1, windows server 2008 r2 smb 2.1, windows 8 smb 3.0, windows server 2012 smb 3.0, windows server 2012 r2 smb 3.0 , windows 10 smb 3.0.

if connecting vm within same azure region can connect using smb 2.1 or smb 3.0. if connecting outside of azure region need ensure port 445 outbound open. many isp's / corporate filewalls block this. wiki contains list of isp's allow / disallow port 445.


Comments

Popular posts from this blog

ruby - Trying to change last to "x"s to 23 -

jquery - Clone last and append item to closest class -

c - Unrecognised emulation mode: elf_i386 on MinGW32 -