For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Joel_60494's avatar
Joel_60494
Icon for Nimbostratus rankNimbostratus
Mar 19, 2009

Error "Couldn't open proxy server" VPN Client Vista

Help out there please...

 

 

I have a user with 64 bit Vista that has the F5 Networks VPN Client. When connecting they are able to do so via the F5 and get authenticated. Problem, no virtual IP gets assigned and the following errors occurs as printed below.

 

 

(HOST:4256,4460) CHostCtrl::Failed: Couldn't open proxy server(0)

 

(HOST:4256,4460) CHostCtrl::CloseClient:control=73554224 m_bConnected=0 m_bFailed=1 Type=V

 

 

Cheers!

 

 

Let me know if more info is needed.
BIG-IP Access Policy Manager (APM)
remote access
security

10 Replies

  • Kevin_67593's avatar
    Kevin_67593
    Icon for Nimbostratus rankNimbostratus
    Aug 11, 2009
    I have a similar problem, on Vista Business 32-bit, launching a VPN connection from a Firepass menu.

     

     

    If I close the "Network Access" window and try again, sometimes the connection will succeed on the second try.
  • Mike_61719's avatar
    Mike_61719
    Icon for Cirrus rankCirrus
    Aug 12, 2009
    What are your NA proxy settings? It would be my guess that it can not resolve the proxy and thus provides you with an error message.
  • sandra_bermudez's avatar
    sandra_bermudez
    Icon for Nimbostratus rankNimbostratus
    Nov 30, 2009
    Got this from F5 - hope it helpd

     

     

    Unfortunately It is a false positive only by Symantec and is not a Firepass issue. The connection failure, and possible error message of "unable to connect to proxy server" occurs because the file "tunnelserver.exe" is being quarantined by all Symantec products.

     

     

    Symantec has released an updated definitions file are available that will resolve the false positive issue

     

    with tunnelserver.exe on the Firepass. This will be released into the normal update channel, but if you need this update

     

    immediately you can obtain it from the link below.

     

     

     

     

    To install, run the respective file on each client to update the definitions.

     

     

    This should restore functionality. If the file was quarantined, be sure to release it from the quarantine. On Symantec it is located in the control panels. Symantec Control Panel>View Quarantine, select the file TunnelServer.exe, and then click Restore.

     

     

    Should users continue to experience any connection problems after this, at the end of this email is a link to our cleaning utility and steps which you can provide to users which will clean remnants of the F5 client and the next time they connect they will be reinstalled properly. Note that users must be local admins of their machine in order to use this utility.

     

     

  • Andy_4942's avatar
    Andy_4942
    Icon for Nimbostratus rankNimbostratus
    Dec 10, 2009
    What is the link to the cleaning utility mentioned on this email? Can it be supplied.

     

  • dabfeh_18958's avatar
    dabfeh_18958
    Icon for Nimbostratus rankNimbostratus
    Jan 11, 2010
    Sorry but what is "F5 box"? can someone simply post the link?

     

    Thanks...
  • Mike_61719's avatar
    Mike_61719
    Icon for Cirrus rankCirrus
    Jan 12, 2010

    Posted By dabfeh on 01/11/2010 11:30 AM

     

     

    Sorry but what is "F5 box"? can someone simply post the link?

     

    Thanks...

     

     

     

    It is on the Firepass, like a direct link on the box. Unfortunately I can not link our Firepass out to you. Ask your F5 Admin's.
  • ItsTheLion_3922's avatar
    ItsTheLion_3922
    Icon for Nimbostratus rankNimbostratus
    Jan 25, 2010
    Not sure if you still having this problem.

     

     

    But you can just open "C:\WINDOWS\Downloaded Program Files", right-click on "F5 Networks Dynamic Application Tunnel Control" and choose remove.

     

     

    Sign in and it should be fixed.