VPN credentials for DevNet Sandbox not working

[boss1944]

I have been able to successfully launch various sandboxes and establish a VPN connection with AnyConnect using the url supplied in the accompanying email, but the supplied log on credentials never work.  This is getting rather annoying now as I am trying to follow a learning track in DevNet but have stalled as I cannot establish a connection to any of the sandboxes reference in the track.  Has anyone else had this problem and know of any solutions?  It is not really helpful that there is no longer a means of directly contacting the DevNet Sandbox team anymore.

[bigevilbeard]

@boss1944 the community has always been the place to connect and contact the sandbox team and report issue. 

To address your question and so I understand your issue. You have reserved a sandbox, the sandbox sets up (without error) you have your vpn connection details, these work and your vpn to the reservation connects fine. However when you try to login to a device, this is via ssh, http, netconf, restconf, this all fails? Which sandbox is this? 

If you can provide some more details, I’m sure someone can help here.

[boss1944]

Hi, thank you for your reply.  The sandbox in question is the Network Services Orchestrator sandbox.  The issue I am having is more or less as you describe, the sandbox launches without error but when I try to establish a VPN connection with AnyConnect the initial connection is successful but the supplied user and password credentials do not work.  However, having tried again recently after waiting for about 10 to 15 minutes after the sandbox has successfully launched I am able to connect with the supplied credentials.  It seems as if there is some sort of lag between my receiving the email informing me the sandbox has launched and actually being able successfully establish the VPN connection.  I'm not sure if this is down to the time zone difference as I am in the UK and accessing a sandbox in the US, or whether there is some sort of latency over the internet connection.  But like I said, I can now successfully launch and connect to sandboxes if I wait 10 to 15 minutes after the launch is complete.  I just have to factor this into my reservation time.

[bigevilbeard · Accepted solution]

Hey @boss1944 good that working now. The lag you see is normal, one of the team posted this in a thread recently, that even tho the vpn is set up, the build of the sandbox takes a little while longer and it’s suggested to wait 10 - 20 minutes, as the build completes before you can fully access. Hopefully it does not cut too much into your lab fun!