SD WAN anyconnect vpn connection time's out

[pmudaliar]

Trying to Connect to Cisco SD WAN Lab with VPN information received in email.
Lab Network Address: devnetsandbox-emea-gwy.cisco.com:20230
I do have internet access.

When using AnyConnect to login, I get below message
"Connection attempt has timed out. Please verify Internet connectivity."

[bigevilbeard]

Hey there, The port range will be anywhere from TCP 20100 through TCP 20354. Give that a try and you should be good to go. If that's not working, keep in mind VPNs also use TLS (TCP 443) and DTLS (UDP 443). Though typically these are open in most organizations, however please check these are open.

Hope this helps

[pmudaliar]

Hi 

I recreated the lab , however I still get a VPN connection timeout while trying to connect to 

devnetsandbox-emea-gwy.cisco.com:20223

SDWAN sandbox

Earlier ,

I was assigned a lab for Collaboration sandbox in in US Region

: devnetsandbox-us-sjc.cisco.com:20119

VPN to this lab worked well, without any issues

Could it be there are some VPN issues in EMEA as the US Sandboxes are working?

[bigevilbeard · Accepted solution]

I reserved and connected to devnetsandbox-emea-gwy.cisco.com:20227 no problems

(venv) STUACLAR-M-R6EU:sd_wan_demo stuaclar$ date
Thu 26 Mar 2020 18:12:09 GMT
(venv) STUACLAR-M-R6EU:sd_wan_demo stuaclar$ time python get_devices.py
╒═════════════╤═════════════╤════════════╤══════════════════════════════════════╤═════════════╕
│ Host Name   │ Device IP   │ Site ID    │ Host ID                              │ Host Type   │
╞═════════════╪═════════════╪════════════╪══════════════════════════════════════╪═════════════╡
│ vmanage-01  │ 4.4.4.90    │ vmanage-01 │ e85cd6d5-4dea-46a1-affb-38fd4cd8debd │ vmanage     │
├─────────────┼─────────────┼────────────┼──────────────────────────────────────┼─────────────┤
│ vsmart-01   │ 4.4.4.70    │ vsmart-01  │ 50cb5f09-3b74-49b7-aa5a-c17db012206c │ vsmart      │
├─────────────┼─────────────┼────────────┼──────────────────────────────────────┼─────────────┤
│ vbond-01    │ 4.4.4.80    │ vbond-01   │ 8163a199-96b2-4886-9b20-bcb9fce4bf88 │ vedge-cloud │
├─────────────┼─────────────┼────────────┼──────────────────────────────────────┼─────────────┤
│ vedge-001   │ 4.4.4.60    │ vedge-001  │ 100faff9-8b36-4312-bf97-743b26bd0211 │ vedge-cloud │
├─────────────┼─────────────┼────────────┼──────────────────────────────────────┼─────────────┤
│ vedge-002   │ 4.4.4.61    │ vedge-002  │ f3d4159b-4172-462c-9c8d-8db76c31521d │ vedge-cloud │
├─────────────┼─────────────┼────────────┼──────────────────────────────────────┼─────────────┤
│ vedge-003   │ 4.4.4.64    │ vedge-003  │ 0435c3e8-d3a0-4c6b-af0a-f95d41974d69 │ vedge-cloud │
├─────────────┼─────────────┼────────────┼──────────────────────────────────────┼─────────────┤
│ vedge-004   │ 4.4.4.65    │ vedge-004  │ 46c18a49-f6f3-4588-a49a-0b1cc387f179 │ vedge-cloud │
╘═════════════╧═════════════╧════════════╧══════════════════════════════════════╧═════════════╛

real	0m1.380s
user	0m0.156s
sys	0m0.043s

Might be worth tearing down your current reservation and grabbing a new one.

Hope that helps