Forum Discussion

SteveVernau_132's avatar
Icon for Nimbostratus rankNimbostratus
Apr 18, 2016

Big IP Edge Client windows 10 no connectivity with VPN - works on windows 7

Hi we are using Big IP Edge client for VPN connection. We validate with user creds, machine certificate check and antivrus check.


When connecting from a windows 7 machine all is well and works as expected.


When connecting form a windows 10 machine, the VPN connects (Access policy is passed A-OK) and it all seems ok (ip address assigned from correct lease pool etc) but I cannot connect to anything! I can see the traffic leaving the client (when I look at firewall logs the client is sending out the traffic to servers i am trying to RDP to for example) but it seems when the traffic is on its way back it doesn't properly get handled by the client (as if maybe its not getting decrypted by the edge client and sent on to application layer or something like that)


Now we are running 11.6 Hotfix 6 which is compatible with windows 10 but so far support haven't been much help. I provided them decrypted tcpdump from F5, wireshark from client, f5wininfo output but last update from support was to disable windows firewall which made no difference (I knew it wouldnt as all outbound traffic allowed anyway and VPN connection is all outbound) then they asked to check that machine has latest windows updates! (As if thats got anything to do with it)


This is causing much grief as we are about to rollout win 10 to the company but unless I can get VPN working its delaying rollout.


Anyone seen this before?


Any help would be greatly appreciated.


7 Replies

  • First I would rule out if its the client compatibility issue. You can try to download the Edge client from windows store instead of the device and try establishing the VPN connection and see if it helps. Can you also try and see it work via browser?


  • Found the issue. We are migrating from Junos Pulse VPN to F5 APM VPN and while having both installed on windows 7 works just fine, for some weird reason having both on windows 10 doesn't. The tunnel is established and traffic leaves the client to go to the hosts you are connecting to but for some reason the return traffic is blocked by the client. As soon as I uninstalled junos pulse this issue went away! Weird as its same version of pulse and same version of edge client, only diff is OS but for whatever reason win 10 cannot handle coexistence of these two VPN apps.


    • Daniel_W__13795's avatar
      Icon for Nimbostratus rankNimbostratus
      Have you opened a service request? I had the same issue that prevents us from a smooth migration Pulse Secure to F5 APM. PM told us that both VPN clients are not supported ;(
    • Sec-Enabled_658's avatar
      Icon for Cirrostratus rankCirrostratus

      Was there ever a workaround for this? I am experiencing the same thing.


  • we are using SSL VPN is working in windows10, i think it may routing issue please apply proper SNAT and routing to servers segment and add return route to F5 SNAT IP or self IP in core switch.