AnyConnect Client Fails Only for Windows 7+ from Comcast Network

[charlessullivan3]

Using Client version 3.1, we have three different ASA devices running AnyConnect VPN. VPN1, VPN2 and VPN3 function properly from Windows clients within our company network and from most networks outside of ours. However from Comcast's network, VPN1 and VPN2 are always accessible, but VPN3 fails only on Windows clients with the following message: "Connection attempt failed due to network or PC issue".

All three of the ASAs are in the same subnet and at the same code level. The one difference with VPN3 is that it doesn't have a legitimate SSL cert, but we have instructed the few users who rely on it to allow connections to untrusted servers. (These are all IT folks doing DR testing.)

Here are a couple of log snippets that I think are relevant:

********************************************************************************

Invoked Function: CTransportWinHttp::processRequestResponse
Return Code: -30015449 (0xFE360027)
Description: CTRANSPORT_ERROR_SET_RESPONSE_DATA

Invoked Function: CTransport::SendRequest
Return Code: -30015451 (0xFE360025)
Description: CTRANSPORT_ERROR_SEND_REQUEST

********************************************************************************

We are going to acquire a certificate sometime within the next month, but I'm not confident that it will make a difference, so I'm hoping I can get some kind of idea why this is happening now. I have to assume that contacting Comcast will be futile, so I'm hoping this is something that can be corrected on our end.

Thanks for any ideas.

[Peter Davis]

Please send a DART (diagnostics report) from a failed and successful connection to ac-mobile-feedback@cisco.com and we will be glad to investigate.

[charlessullivan3]

Thanks. I just sent the 2 DART reports to the address you provided, along with an explanation.

[Peter Davis]

Thanks for following up with us via email. We sent you a follow-up message with a next step to troubleshoot.

[ackoch001]

What was the solution?

[charlessullivan3]

Not a good one, but I would have to say it was outside of Cisco's control. I just found the email message I sent to the Cisco Tech in October 2015. It says this:

"Although the exact cause was not ever determined, just recently we switched ISPs from Sidera to Level 3 and that was all it took to resolve the issue."