Anyconnect fails - unable to bind to [127.0.0.1]:62523

[thewhinger]

Hi

Windows Vista 64, using AnyConnect Secure Mobility Client v3.1.01065

Connection gets to the point where it authenticates, gives me the MOTD banner, then disconnects.

In the event log is this error:

Function: CTcpListenTransport::initiateListening

File: ..\Common\IPC\TcpListenTransport.cpp

Line: 125

Invoked Function: ::bind

Return Code: 10013 (0x0000271D)

Description: An attempt was made to access a socket in a way forbidden by its access permissions.

unable to bind to [127.0.0.1]:62523

The cli version of the client gives an error:

>> state: Connecting

>> notice: Establishing VPN session...

>> notice: Connection attempt has failed.

>> error: AnyConnect was not able to establish a connection to the specified secure gateway. Please try connecting again.

>> state: Disconnected

It does this most of the time; occasionally (and seemingly randomly) when I restart windows and connect it will work fine, after which it works repeatedly (including after disconnects due to hibernation) until I restart windows again (at which point it goes back to failing).

I can't see anything in the output from netstat -an that would suggest something else is already bound to this port.

I can always log on to the system using the windows ipsec client so it can't be an authentication issue.

I'm running the standard windows firewall and avast standard antivirus; I can disable both and it makes no difference to the error.

Any suggestions?

Thanks!

[thewhinger · Accepted solution]

Answering my own question. Typical.

It seems that this error message is a roundabout way of saying "you've got internet connection sharing enabled on one of your adaptors".

I was sharing my wifi card so that I can occasionally plug in other wired-only PCs via my laptop.

I disable the ICS and it starts working.

I've no idea why sometimes it works anyway, but since it's now working I don't care.

[olpeleri]

Hello,

It's indeed not working with ICS. That's expected.

Cheers.

[thewhinger]

Hmm. I appreciate that ICS on the Cisco adaptor would raise issues, but I'd say it's non-obvious that ICS on a different adaptor would.

It would also be really helpful if a slightly more descriptive error appeared, but that's just my opinion I suppose.

[olpeleri]

Hey Geoff.

If you feel the behavior should be corrected, then you  should open a regular TAC case [ in order to get a bug opened]

Cheers,

Olivier

[thewhinger]

Honestly? I no longer care. I've wasted two days of my life on this, I don't intend to waste any more on it.

I would have thought that you would want your product not to cause the amount of frustration it has to its users; if you have no interest in making your own product better that's not my problem and neither is it something I'll lose sleep over.

I imagine someone else with this problem will find this discussion (it's already in the top results for a google search for the error); I hope that as a result they get to waste rather less time on it than I did. Beyond that I have no interest in improving your product for you.

As an aside, I can't figure out how to mark this question as answered - I can only click "Correct Answer" on someone else's post, which seems bizarre, given that the answer I gave was the solution; the end result therefore appears to be that in order to mark the question as answered I must give credit to someone who did not in fact answer the question.