Share via

cannot enable shared access. error: 87 the parameter is incorrect (VPN Starts Internet Connection Sharing service failure )

Anonymous
2018-01-11T04:33:17+00:00

When trying to enable Internet Connection Sharing on a VPN connection (windows build in VPN client), it can't be done and returns an error information:

"cannot enable shared access. error: 87 the parameter is incorrect"

This BUG has been brought to Windows 10 for a long time , probably  since Version 1607, and still remains unfixed untill now (Version 1709, Build 16299.15)

In early windows 10 version such as 1511, this function works fine.

Here comes the most weird thing. I'm pretty sure about my OS is fine. I've reinstall my windows 10 system and the sharing function is just fine on other network adapters such as ethernet or wi-fi adapter, even a 3rd party VPN client adapter. 

The function just can't work on windows build in vpn client (WAN Miniport adapter) .

I hope Microsoft engineer can fix this bug soon . I have been waiting a long time for this and posted an question before this one

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

9 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-01-19T05:20:07+00:00

    Hi Dxt00,

    After some more research on my end I've found that, it appears, that Split Tunneling has been turned off in the later versions of Windows 10 by default due to some security concerns. It can/must now be enabled by executing a simple PowerShell command, more complete information and instructions can be found at the links below;

    http://eyonic.blogspot.com/2016/06/how-to-enable-vpn-split-tunneling-in.html

    https://www.irangers.com/how-to-enable-split-tunneling-on-windows-10-vpn-connections/

    I hope that this helps and is what you are looking for.

    Let us know, and Good Luck.

    -Richard

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments
  2. Anonymous
    2018-01-12T11:01:16+00:00

    Updated to Version 1709, is Build 16299.192 , but still no working

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-01-12T11:00:21+00:00

    Hi,

    This is a common concern when the requirement of the VPN provider is not met. Please check the required settings needed to run your VPN given by your provider. We also have limited resources on VPN and may provide invalid troubleshooting so it's best to post the concern on Microsoft TechNet forum.

    Update us if you need further assistance.

    All the best.

    It is not about VPN connecting problem. It connects smoothly.

    It is about I can't enable Internet Connection Sharing function on your any kind windows build-in VPN adapters, weather it is configured to PPTP, L2TP or ikev2. 

    It's nothing about the VPN provider, actually It is me who set up the VPN server.

    All I know is this function doesn't work since Version 1607(maybe earlier version), but still works fine on Version 1511.

    I have tried to reinstall Version 1511 and Version 1709 on the same hardware to exclude any other influence.

    The result proofs that you must have brought some glitch to  Internet Connection Sharing function

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  4. Anonymous
    2018-01-12T07:30:51+00:00

    Hi,

    This is a common concern when the requirement of the VPN provider is not met. Please check the required settings needed to run your VPN given by your provider. We also have limited resources on VPN and may provide invalid troubleshooting so it's best to post the concern on Microsoft TechNet forum.

    Update us if you need further assistance.

    All the best.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  5. Anonymous
    2018-01-12T09:54:14+00:00

    You could try updating your Win 10 installation as the current build # for Version 1709, is Build 16299.192.

    https://support.microsoft.com/en-us/help/4043454/windows-10-windows-server-2016-update-history?ocid=update_setting_client

    Was this answer helpful?

    0 comments