03-21-2023 08:39 AM
I've been experimenting with the new Windows 365 cloud PCs and recently established a routed based S2S via my firewall (ASA 5515) and Microsoft azure. I can access everything (network shares, AD, DNS,etc.) except for my firewall. I can ping my firewall from the 365 machines, but I can't get in via ASDM nor if I were to startup AnyConnect it won't even resolve my server address. I've tried disabling the machines local firewalls and creating a firewall rule to allow any/any access from the IP range that the 365 machines use. still no luck. I think it's on the firewall side that the problem lies but I am not sure.
Has anyone experienced these types of issues or have any suggestions on where to look?
Solved! Go to Solution.
03-22-2023 09:27 AM
After some more troubleshooting, I realized the mistake was on my end, as I had not yet configured/allowed ASDM access through VPN on that particular IP range.
Thanks
03-21-2023 09:15 AM
>......but I can't get in via ASDM nor if I were to startup AnyConnect
Hmm. note that the particular products (ASDM and Anyconnect) usually have a supported platform list in datasheets and or product specifications, so if the new Windows product is not (yet) in there , then 'it won't work' (so to speak) ,
M.
03-22-2023 09:27 AM
After some more troubleshooting, I realized the mistake was on my end, as I had not yet configured/allowed ASDM access through VPN on that particular IP range.
Thanks
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