AnyConnect VPN client version 2.5.0217- not able to establish connection to gateway

[lindacbennett13]

I am getting an error when trying to establish a connection to the secure gateway:  AnyConnect was not able to establish a connection to the specified secure gateway.  Please try connecting again.

I have tried connecting again many times.  I have also tried rebooting my machine and connecting to no avail.  The problem seems to be intermittent though, because it did connect just fine over the past few days.  Can anyone assist?

I am runing version 2.5.0217 on windows Vista.

[Luiz Veneziani]

Wow. I wasn't too convinced this could do it but I was desperate enough to try anything.

It worked like magic!!!

Thank you for sharing your solution.

[Fadel Matar]

Worked for me as well, thanks!

[kiranoddiraju]

We had the same issue earlier today. After intense troubleshooting we noticed somehow the client profile was missing. We added the client profile with the correct xml file and it started working again. Hope this helps someone who has similar issue.

[abha16]

Problem solved. I love you!

[Nishant Potdar]

I'm facing an issue similar to above issues.

I'm using a laptop provided by my office and I connect to office network using cisco AnyConnect VPN client. When I try to connect using my home WiFi, I can't connect any of the predefined gateways, even my outlook client for O365 doesn't work when I'm on WiFi.

Once I connect my laptop to a datacard, both VPN and outlook works smoothly. 

I contacted my ISP also, he asked me to share TCP/UDP ports used to connect to the VPN so that he can open those ports if those are blocked for security purpose.

Can anyone help me to resolve the issue?

Br,

Nishant

[DigHealthVPNEndUserRGS]

After reading these posts and remembering that my homegroup printers stopped working when I made a successful Cisco VPN connection, I immediately realized it was Windows Homegroup.  Upon disabiling it, the Cisco connection worked just fine. 

This error is probably because Cisco is making checks for security, other computers which can connect into the network without credentials.   First try disabling Homegroup (which finally worked for me).  Other users here have disabled Bluetooth networks emanating from the computer.  Altering "allow other network users to connect through this computer's internet" made no difference for me.  

[gsankatrading]

My solution for this issue was a little different. When I first opened Any Connect, I clicked on the Settings Icon (Looks like a Gear) located on the lower left. Then click on Preferences and make sure Block Connections to Untrusted Servers is selected. 

For me it was only happening on Windows 10 machines, Windows 7 machines were unaffected. I tried everything and rechecked all my settings it was a pain. I notice this wasnt selected on the machines that has Windows 10 installed. Not sure if this was helpful but it worked for me. 

[prasaath.d@axiscapital.com]

Hi Team

Am prasaath we also facing same issue only two users were not able to connect to CiscoAnyConnect VPN .

So that i have  run a debug on ASA .

Am seeing that LDAP communication is not happening. Please check & update.

[148095] Session Start
[148095] New request Session, context 0x725fac60, reqType = Authentication
[148095] Fiber started
[148095] Creating LDAP context with uri=ldap://10.11.140.10:389
[148095] Connect to LDAP server: ldap://10.11.140.10:389, status = Successful
[148095] supportedLDAPVersion: value = 3
[148095] supportedLDAPVersion: value = 2
[148095] Binding as Service-CiscoVPN
[148095] Performing Simple authentication for Service-CiscoVPN to 10.11.140.10
[148095] LDAP Search:
Base DN = [dc=axisspecialty,dc=net]
Filter = [sAMAccountName=prasaath.d]
Scope = [SUBTREE]
[148095] User DN = [CN=D\, Prasaath,OU=Users,OU=Wipro,DC=axisspecialty,DC=net]
[148095] Talking to Active Directory server 10.11.140.10
[148095] Reading password policy for prasaath.d, dn:CN=D\, Prasaath,OU=Users,OU=Wipro,DC=axisspecialty,DC=net
[148095] Read bad password count 0
[148095] Binding as prasaath.d
[148095] Performing Simple authentication for prasaath.d to 10.11.140.10
[148095] Simple authentication for prasaath.d returned code (49) Invalid credentials
[148095] Message (prasaath.d): 80090308: LdapErr: DSID-0C090400, comment: AcceptSecurityContext error, data 52e, v1db1
[148095] Invalid password for prasaath.d
[148095] Fiber exit Tx=624 bytes Rx=11640 bytes, status=-1
[148095] Session End

[148097] Session Start
[148097] New request Session, context 0x725fac60, reqType = Authentication
[148097] Fiber started
[148097] Creating LDAP context with uri=ldap://10.11.140.10:389
[148097] Connect to LDAP server: ldap://10.11.140.10:389, status = Successful
[148097] supportedLDAPVersion: value = 3
[148097] supportedLDAPVersion: value = 2
[148097] Binding as Service-CiscoVPN
[148097] Performing Simple authentication for Service-CiscoVPN to 10.11.140.10
[148097] LDAP Search:
Base DN = [dc=axisspecialty,dc=net]
Filter = [sAMAccountName=prasaath.d]
Scope = [SUBTREE]
[148097] User DN = [CN=D\, Prasaath,OU=Users,OU=Wipro,DC=axisspecialty,DC=net]
[148097] Talking to Active Directory server 10.11.140.10
[148097] Reading password policy for prasaath.d, dn:CN=D\, Prasaath,OU=Users,OU=Wipro,DC=axisspecialty,DC=net
[148097] Read bad password count 1
[148097] Binding as prasaath.d
[148097] Performing Simple authentication for prasaath.d to 10.11.140.10
[148097] Simple authentication for prasaath.d returned code (49) Invalid credentials
[148097] Message (prasaath.d): 80090308: LdapErr: DSID-0C090400, comment: AcceptSecurityContext error, data 52e, v1db1
[148097] Invalid password for prasaath.d
[148097] Fiber exit Tx=624 bytes Rx=11640 bytes, status=-1
[148097] Session End
debug ldap 200
debug ldap enabled at level 200
AMSASA#
[148102] Session Start
[148102] New request Session, context 0x725fac60, reqType = Authentication
[148102] Fiber started
[148102] Creating LDAP context with uri=ldap://10.11.140.10:389

