Forum Discussion
NimbostratusEdge Client not downloading config using APM
Some of our users are unable to access our VPN using a browser in Windows 7. I am aware there is an issue with installing the extensions due to policy changes at Google. I am trying to configure the F5 Edge Client as a work around. I am getting the following error in the edge client logs; Error 2014-06-16 22:34:52:025 HOST \HostCtrl.cpp, CHostCtrl::OnTimer(), TUNNEL_SERVER_READY_CHECK - configuration read timed out Error 2014-06-16 22:34:52:025 HOST \HostCtrl.h, CHostCtrl::Failed, Failed to download configuration (error: 0) Error 2014-06-16 22:34:52:025 HOST \HostCtrl.h, CHostCtrl::Failed, Firing event (message: Failed to download configuration) Error 2014-06-16 22:34:52:026 Standalone CStandaloneDoc::HandleError, Force logoff (Reason: Failed to download configuration)
I am not finding good direction in the documentation. Has anyone hit this before?
Thanks
5 Replies
Kevin_Davies_40Nacreous
One of the problems that occur is the VPN adapter does not have permission to install. You should check that it is actually installed on the client machines.
jim_mcmurchie_1I checked Computer Management / Device Manager and F5 VPN client did show under hidden devices. Anything else I can try? The F5 troubleshooting utility shows several files missing from C:\Windows\Downloaded Program Files\ but the documentation says that their presence is dependent on the version of WIndows, etc installed
- Sec-Enabled_658
Cirrostratus
I am getting the same error. Neither browser or edge client works. running version 11.5.1 HF5
- boneyard
MVP
i would advise you to create a new question with some more info. did it work in the past? which OS, which browser, where did you get your client from? does it work from other systems? if you can you could also open a TAC case. - Sec-Enabled_658I eventually fixed this by checking the default client ssl profile that I had set for the virtual server. I was using the default cert and key in the client ssl profile assigned to the vip, but the cert had expired in 2011. Saw this again in my lab two months later. Fix. Create a new cert and key, add them to the client ssl profile, assign the new profile to the vip.
