microsoft / AzureStorageExplorer

Easily manage the contents of your storage account with Azure Storage Explorer. Upload, download, and manage blobs, files, queues, tables, and Cosmos DB entities. Gain easy access to manage your virtual machine disks. Work with either Azure Resource Manager or classic storage accounts, plus manage and configure cross-origin resource sharing (CORS) rules.
Creative Commons Attribution 4.0 International
377 stars 87 forks source link

Unable to browse Azure File Shares in ADLS Gen2 account #8293

Closed engrmaqs closed 1 week ago

engrmaqs commented 1 week ago

Preflight Checklist

Storage Explorer Version

1.36.2

Regression From

No response

Architecture

x64

Storage Explorer Build Number

20241029.2

Platform

Windows

OS Version

Windows Datacentre 2022 Datacenter Azure Edition

Bug Description

I am unable to browse Azure File Shares on ADLS Gen2 Storage account. Unable to retrieve child resources

ProducerError:{ "name": "Node Fetch Error", "message": "getaddrinfo ENOTFOUND storageeversholtprod.file.core.windows.net", "stack": "Error: getaddrinfo ENOTFOUND storageeversholtprod.file.core.windows.net\n at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)", "cause": {}, "code": "ENOTFOUND", "errno": -3008 }

Steps to Reproduce

  1. Launch Storage Explorer
  2. Click on File Shares and I get the error
  3. Unable to retrieve child resources

ProducerError:{ "name": "Node Fetch Error", "message": "getaddrinfo ENOTFOUND storageeversholtprod.file.core.windows.net", "stack": "Error: getaddrinfo ENOTFOUND storageeversholtprod.file.core.windows.net\n at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)", "cause": {}, "code": "ENOTFOUND", "errno": -3008 }

Actual Experience

  1. Launch Storage Explorer
  2. Click on File Shares and I get the error
  3. Unable to retrieve child resources

ProducerError:{ "name": "Node Fetch Error", "message": "getaddrinfo ENOTFOUND storageeversholtprod.file.core.windows.net", "stack": "Error: getaddrinfo ENOTFOUND storageeversholtprod.file.core.windows.net\n at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)", "cause": {}, "code": "ENOTFOUND", "errno": -3008 }

Expected Experience

No response

Additional Context

No response

craxal commented 1 week ago

@engrmaqs

engrmaqs commented 1 week ago

Thanks for contacting. Our Networks team has managed to resolve the issue. it was related to a DNS entry missing from the Private DNS Zones within Azure Adding Storage Account DNS Entry to the Private Link resolved the issue.