Azure Site to Site Vpn Problem

Question

Hai, Guys. I Configured site to site VPN connectivity between my on premises network and azure network using Sonicwall firewall. what the problem i am facing is

"From the Virtual Machine(VM1) on azure i can able to ping and access(servers,firewall) from my onPremises network. But on my Premises network i cant able to ping and access Virtual Machine(VM1) present on Azure using Private ip of the Virtual Machine. On the Same case i am able to access virtual Machine present on the azure using Virtual Machine(VM1) public ip". If we configured site to site vpn no need to use Virtual Machine public ip for accessing the virtual machine right ?? , Instead of that we can Virtual Machine private ip right?

Can you help me on this case.

Answer

@Seyed Mohmed Reboy ,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

To address your query, "If we configured site to site vpn no need to use Virtual Machine public ip for accessing the virtual machine right ?? , Instead of that we can Virtual Machine private ip right?"

Yes
This is correct

Since you mentioned you are able to ping and access OnPrem servers, this is not a Routing issue.

Can you please check with your OnPrem Networking team if there are any firewalls blocking the outbound connectivity towards the S2S?
From Azure side, make sure no NSG is blocking inbound access to your VM
You can test this using NSG Diagnostics or IP Flow verify
- And share the results

Cheers,

Kapil

Share via

Azure Site to Site Vpn Problem

1 answer

Your answer