I'm googletarded, but I did find this way down a page:

*Are Azure File shares visible publicly over the Internet, or are they only
reachable from Azure?*

As long as port 445 (TCP Outbound) is open and your client supports the SMB
3.0 protocol (*e.g.*, Windows 8 or Windows Server 2012), your file share is
available via the Internet.


Sounds great! However, my net use command gives error 53 from my home Win10
machine with no firewall active, and I get error 5 (access denied) from a
Win2008R2 Azure VM that I just created. Snookered from both directions! The
CloudBerry product is interesting, but I want to avoid foreign software
whenever possible.


*GK*

On 29 February 2016 at 11:05, David Burstin <david.burs...@gmail.com> wrote:

> Hi Greg,
>
> A quick search seems to indicate that
> http://www.cloudberrylab.com/windows-azure-cloud-drive-desktop-software.aspx
> can deal with this, for $30 per machine. I haven't found anything else that
> does, but your Google-fu may be better than mine.
>
> Cheers
> Dave
>
> On 29 February 2016 at 10:53, Greg Keogh <gfke...@gmail.com> wrote:
>
>> Folks, I just read about Azure File Storage and I got all excited at the
>> possibility of creating a familiar mapped drive letter to the cloud. In the
>> portal I created the File share, uploaded some files and issued a net
>> use command which failed with error 53. It turns out I didn't read the
>> fine print in my excitement, which says:
>>
>> *To connect to this file share, run this command from any Windows virtual
>> machine on the same subscription and location*
>>
>> So you can't just mount it from your home PC, only from a suitable VM. I
>> suppose there are security and performance issues, but it's a damn shame as
>> we could really have put this to good use as a kind of "giant file share"
>> for apps written in C++ with no code changes.
>>
>> I just want to be sure that this is all true and there's not some less
>> restrictive way of using Azure File Storage. Is there some other magic way
>> of having a file share in the cloud from anywhere?
>>
>> *Greg K*
>>
>
>

Reply via email to