Azure Virtual Server cannot Ping Servers Located On-Prem
Hi Everyone!
We have an Azure Virtual Server that is connected to our on-prem LAN via Site to Site VPN.
When I am RDP on the Azure Vitrual Server and try to ping servers located on-prem, I am unable to do so.
Any ideas what I may have missed or what I need to perform to get this work?
Any assistance would be greatly appreciated.
We have an Azure Virtual Server that is connected to our on-prem LAN via Site to Site VPN.
When I am RDP on the Azure Vitrual Server and try to ping servers located on-prem, I am unable to do so.
Any ideas what I may have missed or what I need to perform to get this work?
Any assistance would be greatly appreciated.
ASKER
Thank you for this info asavener, but I am still not able to ping the resource.
Some more info... I have three resources defined in my ASA for this Azure Cloud. Two of the resources are located here in Boston, MA and I successful in pinging them. The third resource is a NFS share located in Europe and that is the resource I am unable to ping. When I perform a tracert it seems to leave Azure, but then is has a problem going out and coming back from the resource in Europe.
What are your thoughts?
Some more info... I have three resources defined in my ASA for this Azure Cloud. Two of the resources are located here in Boston, MA and I successful in pinging them. The third resource is a NFS share located in Europe and that is the resource I am unable to ping. When I perform a tracert it seems to leave Azure, but then is has a problem going out and coming back from the resource in Europe.
What are your thoughts?
So the server in Azure cannot ping the NFS server? How is the traffic directed to the NFS server? Is it going back out over a VPN, or is it internally routed, or what?
ASKER
That is correct, the server in Azure is unable to ping the NFS Server in Europe. Internally and via our VPN (when connected via our Cisco VPN client), we are successfully able to ping and tracert to this NFS share.
My apologies to ask, but how I can tell how the traffic is directed to the NFS server, and if it is going back over a VPN? Is there a tool that will tell me this?
My apologies to ask, but how I can tell how the traffic is directed to the NFS server, and if it is going back over a VPN? Is there a tool that will tell me this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I performed a tracert and here is what I am seeing:
On the NFS share IP Address, It performs one hop to 10.10.11.100 and then after 29 hops, it goes to Request timed out.
If I perform a tracert on a resource I am successfully able to ping, it performs on hope to 10.10.11.100 and then after 15 hops showing Request timed out, I get the successful destination.
What are your thoughts?
On the NFS share IP Address, It performs one hop to 10.10.11.100 and then after 29 hops, it goes to Request timed out.
If I perform a tracert on a resource I am successfully able to ping, it performs on hope to 10.10.11.100 and then after 15 hops showing Request timed out, I get the successful destination.
What are your thoughts?
How is the NFS share connected to the rest of your network?
ASKER
This was a routing issue as the resource that we were unable to access was in the Europe. The router in Europe needed to be updated with the route on how to get to the server in Azure.
Open an elevated command prompt, and issue the following commands:
netsh advfirewall firewall add rule name="ICMPv6" dir=in action=allow enable=yes protocol=icmpv6
netsh advfirewall firewall add rule name="ICMPV4" dir=in action=allow enable=yes protocol=icmpv4