I suppose this could be done for Windows Client by adding <AutoUpdate>false</AutoUpdate> to AnyConnectLocalPolicy.xml? I tried but it still does not connect. Here are some logs from client might seem interesting though: Function: CHostLocator::buildHostLocator File: .\Utility\HostLocator.cpp Line: 324 Invoked Function: CSocketSupport::getHostName Return Code: -31195121 (0xFE24000F) Description: SOCKETSUPPORT_ERROR_GETNAMEINFO failed to resolve IP address server.ip.address Function: CAutoProxy::GetAutoProxyStrings File: .\Proxy\AutoProxy.cpp Line: 139 Invoked Function: WinHttpGetProxyForUrl Return Code: 12180 (0x00002F94) Description: WINDOWS_ERROR_CODE SG URL https://server.ip.address:443 Function: CProxyCommonInfo::getProxyStrings File: .\Proxy\ProxyCommonInfo.cpp Line: 803 Invoked Function: CAutoProxy::GetAutoProxyStrings Return Code: -30539766 (0xFE2E000A) Description: AUTOPROXY_ERROR_OPEN_FAILED Function: SDIMgr::ProcessPromptData File: .\SDIMgr.cpp Line: 336 Authentication is not token based (OTP). On 11/14/2013 10:48 AM, Nikos Mavrogiannopoulos wrote: > On Thu, Nov 14, 2013 at 4:41 PM, Nikos Mavrogiannopoulos > <n.mavrogiannopoulos at gmail.com> wrote: > >> Did you enable the specific options for anyconnect in the configuration file? >> The anyconnect clients download some special policy etc files from the >> server that may not have been there in ocserv. Unfortunately they much >> differ on the requests they make on every version. You may want to >> check the client's log as well for clues of what failed. > btw. most cisco clients I've tried fail because they try to > auto-update from the server. If they don't find the required files for > update they close the connection. If they have the option, try to > disable auto-update as this solved my issues most of the time. > > regards, > Nikos
