Forum Discussion
jone14_166962
Altocumulus
AltocumulusBig-IP Edge Client / Windows 10 1809 - No internet connection with connected VPN
Hi everybody
I've updated my computer to Windows 10 Build 1809:
After a successfull connection with Big-IP Edge Client VPN the internet connection is broken. Ping to Google DNS servers with connected VPN:
We have configured Network Access with "split tunneling". The very same VPN worked perfectly with the previous build of Windows 10 (1803).
Version of VPN client: 7160,2018,417,2013
Does anyone run into the same problem?
Thank you, John
The latest windows update for Windows 10 1809 January 22, 2019—KB4476976 (OS Build 17763.292) seems to fix the issue!
rapopd_378474Nimbostratus
Same problem. Cannot be on VPN without losing internet connections due to split tunnel set by my admins. I am not an admin so cannot change the settings to rout all traffic as suggested above. Microsoft is not able to help me, and in fact does not admit to knowing about the problem!! Any suggestions as to how to contact f5?
jone14_166962Hi rapopd,
The problem is known by Microsoft. See https://support.microsoft.com/en-us/help/4464619/windows-10-update-history. This article says that Microsoft is working on a resolution and will provide an update in an upcoming release.
So hopefully it will be fixed in the december cumulative updates (coming next week).
- rapopd_378474
At present, the link describes the problem (Nov 14) but the suggested workaround is to force all tunneling to one channel. This is not an option for my organization, so there is no present workaround. And microsoft support denies knowing about the problem when I called them to find out if there was any progress! So I guess the only solution is to patiently suffer an wait for them to issue a release that miraculously makes the problem go away.
- rapopd_378474
December cumulative update applied today (now Windows lists Version as 10.0.17763 Build 17763). No improvement - still cannot access internet when VPN is enabled. Any suggestions?
Rammnz_262492I installed F5 access app from Microsoft Store in Windows 10, configured the VPN connection and this issue hasn't occured. The concerned user is able to access all the applications through VPN tunnel and also internet.
MTjerneld_37964We also tried the F5 Access UWP app, which adds a VPN Provider to Windows 10. However, it does not seem to support OTP-tokens (we use SMS), so it just returns "wrong username/password". Can someone verify whether OTP/MFA is unsupported with F5 Access or if we need to adjust something to get it working?
boneyardMVP
bit of an off topic question, but looking at the documentation: https://support.f5.com/kb/en-us/products/big-ip_apm/manuals/related/f5-access-config-note-win10-1-2.html
it only supports client certificates as second factor.
- rapopd_378474
Latest update from my IT department is that this is an INTENTIONAL change to security by Microsoft. Split tunneling is no longer being supported by our IT due to need for increased security. So, until things change, our IT department is no longer allowing VPN and internet browsing at the same time unless you log into a remote desktop connection!! Does any one know if this is likely to change with new updates?
- rapopd_378474
We need input from F5. Does anyone know how to contact them for their take on the issue. My IT department says it is a feature of Windows 10 that is preventing them from implementing split tunneling without blocking internet access on a VPN due to security concerns. I find this hard to live with.
- Tuxerl_164080
Also Microsoft's January Patchday (KB4480116) seems not to fix the split tunneling issue. I would really love to hear an answer from f5 support other than "this is a Microsoft issue, we cannot help you" ... Is there no way for f5 to implement a working workaround together with Microsoft ? The issue is known for more than 3 months!
- DCL_381043
Confirming that "January 8, 2019—KB4480116 (OS Build 17763.253)" does not resolve F5 issue. Agree with Tuxerl's sentiment, surprising F5 has not yet worked with MS to discover issue and release fix.
- Ryan_M_362715
Anyone have updates on this? We are experiencing this issue as well.
- a_basharat
Please open a ticket with F5 [everyone], the more tickets the more awareness on the issue. In the meantime, a workout is to switch from split-tunnel to full tunnel which might be not great
- Saravanan_M_K
Employee
Microsoft has fixed this issue in the upcoming Windows 10 19H1 (Redstone 6), roughly scheduled to be released to the public in Mar/Apr 2019.
The current status of Windows 10 Redstone 6 is Build 18317. It was the 19th Insider Preview build of Windows 10 released after RS5 build. It was released on January 16, 2019. This new build arrived via new "19H1" development branch.
- jone14_166962
The latest windows update for Windows 10 1809 January 22, 2019—KB4476976 (OS Build 17763.292) seems to fix the issue!
- Portallion_1480
I can also confirm that installing this patch has resolved the issue.
- Ryan_M_362715
Confirmed as well.
- DCL_381043
Confirming that Win10 Version 1809 (OS Build 17763.292) resolved issue for us.
