05-28-2025 05:40 PM
We have a ASAv in Azure that is only used for AnyConnect. We have a Site-to-Site between Azure and a Watchguard FW at our Colo. The tunnel is up but I can't get to anything in the Colo while connected to the Secure Client. I can get from Azure to the Colo if I login to a VM in either place first. Everything was working fine but all of a sudden it stopped this afternoon and I can't figure out what has happened.
There is still a peering between the VNET of the ASAv and the Network Gateway that is set to use the remote gateway.
Any help would be great. I don't know what else to check.
Solved! Go to Solution.
05-28-2025 07:55 PM
I figured out that the ASAv internal IP was blocked on the Watchguard FW. Not exactly sure how that just happened today since nothing had changed.
05-28-2025 07:55 PM
I figured out that the ASAv internal IP was blocked on the Watchguard FW. Not exactly sure how that just happened today since nothing had changed.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide