I recently had the need to VPN into a network using an F5 Networks VPN. Turns out the provided BIG-IP Edge Client installs ok on Windows 10 but doesn't connect. I kept getting the "Network Access Connection Device was not found." error at the last step of connecting.

"Network Access Connection Device was not found."

Turns out that it was adding a 'device' to device manager but not associating a driver to it. Easily fixed as it happens.

  • Open Device Manager.
  • Find the f5 driver with the warning triangle icon
  • Open its properties, go to the Driver tab, select update driver...
  • Choose browse my computer for driver software
  • Choose Let me pick from a list of device driver on my computer
  • Select F5 Networks fro the left-hand side
  • Select F5 Networks VPN Adapter from the right-hand side. Click next
  • Accept the warning, yes you want to continue

I'm not sure if this driver is standard to windows 10, or only there because I did an in-place upgrade from Windows 7. I assume it is in there by default.

Try connecting again, and you should succeed!

Now at this stage, once connected, you are likely to have every DNS error imaginable connecting to anywhere. This shows as "DNS-PROBE-FINISHED-NXDOMAIN" in chrome.

This had to do with the "F5 Networks DNS Relay Proxy Service". You have two options:

  • Disable the service, deal with UAC
  • Restart the service after every connect.

Depending how often you need to use the VPN, you have a choice. If you disable the service, you will need to accept a UAC dialog after connecting. This dialog will open over and over again on top of itself until you say yes. Annoying, but only right after connecting.

The other option is that after connecting, you have to go into services and restart "F5 Networks DNS Relay Proxy Service". Every time.

I can't say what the service does, what the consequences of not having it running are (apart from the UAC dialog) so up to you what you choose.

I hope this helps other people getting stuck trying to run their VPN on Windows 10 until the officially supported versions become available and get rid of these two small problems in their client software. It is also worth noting that I had a version 7 installer, so you may not get the exact experience I did since I believe they are now up to version 10.