Windows 10: Always on VPN Device Tunnel Issue with Feature Update 2004

Hello all,


I've searched around on how to submit a bug report but I was unable to figure out where to do it so I hope this is appropriate. If this is not the proper place to report this issue, where do I need to go?


I have Always on VPN user and device tunnels deployed at my org. Prior to the 2004 feature update, both device and user tunnels could coexist and connect at the same time without issues.


The device tunnel was deployed using Intune to the managed devices using a custom XML. The user profile was deployed using a logon script. This was all working properly until feature update 2004.


Now with feature update 2004, device and user tunnels cannot be connected at the same time.


If the user tunnel attempts to connect while the device tunnel is connected, they'll get the error "A connection to the remote computer could not be established, so the port used for this connection was closed."


Similar issues were reported below about 1709 but fixed in 1809.


https://github.com/MicrosoftDocs/windowsserverdocs/issues/900


It appears the same regression has occurred with 2004.

:)

 

Vpn ( trusted Vpn)

Hi everyone.
I am not an expert about Vpn and that's why I would like to know if someone could list me a few trusted Vpns, I would really appreciate any suggestion/ advice.

Thanks.

 

Always On VPN Device Tunnel not starting automatically when device Boots up.

Always On VPN Device Tunnel not starting automatically when device Boots up.

When laptop turns on it does not automatically connect to the Always On VPN until I trigger it by disabling wireless and then enabling it.

 

Vpn ( trusted Vpn)

Tired of Germany blocking many youtube videos? *Big Grin