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

rfc19's avatar
rfc19
Icon for Nimbostratus rankNimbostratus
Jan 12, 2015

BIG-IP Edge Client on Windows 8.1 Issue

Hi all,

 

We are experiencing an issue running the BIG-IP Edge Client on Win8.1.

 

On first boot, we are able to connect to the VPN service without any issues. Once we click the 'Disconnect' button and try to reconnect, the Edge Client will sit there trying to reconnect indefinitely. This will continue until we reboot the machine.

 

The following Edge Client logs indicate a routing table issue, however I'm not sure if it's related (the typo is not mine).

 

2015-01-13, 3:28:43:912, 5348,7392,DIALER, 1, \UIpForwardTable.cpp, 769, UIpForwardTable::RestoreRouteTable, Failed to properly restore routing table. Possibly rotuing table is corrupted. Restart the system

 

For your reference: Viprion 2400 | 11.4.1 HF 4

 

Thank you

 

3 Replies

  • Hi,

     

    Raise a support case. Do you know Edge Client is already embedded into Win8.1 ?? Called Inbox VPN Client.

     

    You set your VPN connection from Windows network settings. Select F5 and fill the forms. You can't use it for Client check (AV, FW ...).

     

  • rfc19's avatar
    rfc19
    Icon for Nimbostratus rankNimbostratus

    Thanks Matthieu - case has been raised with F5.

     

    Interesting information regarding the Inbox VPN Client, however we are doing a number of client-side checks, so this would not be feasible.

     

    Also worth noting that this is only occuring in one of our three environments. Configuration has been compared and match up across all environments.

     

  • rfc19's avatar
    rfc19
    Icon for Nimbostratus rankNimbostratus

    Hi all,

     

    It seems as though we have discovered the solution.

     

    When defining the server list in the connectivity profile section, be sure to exclude any reference to protocols (e.g. https://). For some reason, there was causing an issue on Windows 8.1.

     

    Regards