New to Devnet Sandbox, Anyconnect fails to connect

[btchamberlin]

Hello, Im new to accessing the Devnet sandbox and happy to do it. I have Anyconnect on my personal laptop, and have entered the VPN address and credentials handed to me by the deployed lab, but I continue to get this error
"the remote connection was not made because the name of the remote access server did not resolve"

if I do a nslookup from powershell on my system to that deventsandbox URL it resolves fine

[bigevilbeard]

@btchamberlin Not seen this one yet, sounds like a dns problem (it’s always dns! - jokes). What if you enter the IP address and port instead, does it work then? All sandbox VPN is on public IP, a port separates each sandbox/user.

Are you going direct from your laptop, you are not on a vm on your laptop?

[btchamberlin]

Hey @bigevilbeard I confirmed the dns settings on the VPN IPv4 connection is set to automatic but also tried manually setting 8.8.8.8 and 1.1.1.1.  I am not using any vm, this is direct from my personal laptop.  I downloaded the Cisco Secure Connect client from microsoft app store, not sure if that was wise but was the easiest to install and gives me app version 5.1.7.93.  Just tried the resolved ip:port combo and am seeing the same error.

[bigevilbeard]

It’s a long shot, but you can and disable ipv6 on your network adapter settings. I would say try open connect, but saw some issues with this on windows before.

[btchamberlin]

tried openconnect, and tried ending/starting new lab.  I tried disabling IPv6 on the VPN network adapter.  NeverConnect is what it should be called, for now proceeding with studies with no labbing :(.  Thanks @bigevilbeard for the replies and suggestions.

[btchamberlin · Accepted solution]

Okay I circled back to test again, figured out the issue, and its really simple.
When adding a new VPN connection, from the client, it takes me to Windows 11 VPN settings, but it defaults to Windows11 Built-in VPN (drop down menu at very top), I just needed to select AnyConnect profile, im guessing the certificate in the Anyconnect client wasn't being used previously and so it was failing, but its working fine now

[bigevilbeard]

Awesome!