Azure File NFS mount fails with connection reset by peer

Rohit Athikari 116 Reputation points
2020-09-23T16:50:34.39+00:00

I have created NFS azure file share . Followed the steps mentioned in https://learn.microsoft.com/en-us/azure/storage/files/storage-files-how-to-create-nfs-shares?tabs=azure-portal

Have configured Site to Site VPN. Created storage account with VNET and private end points

Now when i try to mount the share on on-prem linux client, i am getting connection reset by peer.

[kompuser@rohit30a-1 ~]$ sudo mount -vvv -t nfs nfsazfiles.file.core.windows.net:/nfsazfiles/nfs1 /mnt/nfsazfiles/nfs1 -o vers=4,minorversion=1,sec=sys
mount.nfs: timeout set for Wed Sep 23 15:53:13 2020
mount.nfs: trying text-based options 'vers=4,minorversion=1,sec=sys,addr=52.239.220.232,clientaddr=10.250.26.166'
mount.nfs: mount(2): Connection reset by peer
mount.nfs: Connection reset by peer

[kompuser@rohit30a-1 ~]$ nslookup nfsazfiles.file.core.windows.net
Server: 10.1.10.44
Address: 10.1.10.44#53

Non-authoritative answer:
nfsazfiles.file.core.windows.net canonical name = nfsazfiles.privatelink.file.core.windows.net.
nfsazfiles.privatelink.file.core.windows.net canonical name = file.blaprdstf02a.store.core.windows.net.
Name: file.blaprdstf02a.store.core.windows.net
Address: 52.239.220.232

[kompuser@rohit30a-1 ~]$ nmap -Pn -p2049 52.239.220.232

Starting Nmap 6.40 ( http://nmap.org ) at 2020-09-23 15:52 UTC
Nmap scan report for 52.239.220.232
Host is up (0.067s latency).
PORT STATE SERVICE
2049/tcp open nfs

Nmap done: 1 IP address (1 host up) scanned in 0.40 seconds

Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
775 questions
{count} votes

Accepted answer
  1. Rohit Athikari 116 Reputation points
    2020-09-24T14:50:57.913+00:00

    I am able to mount and access the share now. I was using the hostname and it was pointing to public IP. Once i used the private endpoint which as the IP from my VNET, its working fine now


0 additional answers

Sort by: Most helpful