Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, July 9, 2018 3:24 PM
I'm having a problem with a Windows 10 workstation. We setup a VPN which is used sometimes. Before the VPN has been connected, everything is fine. After the VPN is connected, everything properly routes thru the VPN. If I disconnect the VPN shortly after connecting it (like, a couple of minutes), we are back to the local network and everything is working fine. However, if I disconnect the VPN (or if it disconnects due to a brief network outage) after it has been in use a while (sometimes as short as 30 minutes), I'm not able to get out of the local network. I can still connect to the router, but any ping or access outside the network doesn't work.
I think this is possibly due to the routing table not being properly restored. I can do a Route /f to clear the routing table and then an ipconfig /release and an ipconfig /renew, and the networking comes back. Sometimes, I can do a route add 192.168.0.0 to connect the router again, and it works. Sometimes, it doesn't show that route in the active routes, but it says the route already exists if I try to add it again.
Anyone have any ideas of why this is happening, and how to correct it permanently? Is this normal for disconnecting a VPN?
Thank you.
Jeremy Heymann
Jeremy Heymann Market Mentor Online
All replies (8)
Tuesday, July 10, 2018 3:15 AM
Hi,
Based on your description, I found an article may relate to your problem, please refer to the link:
You Cannot Connect to the Internet After You Connect to a VPN Server
In addition, I also found a similar case may give you some points, please refer to the link:
Internet Unavailable after VPN disconnects, giving Ping response of No Resources
Hope they can help you.
Best Regards,
Tao
Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, July 10, 2018 3:23 AM
Thank you for your reply. Unfortunately, the first link describes a problem that occurs while the VPN is connected, which isn't my case. And, the second link is actually my post of the same issue in a different forum.
Please let me know if you have any other thoughts.
Jeremy Heymann Market Mentor Online
Friday, May 17, 2019 2:36 PM
I found a work around, of sorts.
It looks like the problem is in the routing table. The VPN changes the general route, so everything goes to the VPN, and doesn’t seem to restore it properly (sometimes). I made myself a command file which removes the route and adds it back correctly. This works most of the time, but for some reason, the interface number sometimes changes.
In a command window, do a ROUTE PRINT. Examine the Interface list, and find the number for your network adapter. Mine is currently 18, but it seems to sometimes change to 17 or 16 or 19. Next, examine the IPV4 Route Table and look for the entry for 0.0.0.0. this seems to be the generic route (ie, anything that we don’t have a better route for just goes to the router). Note the gateway address and the interface metric.
I created a command file as follows:
route delete 0.0.0.0
route add 0.0.0.0 mask 0.0.0.0 192.168.0.1 metric 40 if 18
pause Press any key to continue...
Substitute your gateway address for 192.168.0.1, your metric for the 40, and your interface number for the 18.
See if this works.
I don’t know why this route isn’t properly reestablished when the vpn is disconnected. In my case, it is intermittent. I also don’t know why the interface number sometimes changes, so I have to edit the command file.
When the problem occurs, I have a shortcut to the command file on my desktop. I right-click, and choose Run As Administrator (it needs admin privs), and if the interface hasn’t changed, it restores proper network function.
Jeremy Heymann Market Mentor Online
Saturday, January 25, 2020 10:23 PM
I'm having the same problem. Your bat file works but to get around the interface number you can use a PowerShell Script instead or just do 3 things you described with your first post.
I still don't know why this is happening. I have one of my VPN profiles setup as split tunnel and added some persistence routes to Windows Routing table. Before that I had no problem. Now I can't go back no matter what I try.
Do you have a split tunnel vpn too?
Tuesday, January 28, 2020 3:34 PM
ISSUE:
Hi there again,
I investigated the issue more on my spare time and I found couple of things, hope these findings can help experts crack this issue open. But before that, let me explain my setup so we don't miss anything.
I have couple of PPTP Windows 10 Built-in VPN profiles. One of them is setup to be split tunnel. As described in the first post, before we connect to VPNs everything is fine. After we connect to VPNs everything is fine. But after we disconnect from VPNs, we lose connectivity to the Internet. Local network works fine. It has something to do with the default route not working properly.
Now I have find out that;
- The issue only appears after disconnecting from normal VPN profiles NOT the split one.
- At least in my case, removing the split tunnel profile and resetting the network from Windows 10 Network settings section, fixes the problem permanently.
- It's not an static routes issue. Because clearing the routing table using "route /f" doesn't help.
- It's not a metric issue. I have tested every possible configuration on adapters and routes. No configuration fixed the issue.
- There is no visible difference between the working default route and not working one. I have checked CMD and Powershell information for this.
Given this information I believe that There is an underlying bug in how Windows 10 handles split tunnel routing.
Solution:
For those users who reach this page for similar problem, whom what @Jeremy Heymann suggested as a workaround did not worked for them:
- If you are OK with an extra step and want to keep the split tunnel profile, try disabling and re-enabling your network adapter after you disconnect. You can do this through the left click pop-up menu on the adapter icon in this address:
Settings > Network & Internet > Change Adapter Options (Under "Change your network settings" section)
You have to do this every time you lose Internet access.
- If you need a permanent fix without doing a Windows 10 Fresh Install, follow these steps:
- Open a CMD with administrative privileges and type this command to remove any static routes from Windows 10 routing table:
route /f - Remove your split tunnel VPN profile.
- Reset your network:
Settings > Network & Internet > Reset Network (Blue link at the end of the page)
Final words:
Can we get some expert opinions on this?
Do we need to post this on another forum?
Is there any good fixes for this?
Wednesday, January 29, 2020 3:05 PM
My specific issue was fixed by the VPN provider I am using. Thanks for the response.
Jeremy Heymann Market Mentor Online
Monday, March 9, 2020 6:20 AM
Appreciate the greatpost rahmat, Some colleagues are facing an identical issue, let’s hope it gets fixed
Thursday, March 26, 2020 9:57 PM
I have had this issue for a while. My fix is to disable the NIC and the re-enable it again, this always fixes it. Happens to both Palo Alto Global Protect VPN as well as Private Internet Access VPN.
Would be good if this got fixed, its pretty annoying