SMB over VPN gateway not possible

[Julian12]

Hi,

I have a problem with connecting SMB network shares from an on-premise Server to a VM located in azure over a Site-to-Site VPN and VPN gateway.

We tried everything but it seems that these and other protokolls are natively blockeed from the Azure vpn gateway, is this correct?

Are there any solutions to this problem or did I miss something in the configuration or connection/authentication?

Thanks and regards

[#2]

Hmm, it should work (SMB is one of the ports, that AD needs for SYSVOL replication - if you have a domain controller in Azure, is it replicating properly with your on-premises machines?), as long as the site to site connection is up and running and the firewall allows it.

https://docs.microsoft.com/en-us/azure/storage/files/storage-files-configure-s2s-vpn

I would check the route back to on-premises from Azure, check the Windows Firewall configuration and your third party firewall configuration actually allows SMB through.

Can you connect to a fileserver using its IP address?

On a side note, have you looked at Azure File Sync ( https://docs.microsoft.com/en-us/azure/storage/file-sync/file-sync-deployment-guide?tabs=azure-porta... ), maybe a more suitable option?

[#3]

I tested this with the Microsoft Support and currently the situation is that all traffic is going through the vpn gateway but not something with port 445 or 135, so SMB and DNS and this traffic is not even reaching the vpn gateway tunnel.
It is working when coming from on-prem to Azure but only not from the other side even when setting the VM right next to the gateway with nothing in between.
SMB is eve nworking from one VM to anthoer VM in a peered network.
MS support hat also no clue whats going on there so we deployed a new vpn gateway in the remote network and there SMB is working but this is only temporary and the problem is still not solved atm.

[#4]

Did you ever get a solution we have exactly the same issue

[#5]

@m77ewlHi, yeah, the problem was the switch in the vpn routing table configuration for Distributing gateway routes, this was set to no but after enabling it to yes, it was working^^

Even when you have special routing in place, this switch must be enabled in the vpn routing table.

Hope this helps.