8

Created Azure file share in portal and copied the PowerShell script to connect it as drive Q: (verified not in use). Response:

New-PSDrive : The network resource type is not correct
At line:3 char:1
+ New-PSDrive -Name Q -PSProvider FileSystem -Root "\\xxxx.file.c ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (Q:PSDriveInfo) [New-PSDrive],  Win32Exception
+ FullyQualifiedErrorId :      CouldNotMapNetworkDrive,Microsoft.PowerShell.Commands.NewPSDriveCommand

where "xxxx" is the share name. The PS command was copied directly from the portal and not altered.

Barry Briggs
  • 209
  • 2
  • 14

2 Answers2

2

As noted in comments above, Comcast blocks port 445. Solution was to have another object in the cloud reference the Azure File and then return the data to the client over HTTP.

Barry Briggs
  • 209
  • 2
  • 14
0

Several workaround for port 445 (SMB port) being blocked are listed here: https://learn.microsoft.com/en-us/azure/storage/files/storage-troubleshoot-windows-file-connection-problems#error-53-error-67-or-error-87-when-you-mount-or-unmount-an-azure-file-share

  • I would be helpful if the answer had more guidance. Something like you could follow "Solution 4 - Use REST API based tools like Storage Explorer/Powershell" and use the following powershell.code.example. – Jason Pyeron Mar 02 '20 at 23:11