[prasaath.d@axiscapital.com]

Hi Team

Still 2 users from my environment facing issue in connect to Cisco Any Connect VPN.

i have already run a Debug command .

kindly find the below Debug Output.

Please any one Assist on this.

[148095] Session Start
[148095] New request Session, context 0x725fac60, reqType = Authentication
[148095] Fiber started
[148095] Creating LDAP context with uri=ldap://10.11.140.10:389
[148095] Connect to LDAP server: ldap://10.11.140.10:389, status = Successful
[148095] supportedLDAPVersion: value = 3
[148095] supportedLDAPVersion: value = 2
[148095] Binding as Service-CiscoVPN
[148095] Performing Simple authentication for Service-CiscoVPN to 10.11.140.10
[148095] LDAP Search:
Base DN = [dc=axisspecialty,dc=net]
Filter = [sAMAccountName=prasaath.d]
Scope = [SUBTREE]
[148095] User DN = [CN=D\, Prasaath,OU=Users,OU=Wipro,DC=axisspecialty,DC=net]
[148095] Talking to Active Directory server 10.11.140.10
[148095] Reading password policy for prasaath.d, dn:CN=D\, Prasaath,OU=Users,OU=Wipro,DC=axisspecialty,DC=net
[148095] Read bad password count 0
[148095] Binding as prasaath.d
[148095] Performing Simple authentication for prasaath.d to 10.11.140.10
[148095] Simple authentication for prasaath.d returned code (49) Invalid credentials
[148095] Message (prasaath.d): 80090308: LdapErr: DSID-0C090400, comment: AcceptSecurityContext error, data 52e, v1db1
[148095] Invalid password for prasaath.d
[148095] Fiber exit Tx=624 bytes Rx=11640 bytes, status=-1
[148095] Session End

[148097] Session Start
[148097] New request Session, context 0x725fac60, reqType = Authentication
[148097] Fiber started
[148097] Creating LDAP context with uri=ldap://10.11.140.10:389
[148097] Connect to LDAP server: ldap://10.11.140.10:389, status = Successful
[148097] supportedLDAPVersion: value = 3
[148097] supportedLDAPVersion: value = 2
[148097] Binding as Service-CiscoVPN
[148097] Performing Simple authentication for Service-CiscoVPN to 10.11.140.10
[148097] LDAP Search:
Base DN = [dc=axisspecialty,dc=net]
Filter = [sAMAccountName=prasaath.d]
Scope = [SUBTREE]
[148097] User DN = [CN=D\, Prasaath,OU=Users,OU=Wipro,DC=axisspecialty,DC=net]
[148097] Talking to Active Directory server 10.11.140.10
[148097] Reading password policy for prasaath.d, dn:CN=D\, Prasaath,OU=Users,OU=Wipro,DC=axisspecialty,DC=net
[148097] Read bad password count 1
[148097] Binding as prasaath.d
[148097] Performing Simple authentication for prasaath.d to 10.11.140.10
[148097] Simple authentication for prasaath.d returned code (49) Invalid credentials
[148097] Message (prasaath.d): 80090308: LdapErr: DSID-0C090400, comment: AcceptSecurityContext error, data 52e, v1db1
[148097] Invalid password for prasaath.d
[148097] Fiber exit Tx=624 bytes Rx=11640 bytes, status=-1
[148097] Session End
debug ldap 200
debug ldap enabled at level 200
AMSASA#
[148102] Session Start
[148102] New request Session, context 0x725fac60, reqType = Authentication
[148102] Fiber started
[148102] Creating LDAP context with uri=ldap://10.11.140.10:389
[148102] Connect to LDAP server: ldap://10.11.140.10:389, status = Successful
[148102] supportedLDAPVersion: value = 3
[148102] supportedLDAPVersion: value = 2
[148102] Binding as Service-CiscoVPN
[148102] Performing Simple authentication for Service-CiscoVPN to 10.11.140.10
[148102] LDAP Search:
Base DN = [dc=axisspecialty,dc=net]
Filter = [sAMAccountName=prasaath.d]
Scope = [SUBTREE]
[148102] User DN = [CN=D\, Prasaath,OU=Users,OU=Wipro,DC=axisspecialty,DC=net]
[148102] Talking to Active Directory server 10.11.140.10
[148102] Reading password policy for prasaath.d, dn:CN=D\, Prasaath,OU=Users,OU=Wipro,DC=axisspecialty,DC=net
[148102] Read bad password count 2
[148102] Binding as prasaath.d
[148102] Performing Simple authentication for prasaath.d to 10.11.140.10
[148102] Simple authentication for prasaath.d returned code (49) Invalid credentials
[148102] Message (prasaath.d): 80090308: LdapErr: DSID-0C090400, comment: AcceptSecurityContext error, data 52e, v1db1
[148102] Invalid password for prasaath.d
[148102] Fiber exit Tx=624 bytes Rx=11640 bytes, status=-1
[148102] Session End

[ziqex]

I have experienced the same issue with not being able to establish connection to gateway. In my case the issue was laying on the ISP side as the there was no issues when I tried connecting on different network.

Thank you.