Unable to connect Azure File Sync from On-premises File share

Question

We have configured Azure file Sync ( Storage file Sync ) in Azure. But we are unable to connect from On-premises server. We did the host entry also for Storage account and Storage sync.

we already have the following setup:

• VPN from on-premise into Azure
• Storage account to and Azure file
• Subnet for the Private Link Endpoints
• Storage account to and Azure file share
• On-Premise file share

We have followed the below mentioned blog for configuring the Azure file sync agent.

https://ajcurtis.co.uk/2021/02/15/azure-file-sync-for-a-hybrid-environment/

Answer 1

Hello Mahavir Saroj,

Greetings! Welcome to Microsoft Q&A Platform.

I understand that you are encountering issue with connecting to Azure File Sync from an on-premises file share.

If you have a specific error, you might get some resolution on our troubleshooting page: https://learn.microsoft.com/en-us/troubleshoot/azure/azure-storage/files/file-sync/file-sync-troubleshoot,https://learn.microsoft.com/en-us/troubleshoot/azure/azure-storage/files/connectivity/files-troubleshoot-smb-connectivity?tabs=windows Can you please un-install and re-install the Azure File Sync agent. Download the newest Azure File Sync agent installer from the Microsoft Download Center. To upgrade an existing Azure File Sync agent installation, uninstall the older version and then install the latest version from the downloaded installer. The server registration, sync groups, and any other settings are maintained by the Azure File Sync installer.

https://www.catalog.update.microsoft.com/Search.aspx?q=5023058 Azure File Sync Agent v18.1

I also recommend running the AzFileDiagnostics script for Windows to look for common issues.

Please consider checking the following steps to troubleshoot the issue:

• If you have virtual network (VNET) or firewall rules configured on the storage account, network traffic may be denied.Ensure that VNET and firewall rules are properly configured and temporarily change the storage account setting to allow access from all networks to test if rules are causing the issue.
• Port 445 Connectivity: Verify that port 445 is accessible from your development machine to the Azure storage account. You can use the PowerShell command Test-NetConnection -Port 445 -ComputerName somestoragexxx.file.core.windows.net to check connectivity.If TCP 445 connectivity fails, check your ISP or on-premises network security for outbound port 445 blocking.
• Check the sync interval: Make sure that the sync interval is set correctly. The sync interval determines how often the sync agent checks for changes in the Azure File Share. If the sync interval is too long, it may take longer for the changes to be detected. You can check the sync interval by using the Set-StorageSyncServiceConfiguration cmdlet.
• Check the file size: Make sure that the file size is not too large. If the file size is too large, it may take longer for the changes to be detected. You can check the maximum file size supported by the sync agent by using the Get-StorageSyncServiceConfiguration cmdlet.
• Check the network connectivity: Slow network connectivity can also affect the sync agent's ability to detect changes. Make sure that the network connectivity between the Azure File Share and the local file server is stable and fast.
• Check the sync agent logs: Check the sync agent logs for any error messages related to the file that is not updating correctly. The error messages may provide clues as to what is causing the issue.
• Try restarting the sync agent: Sometimes, restarting the sync agent can help resolve issues with file syncing. You can restart the sync agent by using the Restart-StorageSyncService cmdlet.

refer FAQ for more insights - https://learn.microsoft.com/en-us/azure/storage/files/storage-files-faq#general

Hope this answer helps! Please let us know if you have any further queries. I’m happy to assist you further.

---

Please "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.