locked
Windows (built-in) VPN - can't connect after initial successful connect/disconnect RRS feed

  • Question

  • Hi, 

    I have Windows 10 Home build 10240. Since the beginning of Windows 10 I got the following issue with VPN connection (to my office network). It is PPTP connection with basic settings based on Windows (built-it) setup. My problem is that I can successfully connect to the office VPN only after computer restart. So, it would connect successfully and work fine but if I disconnect from VPN and try to connect again, I would always get error

    Can't connect to xxxxxxxx

    A connection to the remote computer could not be established. You might need to change the network settings for this connection. 

    The only way to make it work again is to restart computer. 

    Any suggestions how to fix that bug?

    Pavel

    Sunday, October 18, 2015 12:30 AM

Answers

  • Hi,

    Some further info. I believe the issue is due to Miniport PPTP adapter not disconnecting from VPN connection correctly. Once I reboot the computer, WAN Miniport (PPTP) adapter is disconnected and I don't see it in ipconfig /all

    After VPN connection is established, I get correct entry in ipconfig /all for that conneciton

    PPP adapter MyVPN:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : MyVPN
       Physical Address. . . . . . . . . :
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : xxx.xxx.xxx.xxx(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.255
       Default Gateway . . . . . . . . . : 0.0.0.0
       DNS Servers . . . . . . . . . . . : xxx.xxx.xxx.xxx
                                           xxx.xxx.xxx.xxx
       NetBIOS over Tcpip. . . . . . . . : Enabled

    After disconnection, the connection was not closed correctly. It remained open with media unoperational status and IP address assigned. Hence, I couldn't connect to VPN again. 

    Now, it seems to be working after I ran netsh to reset ip settings on interfaces. Now, it correctly stops connection. I'll see if it will be permanent fix.


    • Proposed as answer by Michael_LS Tuesday, October 20, 2015 8:28 AM
    • Marked as answer by Pavel Karkarin Friday, October 23, 2015 1:32 AM
    Sunday, October 18, 2015 4:21 AM

All replies

  • Hello,

    Please refer the answer of following thread, see if it helps:

    https://social.technet.microsoft.com/Forums/windows/en-US/ff95ed6e-3246-4daf-9555-a331385ad7b6/windows-vpn-error-720-a-connection-to-the-remote-computer-could-not-be-established?forum=w7itpronetworking

    Hope this helps, Good luck :)

    Windows Troubleshooting & How to guides - http://www.kapilarya.com

    Sunday, October 18, 2015 2:37 AM
  • Thank you for advice but it is not my case unfortunately. 

    I tried to reinstall Miniports, it didn't help. 

    In my case, I am able to establish VPN connection again but only after I do computer reboot. Once connected to VPN, I can use it successfully. Once I disconnect from VPN, I am not able to get connection again until I reboot the laptop. 

    Regards

    Pavel

    Sunday, October 18, 2015 2:51 AM
  • Hi,

    Some further info. I believe the issue is due to Miniport PPTP adapter not disconnecting from VPN connection correctly. Once I reboot the computer, WAN Miniport (PPTP) adapter is disconnected and I don't see it in ipconfig /all

    After VPN connection is established, I get correct entry in ipconfig /all for that conneciton

    PPP adapter MyVPN:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : MyVPN
       Physical Address. . . . . . . . . :
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : xxx.xxx.xxx.xxx(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.255
       Default Gateway . . . . . . . . . : 0.0.0.0
       DNS Servers . . . . . . . . . . . : xxx.xxx.xxx.xxx
                                           xxx.xxx.xxx.xxx
       NetBIOS over Tcpip. . . . . . . . : Enabled

    After disconnection, the connection was not closed correctly. It remained open with media unoperational status and IP address assigned. Hence, I couldn't connect to VPN again. 

    Now, it seems to be working after I ran netsh to reset ip settings on interfaces. Now, it correctly stops connection. I'll see if it will be permanent fix.


    • Proposed as answer by Michael_LS Tuesday, October 20, 2015 8:28 AM
    • Marked as answer by Pavel Karkarin Friday, October 23, 2015 1:32 AM
    Sunday, October 18, 2015 4:21 AM
  • Hi Pavel,

    Thanks for your sharing and update.

    If any further issues, please feel free to post back.

    Regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, October 20, 2015 9:15 AM
  • I am experiencing the same issue. A reboot clears it. Any tips?
    Friday, April 1, 2016 6:43 PM
  • Hi John,

    Not sure if you will find my experience of any use. As I found, it was due to Miniport PPTP adapter not disconnecting from VPN connection correctly. I did resolve the issue by running netcfg -d but it is only half of issue. 

    Due to my work I need to use Cisco VPN 5.0.07.0440 which surely doesn't work right in Windows 10. So, I had to install SonicWall Global VPN Client before running Cisco VPN msi to get it done. Well, that didn't work right with my Microsoft VPN configuration and I was always getting the described issue. As soon as  I got rid of Cisco VPN and SonicWall VPN, Microsoft VPN configuration started working very well. Now, I don't see the issue at all.

    Pavel

    Monday, April 4, 2016 5:13 AM
  • Hey,


    I have the same issue with Windows 10 Pro all updates.
    The trick with NETSH INT IP RESET didn't work to me either (or I hope to work after that restart at least...)

    Any more ideas/fixes? Since this is really annoying in working environment when you don't want to restart your PC.

    Other than that Pavel is right - if you go to the interfaces you will see its in disconnecting state and never disconnect... https://i.gyazo.com/7d6db17a19df9bb7313ad40fda05a567.png

    Reminds me the issue where you can't  no longer type program name from windows key menu and need to kill Search.exe

    Tuesday, August 23, 2016 2:03 PM
  • I've been banging my 'ead against the wall for months with this exact same issue.  I tried everything in this forum as well as scoured the internet for answers to no avail.  I internally blamed it on Microsoft, but I was wrong :)

    I connect to multiple VPNs throughout the day and this was quite annoying to say the least.  

    In my case, I found a Sonicwall Netextender program was launching at start up.   Disabling this solved the issue for me.   You may want to check your startup programs to see if there is another VPN service conflicting.  

    Hope this helps someone else in the world from banging their 'eads against the wall!

    Saturday, March 17, 2018 8:02 AM
  • I too had this problem, Still do but found a much simpler way after many days of research and never finding an answer.  Try creating a batch file using Rasdial.exe, So the script would look something to the looks of this:

    Rasdial.exe "MY VPN" "USERNAME" "PASSWORD"

    (Keep the quotes)

    Where "MY VPN" is the name of your VPN Connection

    "USERNAME" is the username you use for your connection

    "PASSWORD" is the password you use for the connection

    After I ran this command in CMD i had my vpn fire up in a matter of seconds. Next to test this, I wrote the batch file and disconected. Attempted to re-connect again using the normal way through windows. Same problem. Ran my batch file and it fired right up. Hate the problem but the solution is good enough to call a fix in my opinion. 

    Hope this helps someone else that is banging their head against the wall with this problem.

    Saturday, April 7, 2018 6:25 AM
  • Fantastic! I had to do something like this on Win7, but was "fooled" by the Win 10 UI "nicety". It's worth mentioning that "PASSWORD" isn't required in my case (my connection has "Remember credentials" checked).
    Wednesday, May 23, 2018 8:50 PM
  • Had the same problem and this worked for me. Really wish someone knew why it's broken on the gui only.
    Friday, March 8, 2019 4:38 PM
  • I realy struggle to understand MS .. its 2 ways VPN connection approach ...

    but I have found out that once this situation occurs it is still possible to connect going to Settings > Network  > VPN or using Windows key + A > VPN 



    Tuesday, June 18, 2019 1:23 PM
  • Can you share what netsh commands you issued?  Also, any follow-up on if the fix was permanent?  I am having the same issue on Win 10 latest build.

    - Jay

    Friday, November 15, 2019 7:39 PM