Share via

VPN issues - The initial Secure Socket Tunneling Protocol request could not be successfully sent to the server.

Question

Sunday, July 15, 2018 2:30 PM

Hi everyone,

I’ve faced with VPN connectivity issue. Here is the event description

The initial Secure Socket Tunneling Protocol request could not be successfully sent to the server. This can be due to network connectivity issues or certificate (trust) issues

I’ve already tried different solutions including removing wan miniport items from device manager, checking VPN profile, etc.

VPN itself is ok, I’ve tried to connect to it, using another PC(Win 10 pro) in my local network, with the same credentials and settings, connection running fine.

Any suggestions?

OS: win 10 home, 1803, OS build - 17134.137

All replies (11)

Monday, July 16, 2018 3:50 AM

Hi,

Did you use built-in VPN or third-party? What's difference between Windows 10 work fine and have problem.

Please temporarily turn off firewalls and any antivirus or malware-prevention software to try again.

If the issue persist, run network reset and then re-configure the VPN:

1. Select the Start  button, then select Settings  > Network & Internet  > Status > Network reset.

2.  On the Network reset screen, select Reset now > Yes to confirm. Wait for your PC to restart and see if that fixes the problem.

In addition, the latest build is 17134.165. You can update to this build for test.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Tuesday, July 17, 2018 6:05 AM

Hi Karen, I've tried all of those steps, you've described. And it's not working. The difference between OS - working one - is the win 10 pro, and second one (vpn isn't working) - win 10 home.

About vpn client - I'm using default win 10 vpn client.

Tuesday, July 17, 2018 9:30 AM

That's odd.

Have you rebuild the VPN after network reset?

If yes, could you share the exact error code and message window here?

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Tuesday, July 17, 2018 9:59 AM

Yes, I've rebuild VPN after reset.

Wednesday, July 18, 2018 2:45 AM

Hi,

Try the methods other members used to resolve similar issue:

1. Delete the network adapter driver from Device Manager. Then reboot to check the result.
2. Use command **netsh int ip reset
**3. Check if there is WLAN Miniport IP in Device Manager. If so, try to uninstall its driver.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Wednesday, July 18, 2018 6:59 AM

Thanks, it's one of the regular solutions, I've already tried. It didn't help

Friday, July 20, 2018 7:53 AM

Hi,

Try this:

1. Open the Control Panel (the traditional one) 
2. Go to "Internet Options" 
3. Go to the "Connections" tab 
4. Select your VPN in the list and click "Settings" 
5. Click "Properties" 
6. Go to the "Security" tab 
7. Select "Allow these protocols" and check the MS-CHAP v2 option

Besides that, please also check if DHCP client service is running fine.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Friday, July 20, 2018 8:41 AM

Thank you for your reply, this steps was performed after vpn connection was created. Still not working.

Monday, July 23, 2018 7:18 PM

Issue solved.  The main reason was one of the incorectly installed update, which cause a lot of failures.

Last update manual reinstall - solved this.

Tuesday, July 24, 2018 8:06 AM

Hi Dobytko,

Thanks for your update and share your solution here. It will be very beneficial to other members who have similar question.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Monday, October 29, 2018 4:53 PM

Try disabling the Microsoft LLDP Protocol Driver by unchecking the box in the properties of the Wi-Fi connection or the Local Area Connection you are using to connect to the Internet.  That immediately worked for me.