
Can I test the VPN gateway over the public internet without going through the tunnel?
Yes — and that is a useful step. SSTP uses TCP 443; IKEv2 typically uses UDP 500 and UDP 4500 with NAT traversal. Confirm the gateway hostname is reachable on those ports and resolves to the IP your IT group gave you before the VPN profile is connected. If you can’t reach the gateway at all, the drop isn’t a Windows client problem.
Why does the VPN stay up on another laptop but not on mine?
That is comparison evidence pointing at your device, its profile, its adapter, or its update state. Check that you and the other laptop are connecting to the same gateway with the same protocol, and verify your Windows 11 build matches. If yours is a managed device, ask IT whether your device has the same Always On VPN profile payload as the working one.[2]
Can I test the VPN gateway over the public internet without going through the tunnel?
Yes — and that is a useful step. SSTP uses TCP 443; IKEv2 typically uses UDP 500 and UDP 4500 with NAT traversal. Confirm the gateway hostname is reachable on those ports and resolves to the IP your IT group gave you before the VPN profile is connected. If you can’t reach the gateway at all, the drop isn’t a Windows client problem.
Related guides from The IT Guys
- Remote Access Broke After a Router Upgrade? Check Double NAT and CGNAT — use this when the failure is on the carrier or router side rather than the Windows client.
- Is Remote Desktop Open to the Internet? Close Port 3389 and Use an Approved Remote-Access Plan — use this when Remote Desktop and VPN together are the workflow.
- Connected but No Internet? A 169.254 Address Points to DHCP, Not a Broken NIC — use this when the VPN works, but only certain name lookups fail.
- Weak Cell Signal Indoors? Set Up Wi-Fi Calling — and Fix the 911 Address — use this when the laptop loses both Wi-Fi and the cellular fallback.
Your next action
Capture the exact VPN error and timestamp. Open Event Viewer and read RasClient and RasMan. Run the Network Adapter troubleshooter. If this is a managed work device and the troubleshooter, log review, and adapter power settings don’t identify the cause, contact The IT Guys with the error, the KB number of the most recent cumulative update, and an export of the two logs — never send us a password, certificate, or session key.
Sources
- Microsoft Learn: About Always On VPN for Windows Server Remote Access — accessed October 21, 2026.
- Microsoft Learn: Tutorial — Create Always On VPN Connection on Windows Client Devices — accessed October 21, 2026.
- Microsoft Learn: VPN authentication options in Windows — accessed October 21, 2026.
- Microsoft Learn: Troubleshoot L2TP/IPSec VPN client connection (KB 325034) — last updated February 12, 2026.
- Microsoft Learn Q&A: Always On VPN disconnections — RasClient and RasMan event-log pointers — accessed October 21, 2026.
- Microsoft Learn Q&A: Persistent network connection drops in Windows 11 — accessed October 21, 2026.
- CISA + NSA: Selecting and Hardening Remote Access VPN Solutions — accessed October 21, 2026.
- Microsoft Learn: VPN connection types (IKEv2/L2TP/PPTP/SSTP/Automatic) — accessed October 21, 2026.
- Microsoft Support: Connect to a VPN in Windows — applies to Windows 10 and Windows 11, accessed October 21, 2026.
Will running Network reset fix the VPN?
Sometimes, but at a high cost. Microsoft Q&A respondents and Microsoft’s own network-reset page treat it as a last-step option because it removes installed adapters and their settings, then reinstalls them with defaults — VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] Run the troubleshooters and read the logs first; only invoke Network reset on a device you own end-to-end.
Why does the VPN stay up on another laptop but not on mine?
That is comparison evidence pointing at your device, its profile, its adapter, or its update state. Check that you and the other laptop are connecting to the same gateway with the same protocol, and verify your Windows 11 build matches. If yours is a managed device, ask IT whether your device has the same Always On VPN profile payload as the working one.[2]
Can I test the VPN gateway over the public internet without going through the tunnel?
Yes — and that is a useful step. SSTP uses TCP 443; IKEv2 typically uses UDP 500 and UDP 4500 with NAT traversal. Confirm the gateway hostname is reachable on those ports and resolves to the IP your IT group gave you before the VPN profile is connected. If you can’t reach the gateway at all, the drop isn’t a Windows client problem.
Related guides from The IT Guys
- Remote Access Broke After a Router Upgrade? Check Double NAT and CGNAT — use this when the failure is on the carrier or router side rather than the Windows client.
- Is Remote Desktop Open to the Internet? Close Port 3389 and Use an Approved Remote-Access Plan — use this when Remote Desktop and VPN together are the workflow.
- Connected but No Internet? A 169.254 Address Points to DHCP, Not a Broken NIC — use this when the VPN works, but only certain name lookups fail.
- Weak Cell Signal Indoors? Set Up Wi-Fi Calling — and Fix the 911 Address — use this when the laptop loses both Wi-Fi and the cellular fallback.
Your next action
Capture the exact VPN error and timestamp. Open Event Viewer and read RasClient and RasMan. Run the Network Adapter troubleshooter. If this is a managed work device and the troubleshooter, log review, and adapter power settings don’t identify the cause, contact The IT Guys with the error, the KB number of the most recent cumulative update, and an export of the two logs — never send us a password, certificate, or session key.
Sources
- Microsoft Learn: About Always On VPN for Windows Server Remote Access — accessed October 21, 2026.
- Microsoft Learn: Tutorial — Create Always On VPN Connection on Windows Client Devices — accessed October 21, 2026.
- Microsoft Learn: VPN authentication options in Windows — accessed October 21, 2026.
- Microsoft Learn: Troubleshoot L2TP/IPSec VPN client connection (KB 325034) — last updated February 12, 2026.
- Microsoft Learn Q&A: Always On VPN disconnections — RasClient and RasMan event-log pointers — accessed October 21, 2026.
- Microsoft Learn Q&A: Persistent network connection drops in Windows 11 — accessed October 21, 2026.
- CISA + NSA: Selecting and Hardening Remote Access VPN Solutions — accessed October 21, 2026.
- Microsoft Learn: VPN connection types (IKEv2/L2TP/PPTP/SSTP/Automatic) — accessed October 21, 2026.
- Microsoft Support: Connect to a VPN in Windows — applies to Windows 10 and Windows 11, accessed October 21, 2026.
Should I switch to PPTP because it’s the only option that “just works”?
No. Microsoft lists PPTP as one of the four built-in protocols but CISA and NSA’s hardening guidance explicitly recommends against relying on PPTP because of well-known weaknesses.[8][7] Ask your IT owner for IKEv2 or SSTP — those are the modern options.
Will running Network reset fix the VPN?
Sometimes, but at a high cost. Microsoft Q&A respondents and Microsoft’s own network-reset page treat it as a last-step option because it removes installed adapters and their settings, then reinstalls them with defaults — VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] Run the troubleshooters and read the logs first; only invoke Network reset on a device you own end-to-end.
Why does the VPN stay up on another laptop but not on mine?
That is comparison evidence pointing at your device, its profile, its adapter, or its update state. Check that you and the other laptop are connecting to the same gateway with the same protocol, and verify your Windows 11 build matches. If yours is a managed device, ask IT whether your device has the same Always On VPN profile payload as the working one.[2]
Can I test the VPN gateway over the public internet without going through the tunnel?
Yes — and that is a useful step. SSTP uses TCP 443; IKEv2 typically uses UDP 500 and UDP 4500 with NAT traversal. Confirm the gateway hostname is reachable on those ports and resolves to the IP your IT group gave you before the VPN profile is connected. If you can’t reach the gateway at all, the drop isn’t a Windows client problem.
Related guides from The IT Guys
- Remote Access Broke After a Router Upgrade? Check Double NAT and CGNAT — use this when the failure is on the carrier or router side rather than the Windows client.
- Is Remote Desktop Open to the Internet? Close Port 3389 and Use an Approved Remote-Access Plan — use this when Remote Desktop and VPN together are the workflow.
- Connected but No Internet? A 169.254 Address Points to DHCP, Not a Broken NIC — use this when the VPN works, but only certain name lookups fail.
- Weak Cell Signal Indoors? Set Up Wi-Fi Calling — and Fix the 911 Address — use this when the laptop loses both Wi-Fi and the cellular fallback.
Your next action
Capture the exact VPN error and timestamp. Open Event Viewer and read RasClient and RasMan. Run the Network Adapter troubleshooter. If this is a managed work device and the troubleshooter, log review, and adapter power settings don’t identify the cause, contact The IT Guys with the error, the KB number of the most recent cumulative update, and an export of the two logs — never send us a password, certificate, or session key.
Sources
- Microsoft Learn: About Always On VPN for Windows Server Remote Access — accessed October 21, 2026.
- Microsoft Learn: Tutorial — Create Always On VPN Connection on Windows Client Devices — accessed October 21, 2026.
- Microsoft Learn: VPN authentication options in Windows — accessed October 21, 2026.
- Microsoft Learn: Troubleshoot L2TP/IPSec VPN client connection (KB 325034) — last updated February 12, 2026.
- Microsoft Learn Q&A: Always On VPN disconnections — RasClient and RasMan event-log pointers — accessed October 21, 2026.
- Microsoft Learn Q&A: Persistent network connection drops in Windows 11 — accessed October 21, 2026.
- CISA + NSA: Selecting and Hardening Remote Access VPN Solutions — accessed October 21, 2026.
- Microsoft Learn: VPN connection types (IKEv2/L2TP/PPTP/SSTP/Automatic) — accessed October 21, 2026.
- Microsoft Support: Connect to a VPN in Windows — applies to Windows 10 and Windows 11, accessed October 21, 2026.
Does a “Connected” indicator mean the tunnel is actually working?
Not always. Microsoft documents that Always On VPN connectivity features — trusted network detection, name-based triggering, and name resolution via the Name Resolution Policy Table — can succeed while the authentication step later fails.[1] Confirm with one named resource behind the VPN, not by the tray icon.
Should I switch to PPTP because it’s the only option that “just works”?
No. Microsoft lists PPTP as one of the four built-in protocols but CISA and NSA’s hardening guidance explicitly recommends against relying on PPTP because of well-known weaknesses.[8][7] Ask your IT owner for IKEv2 or SSTP — those are the modern options.
Will running Network reset fix the VPN?
Sometimes, but at a high cost. Microsoft Q&A respondents and Microsoft’s own network-reset page treat it as a last-step option because it removes installed adapters and their settings, then reinstalls them with defaults — VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] Run the troubleshooters and read the logs first; only invoke Network reset on a device you own end-to-end.
Why does the VPN stay up on another laptop but not on mine?
That is comparison evidence pointing at your device, its profile, its adapter, or its update state. Check that you and the other laptop are connecting to the same gateway with the same protocol, and verify your Windows 11 build matches. If yours is a managed device, ask IT whether your device has the same Always On VPN profile payload as the working one.[2]
Can I test the VPN gateway over the public internet without going through the tunnel?
Yes — and that is a useful step. SSTP uses TCP 443; IKEv2 typically uses UDP 500 and UDP 4500 with NAT traversal. Confirm the gateway hostname is reachable on those ports and resolves to the IP your IT group gave you before the VPN profile is connected. If you can’t reach the gateway at all, the drop isn’t a Windows client problem.
Related guides from The IT Guys
- Remote Access Broke After a Router Upgrade? Check Double NAT and CGNAT — use this when the failure is on the carrier or router side rather than the Windows client.
- Is Remote Desktop Open to the Internet? Close Port 3389 and Use an Approved Remote-Access Plan — use this when Remote Desktop and VPN together are the workflow.
- Connected but No Internet? A 169.254 Address Points to DHCP, Not a Broken NIC — use this when the VPN works, but only certain name lookups fail.
- Weak Cell Signal Indoors? Set Up Wi-Fi Calling — and Fix the 911 Address — use this when the laptop loses both Wi-Fi and the cellular fallback.
Your next action
Capture the exact VPN error and timestamp. Open Event Viewer and read RasClient and RasMan. Run the Network Adapter troubleshooter. If this is a managed work device and the troubleshooter, log review, and adapter power settings don’t identify the cause, contact The IT Guys with the error, the KB number of the most recent cumulative update, and an export of the two logs — never send us a password, certificate, or session key.
Sources
- Microsoft Learn: About Always On VPN for Windows Server Remote Access — accessed October 21, 2026.
- Microsoft Learn: Tutorial — Create Always On VPN Connection on Windows Client Devices — accessed October 21, 2026.
- Microsoft Learn: VPN authentication options in Windows — accessed October 21, 2026.
- Microsoft Learn: Troubleshoot L2TP/IPSec VPN client connection (KB 325034) — last updated February 12, 2026.
- Microsoft Learn Q&A: Always On VPN disconnections — RasClient and RasMan event-log pointers — accessed October 21, 2026.
- Microsoft Learn Q&A: Persistent network connection drops in Windows 11 — accessed October 21, 2026.
- CISA + NSA: Selecting and Hardening Remote Access VPN Solutions — accessed October 21, 2026.
- Microsoft Learn: VPN connection types (IKEv2/L2TP/PPTP/SSTP/Automatic) — accessed October 21, 2026.
- Microsoft Support: Connect to a VPN in Windows — applies to Windows 10 and Windows 11, accessed October 21, 2026.
Good
- Record the exact error and timestamp before changing anything.
- Read RasClient and RasMan Event Viewer logs.
- Run Network Adapter and Internet Connections troubleshooters first.
- Test the same credentials from a second network (wired Ethernet or phone hotspot).
- Disable Wi-Fi power-saving on the wireless adapter.
- Ask IT to roll the tunnel to IKEv2 if the gateway supports it.
- Plan a migration away from PPTP — CISA and NSA both recommend against it.[7]
Bad
- Run Network reset on a managed work device without coordinating with IT.
- Uninstall a vendor VPN client on a managed device.
- Open TCP 443 or UDP 500/4500 on the home router “so the VPN can get through.”
- Edit the
AssumeUDPEncapsulationContextOnSendRuleregistry on a work laptop without documentation. - Type VPN credentials into a chat, screenshot, or email.
- Disable the firewall or antivirus “to see if that’s the problem.”
- Assume the VPN is broken because the Wi-Fi is bad.
Two realistic examples
Harmless misalignment: Wi-Fi power-save killing the tunnel
Illustrative example: A remote worker says the VPN drops every 20 to 40 minutes, only on the home Wi-Fi. The Event Viewer logs show repeated Remote Access Connection Manager events flagged as link state changes. The wireline adapter is fine; the Wi-Fi adapter was set to Power Saving Mode on the Balanced plan. Changing the adapter power setting to Maximum Performance on the home and current power plans keeps the tunnel stable for the full work day. The VPN client was never the problem.
Costly wrong turn: Network reset on a managed work device
Illustrative caution: A managed Windows 11 device has an Always On VPN profile delivered by Intune and a third-party EDR client. The user runs Settings → Network & internet → Advanced network settings → Network reset “to fix the VPN.” Network reset removes and reinstalls every network adapter and resets every network setting — including the Always On VPN tunnel and any third-party VPN client. Microsoft’s troubleshooting guidance explicitly warns that VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] The user now has a worse problem, and IT has to reissue the profile. Coordinate first.
Frequently asked questions
Does a “Connected” indicator mean the tunnel is actually working?
Not always. Microsoft documents that Always On VPN connectivity features — trusted network detection, name-based triggering, and name resolution via the Name Resolution Policy Table — can succeed while the authentication step later fails.[1] Confirm with one named resource behind the VPN, not by the tray icon.
Should I switch to PPTP because it’s the only option that “just works”?
No. Microsoft lists PPTP as one of the four built-in protocols but CISA and NSA’s hardening guidance explicitly recommends against relying on PPTP because of well-known weaknesses.[8][7] Ask your IT owner for IKEv2 or SSTP — those are the modern options.
Will running Network reset fix the VPN?
Sometimes, but at a high cost. Microsoft Q&A respondents and Microsoft’s own network-reset page treat it as a last-step option because it removes installed adapters and their settings, then reinstalls them with defaults — VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] Run the troubleshooters and read the logs first; only invoke Network reset on a device you own end-to-end.
Why does the VPN stay up on another laptop but not on mine?
That is comparison evidence pointing at your device, its profile, its adapter, or its update state. Check that you and the other laptop are connecting to the same gateway with the same protocol, and verify your Windows 11 build matches. If yours is a managed device, ask IT whether your device has the same Always On VPN profile payload as the working one.[2]
Can I test the VPN gateway over the public internet without going through the tunnel?
Yes — and that is a useful step. SSTP uses TCP 443; IKEv2 typically uses UDP 500 and UDP 4500 with NAT traversal. Confirm the gateway hostname is reachable on those ports and resolves to the IP your IT group gave you before the VPN profile is connected. If you can’t reach the gateway at all, the drop isn’t a Windows client problem.
Related guides from The IT Guys
- Remote Access Broke After a Router Upgrade? Check Double NAT and CGNAT — use this when the failure is on the carrier or router side rather than the Windows client.
- Is Remote Desktop Open to the Internet? Close Port 3389 and Use an Approved Remote-Access Plan — use this when Remote Desktop and VPN together are the workflow.
- Connected but No Internet? A 169.254 Address Points to DHCP, Not a Broken NIC — use this when the VPN works, but only certain name lookups fail.
- Weak Cell Signal Indoors? Set Up Wi-Fi Calling — and Fix the 911 Address — use this when the laptop loses both Wi-Fi and the cellular fallback.
Your next action
Capture the exact VPN error and timestamp. Open Event Viewer and read RasClient and RasMan. Run the Network Adapter troubleshooter. If this is a managed work device and the troubleshooter, log review, and adapter power settings don’t identify the cause, contact The IT Guys with the error, the KB number of the most recent cumulative update, and an export of the two logs — never send us a password, certificate, or session key.
Sources
- Microsoft Learn: About Always On VPN for Windows Server Remote Access — accessed October 21, 2026.
- Microsoft Learn: Tutorial — Create Always On VPN Connection on Windows Client Devices — accessed October 21, 2026.
- Microsoft Learn: VPN authentication options in Windows — accessed October 21, 2026.
- Microsoft Learn: Troubleshoot L2TP/IPSec VPN client connection (KB 325034) — last updated February 12, 2026.
- Microsoft Learn Q&A: Always On VPN disconnections — RasClient and RasMan event-log pointers — accessed October 21, 2026.
- Microsoft Learn Q&A: Persistent network connection drops in Windows 11 — accessed October 21, 2026.
- CISA + NSA: Selecting and Hardening Remote Access VPN Solutions — accessed October 21, 2026.
- Microsoft Learn: VPN connection types (IKEv2/L2TP/PPTP/SSTP/Automatic) — accessed October 21, 2026.
- Microsoft Support: Connect to a VPN in Windows — applies to Windows 10 and Windows 11, accessed October 21, 2026.
Good
- Record the exact error and timestamp before changing anything.
- Read RasClient and RasMan Event Viewer logs.
- Run Network Adapter and Internet Connections troubleshooters first.
- Test the same credentials from a second network (wired Ethernet or phone hotspot).
- Disable Wi-Fi power-saving on the wireless adapter.
- Ask IT to roll the tunnel to IKEv2 if the gateway supports it.
- Plan a migration away from PPTP — CISA and NSA both recommend against it.[7]
Bad
- Run Network reset on a managed work device without coordinating with IT.
- Uninstall a vendor VPN client on a managed device.
- Open TCP 443 or UDP 500/4500 on the home router “so the VPN can get through.”
- Edit the
AssumeUDPEncapsulationContextOnSendRuleregistry on a work laptop without documentation. - Type VPN credentials into a chat, screenshot, or email.
- Disable the firewall or antivirus “to see if that’s the problem.”
- Assume the VPN is broken because the Wi-Fi is bad.
Two realistic examples
Harmless misalignment: Wi-Fi power-save killing the tunnel
Illustrative example: A remote worker says the VPN drops every 20 to 40 minutes, only on the home Wi-Fi. The Event Viewer logs show repeated Remote Access Connection Manager events flagged as link state changes. The wireline adapter is fine; the Wi-Fi adapter was set to Power Saving Mode on the Balanced plan. Changing the adapter power setting to Maximum Performance on the home and current power plans keeps the tunnel stable for the full work day. The VPN client was never the problem.
Costly wrong turn: Network reset on a managed work device
Illustrative caution: A managed Windows 11 device has an Always On VPN profile delivered by Intune and a third-party EDR client. The user runs Settings → Network & internet → Advanced network settings → Network reset “to fix the VPN.” Network reset removes and reinstalls every network adapter and resets every network setting — including the Always On VPN tunnel and any third-party VPN client. Microsoft’s troubleshooting guidance explicitly warns that VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] The user now has a worse problem, and IT has to reissue the profile. Coordinate first.
Frequently asked questions
Does a “Connected” indicator mean the tunnel is actually working?
Not always. Microsoft documents that Always On VPN connectivity features — trusted network detection, name-based triggering, and name resolution via the Name Resolution Policy Table — can succeed while the authentication step later fails.[1] Confirm with one named resource behind the VPN, not by the tray icon.
Should I switch to PPTP because it’s the only option that “just works”?
No. Microsoft lists PPTP as one of the four built-in protocols but CISA and NSA’s hardening guidance explicitly recommends against relying on PPTP because of well-known weaknesses.[8][7] Ask your IT owner for IKEv2 or SSTP — those are the modern options.
Will running Network reset fix the VPN?
Sometimes, but at a high cost. Microsoft Q&A respondents and Microsoft’s own network-reset page treat it as a last-step option because it removes installed adapters and their settings, then reinstalls them with defaults — VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] Run the troubleshooters and read the logs first; only invoke Network reset on a device you own end-to-end.
Why does the VPN stay up on another laptop but not on mine?
That is comparison evidence pointing at your device, its profile, its adapter, or its update state. Check that you and the other laptop are connecting to the same gateway with the same protocol, and verify your Windows 11 build matches. If yours is a managed device, ask IT whether your device has the same Always On VPN profile payload as the working one.[2]
Can I test the VPN gateway over the public internet without going through the tunnel?
Yes — and that is a useful step. SSTP uses TCP 443; IKEv2 typically uses UDP 500 and UDP 4500 with NAT traversal. Confirm the gateway hostname is reachable on those ports and resolves to the IP your IT group gave you before the VPN profile is connected. If you can’t reach the gateway at all, the drop isn’t a Windows client problem.
Related guides from The IT Guys
- Remote Access Broke After a Router Upgrade? Check Double NAT and CGNAT — use this when the failure is on the carrier or router side rather than the Windows client.
- Is Remote Desktop Open to the Internet? Close Port 3389 and Use an Approved Remote-Access Plan — use this when Remote Desktop and VPN together are the workflow.
- Connected but No Internet? A 169.254 Address Points to DHCP, Not a Broken NIC — use this when the VPN works, but only certain name lookups fail.
- Weak Cell Signal Indoors? Set Up Wi-Fi Calling — and Fix the 911 Address — use this when the laptop loses both Wi-Fi and the cellular fallback.
Your next action
Capture the exact VPN error and timestamp. Open Event Viewer and read RasClient and RasMan. Run the Network Adapter troubleshooter. If this is a managed work device and the troubleshooter, log review, and adapter power settings don’t identify the cause, contact The IT Guys with the error, the KB number of the most recent cumulative update, and an export of the two logs — never send us a password, certificate, or session key.
Sources
- Microsoft Learn: About Always On VPN for Windows Server Remote Access — accessed October 21, 2026.
- Microsoft Learn: Tutorial — Create Always On VPN Connection on Windows Client Devices — accessed October 21, 2026.
- Microsoft Learn: VPN authentication options in Windows — accessed October 21, 2026.
- Microsoft Learn: Troubleshoot L2TP/IPSec VPN client connection (KB 325034) — last updated February 12, 2026.
- Microsoft Learn Q&A: Always On VPN disconnections — RasClient and RasMan event-log pointers — accessed October 21, 2026.
- Microsoft Learn Q&A: Persistent network connection drops in Windows 11 — accessed October 21, 2026.
- CISA + NSA: Selecting and Hardening Remote Access VPN Solutions — accessed October 21, 2026.
- Microsoft Learn: VPN connection types (IKEv2/L2TP/PPTP/SSTP/Automatic) — accessed October 21, 2026.
- Microsoft Support: Connect to a VPN in Windows — applies to Windows 10 and Windows 11, accessed October 21, 2026.
Treat as in scope
- Any built-in VPN profile listed under Settings → Network & internet → VPN.
- Any vendor VPN client that came from the Microsoft Store, your employer, or an IT-pushed application.[9]
- Always On VPN user tunnels and device tunnels deployed by Intune, Configuration Manager, or PowerShell.[2]
- Built-in tunneling protocols IKEv2, L2TP/IPSec, SSTP, and PPTP.[8]
- Connections that drop after sleep, after switching between Wi-Fi and Ethernet, after a recent cumulative update, or after a long idle period.[5]
Not automatically a VPN problem
- A flaky public Wi-Fi network that is dropping everything, not just the tunnel.
- An outage on the VPN gateway or corporate firewall itself.
- A captive portal (hotel, café, airport) you haven’t signed into.
- A sleep/hibernate issue, lid-close issue, or power-policy issue that happens to wake up the laptop.
- A certificate that expired on the gateway side, not on your laptop.[7]
Step-by-step: narrow down the cause before changing anything
1. Capture the exact symptom and timing
Practical evidence-preservation guidance: Write down the date, time, Wi-Fi network, what you clicked, the connection entry name, and the precise wording of any error. A message like “The VPN connection failed” or “A connection to the remote computer could not be established” is diagnostic gold for whoever has to fix it. Screenshots or photos of the dialog are acceptable; passwords, certificates, and session keys are not.
Practical platform note: Microsoft Support’s user-facing VPN guide says you can connect or disconnect from the VPN quick setting on the taskbar, and that any sign-in prompt that appears is the gateway’s authentication dialog — not Windows itself.[9] If you suspect a credential issue, the safest first move is to confirm the password still works in the IT-managed webmail or password-reset portal before touching the VPN client.
2. Open the two Event Viewer logs that matter
Microsoft Q&A moderators recommend the same two logs for Always On VPN disconnects: Applications and Services Logs → Microsoft → Windows → RasClient and RasMan. The RasClient log is for client-side events (dial attempts, credential prompts, user actions); the RasMan log is for the Remote Access Connection Manager service that owns the connection.[5]
- Open Event Viewer from the Start menu (run as administrator if you can).
- Expand Applications and Services Logs, then Microsoft, then Windows.
- Click RasClient in the left pane, then click Filter Current Log… on the right and choose Last hour or Last 24 hours, with Critical, Error, and Warning levels checked.
- Repeat for RasMan.
- Look for repeating entries with the same Event ID — that is the diagnostic signature. Common IDs include 20222 (IKE authentication credentials are unacceptable), 20224 (IKE failed to find a valid machine certificate), and Event 4-class messages in RasMan about a connection terminated.
Practical scope guidance: Don’t mail the logs straight to IT. Export them as .evtx from Event Viewer only when the IT owner asks for them; the logs can include host names and timestamps but should not include credentials or session keys at the level of information shown in the user-facing filters.[5]
3. Run the built-in Network troubleshooter first
Before you change anything, run the troubleshooter Microsoft already ships with Windows 11. Microsoft Q&A guidance lists Network Adapter and Internet Connections as the right troubleshooters, and recommends them over a Network reset whenever a connection drops but does not fail outright.[6]
- Open Start → Settings → System → Troubleshoot → Other troubleshooters.
- Run Network Adapter first. If it identifies an adapter-level issue, follow its one recommended fix.
- Run Internet Connections second to verify that the laptop still has working internet in general.
- If the troubleshooter reports “Troubleshooting couldn’t identify the problem,” that is not a clean bill of health — it just means it didn’t have a preset fix. Continue with the Event Viewer evidence.[6]
4. Reconnect once from a known-good network
Practical isolation guidance: Test the VPN from a wired Ethernet connection if you can — Microsoft Q&A respondents specifically recommend this to separate “wired-only, wireless-only, or both” failure modes for persistent drops.[6] If wired works but wireless drops, the cause is Wi-Fi roaming or a weak signal — not the VPN client.
- Disable VPN split tunneling if the IT profile enables it, then reconnect — a poorly framed split-tunnel policy can break name resolution while leaving the tunnel up.[1]
- If you connect from home, also try a phone hotspot for one connection test — that cleanly separates the Wi-Fi network from the laptop’s wireless adapter.
- Move closer to the Wi-Fi access point or restart the access point itself; intermittent wireless can show up as a “VPN drops every 10 minutes” symptom even though the VPN is innocent.
5. Disable hibernation-sleep drop first
Microsoft’s Always On VPN overview documents that the Windows VPN client expects name-based triggering and trusted network detection to work even after the laptop sleeps — but those assumptions rely on drivers and the network stack being idle-aware.[1] A very common drop cause on Windows 11 is the wireless adapter going to sleep with the rest of the laptop, then failing to reconnect the tunnel cleanly afterward.
- Open Control Panel → Power Options → Change plan settings → Change advanced power settings.
- Expand Wireless Adapter Settings → Power Saving Mode and set it to Maximum Performance.
- Expand PCI Express → Link State Power Management and set it to Off.
- Expand Sleep → Allow wake timers and enable it (this lets the VPN client wake the network adapter when needed).
Practical caveat: These settings work for the current power plan. If you switch between “Balanced” and “Power saver” on the road, you may need to repeat them.
6. Mind the protocol — the failure modes are different
The Windows VPN platform ships four built-in tunneling protocols plus an Automatic option. Each one fails in different ways:[8]
Phone readers: swipe the table left to compare protocol-specific failure modes.
| Protocol | Common drop causes | First client-side check |
|---|---|---|
| IKEv2 | Rekey failure, certificate mismatch, NAT traversal blocked upstream. | Run an elevated Get-VpnConnection in PowerShell; verify the certificate under certlm.msc → Personal → Certificates has not expired. |
| L2TP/IPSec | Pre-shared key or certificate mismatch, NAT traversal requires a registry setting. | Confirm the pre-shared key or client certificate; KB 325034 documents the IPSec NAT-T requirements.[4] |
| SSTP | Blocked outbound TCP 443, captive portal, expired server certificate. | Verify the laptop can reach vpn.yourcompany.com on TCP 443 without the VPN profile. |
| PPTP | Deprecated; CISA and NSA recommend against it because the protocol has well-known weaknesses.[7] | Plan a migration to IKEv2 or SSTP with the IT owner; do not try to “fix” PPTP — replace it. |
| Automatic | Falls back to a less-preferred protocol when the first one fails; can mask the real cause. | Ask the IT owner for the explicit list to try, in order, before diagnosing. |
Practical ordering guidance: When in doubt, ask your IT owner which protocol the gateway supports. Always On VPN user tunnels support SSTP and IKEv2; device tunnels support IKEv2 only, with no SSTP fallback.[2][8]
7. Check for a recent cumulative update regression
Microsoft Q&A posts from 2026 show reproducible Always On VPN failures after specific cumulative updates, including the September 2026 KB5124008 rollup affecting certificate-based authentication on Windows 11 24H2/25H2. The documented signature is: VPN works, the rollup installs, Always On VPN stops working, uninstalling the rollup and rebooting restores it. Moderators recommended opening a Microsoft support case with RasClient/RasMan logs and pausing the rollup rollout until a fixed build ships.Microsoft Q&A thread (treated as timing context; not used as a load-bearing claim about your device).
- Open Settings → Windows Update → Update history and look at the last one or two installs.
- If the drop began within a day of a cumulative update, note the KB number but do not uninstall it on your own; unmanaged cumulative-update uninstalls are limited to ten days on Windows 11, and on managed devices only IT can authoritatively revert.
- Cross-check that the Windows 11 build is in a Microsoft-supported branch — Windows 11 26H2 is the current general-availability channel as of late September 2026 per our coverage.
8. Only now — and only if you own the profile — consider the narrowest repair
For a profile you created yourself, the narrowest repairs in order are: re-enter the pre-shared key (L2TP) or password, remove and recreate the built-in VPN profile under Settings → Network & internet → VPN, or run Windows’ msftconnecttest.net reachability check to confirm the DNS layer still works. Microsoft Support’s user guide walks through the GUI add/edit flow for a built-in profile.[9] For a vendor client (Cisco, Palo Alto, Fortinet, etc.), follow the vendor’s guidance; never blanket-uninstall the client and reinstall it without the gateway side information, because a different client bundle can overwrite a working managed profile.[2]
Practical change-control guidance: Network reset is documented as a last step — Microsoft’s network-reset page warns that VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] On a managed work device, schedule that with IT so the profile can be re-issued in the same window.
Good fixes and bad shortcuts
Good
- Record the exact error and timestamp before changing anything.
- Read RasClient and RasMan Event Viewer logs.
- Run Network Adapter and Internet Connections troubleshooters first.
- Test the same credentials from a second network (wired Ethernet or phone hotspot).
- Disable Wi-Fi power-saving on the wireless adapter.
- Ask IT to roll the tunnel to IKEv2 if the gateway supports it.
- Plan a migration away from PPTP — CISA and NSA both recommend against it.[7]
Bad
- Run Network reset on a managed work device without coordinating with IT.
- Uninstall a vendor VPN client on a managed device.
- Open TCP 443 or UDP 500/4500 on the home router “so the VPN can get through.”
- Edit the
AssumeUDPEncapsulationContextOnSendRuleregistry on a work laptop without documentation. - Type VPN credentials into a chat, screenshot, or email.
- Disable the firewall or antivirus “to see if that’s the problem.”
- Assume the VPN is broken because the Wi-Fi is bad.
Two realistic examples
Harmless misalignment: Wi-Fi power-save killing the tunnel
Illustrative example: A remote worker says the VPN drops every 20 to 40 minutes, only on the home Wi-Fi. The Event Viewer logs show repeated Remote Access Connection Manager events flagged as link state changes. The wireline adapter is fine; the Wi-Fi adapter was set to Power Saving Mode on the Balanced plan. Changing the adapter power setting to Maximum Performance on the home and current power plans keeps the tunnel stable for the full work day. The VPN client was never the problem.
Costly wrong turn: Network reset on a managed work device
Illustrative caution: A managed Windows 11 device has an Always On VPN profile delivered by Intune and a third-party EDR client. The user runs Settings → Network & internet → Advanced network settings → Network reset “to fix the VPN.” Network reset removes and reinstalls every network adapter and resets every network setting — including the Always On VPN tunnel and any third-party VPN client. Microsoft’s troubleshooting guidance explicitly warns that VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] The user now has a worse problem, and IT has to reissue the profile. Coordinate first.
Frequently asked questions
Does a “Connected” indicator mean the tunnel is actually working?
Not always. Microsoft documents that Always On VPN connectivity features — trusted network detection, name-based triggering, and name resolution via the Name Resolution Policy Table — can succeed while the authentication step later fails.[1] Confirm with one named resource behind the VPN, not by the tray icon.
Should I switch to PPTP because it’s the only option that “just works”?
No. Microsoft lists PPTP as one of the four built-in protocols but CISA and NSA’s hardening guidance explicitly recommends against relying on PPTP because of well-known weaknesses.[8][7] Ask your IT owner for IKEv2 or SSTP — those are the modern options.
Will running Network reset fix the VPN?
Sometimes, but at a high cost. Microsoft Q&A respondents and Microsoft’s own network-reset page treat it as a last-step option because it removes installed adapters and their settings, then reinstalls them with defaults — VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] Run the troubleshooters and read the logs first; only invoke Network reset on a device you own end-to-end.
Why does the VPN stay up on another laptop but not on mine?
That is comparison evidence pointing at your device, its profile, its adapter, or its update state. Check that you and the other laptop are connecting to the same gateway with the same protocol, and verify your Windows 11 build matches. If yours is a managed device, ask IT whether your device has the same Always On VPN profile payload as the working one.[2]
Can I test the VPN gateway over the public internet without going through the tunnel?
Yes — and that is a useful step. SSTP uses TCP 443; IKEv2 typically uses UDP 500 and UDP 4500 with NAT traversal. Confirm the gateway hostname is reachable on those ports and resolves to the IP your IT group gave you before the VPN profile is connected. If you can’t reach the gateway at all, the drop isn’t a Windows client problem.
Related guides from The IT Guys
- Remote Access Broke After a Router Upgrade? Check Double NAT and CGNAT — use this when the failure is on the carrier or router side rather than the Windows client.
- Is Remote Desktop Open to the Internet? Close Port 3389 and Use an Approved Remote-Access Plan — use this when Remote Desktop and VPN together are the workflow.
- Connected but No Internet? A 169.254 Address Points to DHCP, Not a Broken NIC — use this when the VPN works, but only certain name lookups fail.
- Weak Cell Signal Indoors? Set Up Wi-Fi Calling — and Fix the 911 Address — use this when the laptop loses both Wi-Fi and the cellular fallback.
Your next action
Capture the exact VPN error and timestamp. Open Event Viewer and read RasClient and RasMan. Run the Network Adapter troubleshooter. If this is a managed work device and the troubleshooter, log review, and adapter power settings don’t identify the cause, contact The IT Guys with the error, the KB number of the most recent cumulative update, and an export of the two logs — never send us a password, certificate, or session key.
Sources
- Microsoft Learn: About Always On VPN for Windows Server Remote Access — accessed October 21, 2026.
- Microsoft Learn: Tutorial — Create Always On VPN Connection on Windows Client Devices — accessed October 21, 2026.
- Microsoft Learn: VPN authentication options in Windows — accessed October 21, 2026.
- Microsoft Learn: Troubleshoot L2TP/IPSec VPN client connection (KB 325034) — last updated February 12, 2026.
- Microsoft Learn Q&A: Always On VPN disconnections — RasClient and RasMan event-log pointers — accessed October 21, 2026.
- Microsoft Learn Q&A: Persistent network connection drops in Windows 11 — accessed October 21, 2026.
- CISA + NSA: Selecting and Hardening Remote Access VPN Solutions — accessed October 21, 2026.
- Microsoft Learn: VPN connection types (IKEv2/L2TP/PPTP/SSTP/Automatic) — accessed October 21, 2026.
- Microsoft Support: Connect to a VPN in Windows — applies to Windows 10 and Windows 11, accessed October 21, 2026.
Treat as in scope
- Any built-in VPN profile listed under Settings → Network & internet → VPN.
- Any vendor VPN client that came from the Microsoft Store, your employer, or an IT-pushed application.[9]
- Always On VPN user tunnels and device tunnels deployed by Intune, Configuration Manager, or PowerShell.[2]
- Built-in tunneling protocols IKEv2, L2TP/IPSec, SSTP, and PPTP.[8]
- Connections that drop after sleep, after switching between Wi-Fi and Ethernet, after a recent cumulative update, or after a long idle period.[5]
Not automatically a VPN problem
- A flaky public Wi-Fi network that is dropping everything, not just the tunnel.
- An outage on the VPN gateway or corporate firewall itself.
- A captive portal (hotel, café, airport) you haven’t signed into.
- A sleep/hibernate issue, lid-close issue, or power-policy issue that happens to wake up the laptop.
- A certificate that expired on the gateway side, not on your laptop.[7]
Step-by-step: narrow down the cause before changing anything
1. Capture the exact symptom and timing
Practical evidence-preservation guidance: Write down the date, time, Wi-Fi network, what you clicked, the connection entry name, and the precise wording of any error. A message like “The VPN connection failed” or “A connection to the remote computer could not be established” is diagnostic gold for whoever has to fix it. Screenshots or photos of the dialog are acceptable; passwords, certificates, and session keys are not.
Practical platform note: Microsoft Support’s user-facing VPN guide says you can connect or disconnect from the VPN quick setting on the taskbar, and that any sign-in prompt that appears is the gateway’s authentication dialog — not Windows itself.[9] If you suspect a credential issue, the safest first move is to confirm the password still works in the IT-managed webmail or password-reset portal before touching the VPN client.
2. Open the two Event Viewer logs that matter
Microsoft Q&A moderators recommend the same two logs for Always On VPN disconnects: Applications and Services Logs → Microsoft → Windows → RasClient and RasMan. The RasClient log is for client-side events (dial attempts, credential prompts, user actions); the RasMan log is for the Remote Access Connection Manager service that owns the connection.[5]
- Open Event Viewer from the Start menu (run as administrator if you can).
- Expand Applications and Services Logs, then Microsoft, then Windows.
- Click RasClient in the left pane, then click Filter Current Log… on the right and choose Last hour or Last 24 hours, with Critical, Error, and Warning levels checked.
- Repeat for RasMan.
- Look for repeating entries with the same Event ID — that is the diagnostic signature. Common IDs include 20222 (IKE authentication credentials are unacceptable), 20224 (IKE failed to find a valid machine certificate), and Event 4-class messages in RasMan about a connection terminated.
Practical scope guidance: Don’t mail the logs straight to IT. Export them as .evtx from Event Viewer only when the IT owner asks for them; the logs can include host names and timestamps but should not include credentials or session keys at the level of information shown in the user-facing filters.[5]
3. Run the built-in Network troubleshooter first
Before you change anything, run the troubleshooter Microsoft already ships with Windows 11. Microsoft Q&A guidance lists Network Adapter and Internet Connections as the right troubleshooters, and recommends them over a Network reset whenever a connection drops but does not fail outright.[6]
- Open Start → Settings → System → Troubleshoot → Other troubleshooters.
- Run Network Adapter first. If it identifies an adapter-level issue, follow its one recommended fix.
- Run Internet Connections second to verify that the laptop still has working internet in general.
- If the troubleshooter reports “Troubleshooting couldn’t identify the problem,” that is not a clean bill of health — it just means it didn’t have a preset fix. Continue with the Event Viewer evidence.[6]
4. Reconnect once from a known-good network
Practical isolation guidance: Test the VPN from a wired Ethernet connection if you can — Microsoft Q&A respondents specifically recommend this to separate “wired-only, wireless-only, or both” failure modes for persistent drops.[6] If wired works but wireless drops, the cause is Wi-Fi roaming or a weak signal — not the VPN client.
- Disable VPN split tunneling if the IT profile enables it, then reconnect — a poorly framed split-tunnel policy can break name resolution while leaving the tunnel up.[1]
- If you connect from home, also try a phone hotspot for one connection test — that cleanly separates the Wi-Fi network from the laptop’s wireless adapter.
- Move closer to the Wi-Fi access point or restart the access point itself; intermittent wireless can show up as a “VPN drops every 10 minutes” symptom even though the VPN is innocent.
5. Disable hibernation-sleep drop first
Microsoft’s Always On VPN overview documents that the Windows VPN client expects name-based triggering and trusted network detection to work even after the laptop sleeps — but those assumptions rely on drivers and the network stack being idle-aware.[1] A very common drop cause on Windows 11 is the wireless adapter going to sleep with the rest of the laptop, then failing to reconnect the tunnel cleanly afterward.
- Open Control Panel → Power Options → Change plan settings → Change advanced power settings.
- Expand Wireless Adapter Settings → Power Saving Mode and set it to Maximum Performance.
- Expand PCI Express → Link State Power Management and set it to Off.
- Expand Sleep → Allow wake timers and enable it (this lets the VPN client wake the network adapter when needed).
Practical caveat: These settings work for the current power plan. If you switch between “Balanced” and “Power saver” on the road, you may need to repeat them.
6. Mind the protocol — the failure modes are different
The Windows VPN platform ships four built-in tunneling protocols plus an Automatic option. Each one fails in different ways:[8]
Phone readers: swipe the table left to compare protocol-specific failure modes.
| Protocol | Common drop causes | First client-side check |
|---|---|---|
| IKEv2 | Rekey failure, certificate mismatch, NAT traversal blocked upstream. | Run an elevated Get-VpnConnection in PowerShell; verify the certificate under certlm.msc → Personal → Certificates has not expired. |
| L2TP/IPSec | Pre-shared key or certificate mismatch, NAT traversal requires a registry setting. | Confirm the pre-shared key or client certificate; KB 325034 documents the IPSec NAT-T requirements.[4] |
| SSTP | Blocked outbound TCP 443, captive portal, expired server certificate. | Verify the laptop can reach vpn.yourcompany.com on TCP 443 without the VPN profile. |
| PPTP | Deprecated; CISA and NSA recommend against it because the protocol has well-known weaknesses.[7] | Plan a migration to IKEv2 or SSTP with the IT owner; do not try to “fix” PPTP — replace it. |
| Automatic | Falls back to a less-preferred protocol when the first one fails; can mask the real cause. | Ask the IT owner for the explicit list to try, in order, before diagnosing. |
Practical ordering guidance: When in doubt, ask your IT owner which protocol the gateway supports. Always On VPN user tunnels support SSTP and IKEv2; device tunnels support IKEv2 only, with no SSTP fallback.[2][8]
7. Check for a recent cumulative update regression
Microsoft Q&A posts from 2026 show reproducible Always On VPN failures after specific cumulative updates, including the September 2026 KB5124008 rollup affecting certificate-based authentication on Windows 11 24H2/25H2. The documented signature is: VPN works, the rollup installs, Always On VPN stops working, uninstalling the rollup and rebooting restores it. Moderators recommended opening a Microsoft support case with RasClient/RasMan logs and pausing the rollup rollout until a fixed build ships.Microsoft Q&A thread (treated as timing context; not used as a load-bearing claim about your device).
- Open Settings → Windows Update → Update history and look at the last one or two installs.
- If the drop began within a day of a cumulative update, note the KB number but do not uninstall it on your own; unmanaged cumulative-update uninstalls are limited to ten days on Windows 11, and on managed devices only IT can authoritatively revert.
- Cross-check that the Windows 11 build is in a Microsoft-supported branch — Windows 11 26H2 is the current general-availability channel as of late September 2026 per our coverage.
8. Only now — and only if you own the profile — consider the narrowest repair
For a profile you created yourself, the narrowest repairs in order are: re-enter the pre-shared key (L2TP) or password, remove and recreate the built-in VPN profile under Settings → Network & internet → VPN, or run Windows’ msftconnecttest.net reachability check to confirm the DNS layer still works. Microsoft Support’s user guide walks through the GUI add/edit flow for a built-in profile.[9] For a vendor client (Cisco, Palo Alto, Fortinet, etc.), follow the vendor’s guidance; never blanket-uninstall the client and reinstall it without the gateway side information, because a different client bundle can overwrite a working managed profile.[2]
Practical change-control guidance: Network reset is documented as a last step — Microsoft’s network-reset page warns that VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] On a managed work device, schedule that with IT so the profile can be re-issued in the same window.
Good fixes and bad shortcuts
Good
- Record the exact error and timestamp before changing anything.
- Read RasClient and RasMan Event Viewer logs.
- Run Network Adapter and Internet Connections troubleshooters first.
- Test the same credentials from a second network (wired Ethernet or phone hotspot).
- Disable Wi-Fi power-saving on the wireless adapter.
- Ask IT to roll the tunnel to IKEv2 if the gateway supports it.
- Plan a migration away from PPTP — CISA and NSA both recommend against it.[7]
Bad
- Run Network reset on a managed work device without coordinating with IT.
- Uninstall a vendor VPN client on a managed device.
- Open TCP 443 or UDP 500/4500 on the home router “so the VPN can get through.”
- Edit the
AssumeUDPEncapsulationContextOnSendRuleregistry on a work laptop without documentation. - Type VPN credentials into a chat, screenshot, or email.
- Disable the firewall or antivirus “to see if that’s the problem.”
- Assume the VPN is broken because the Wi-Fi is bad.
Two realistic examples
Harmless misalignment: Wi-Fi power-save killing the tunnel
Illustrative example: A remote worker says the VPN drops every 20 to 40 minutes, only on the home Wi-Fi. The Event Viewer logs show repeated Remote Access Connection Manager events flagged as link state changes. The wireline adapter is fine; the Wi-Fi adapter was set to Power Saving Mode on the Balanced plan. Changing the adapter power setting to Maximum Performance on the home and current power plans keeps the tunnel stable for the full work day. The VPN client was never the problem.
Costly wrong turn: Network reset on a managed work device
Illustrative caution: A managed Windows 11 device has an Always On VPN profile delivered by Intune and a third-party EDR client. The user runs Settings → Network & internet → Advanced network settings → Network reset “to fix the VPN.” Network reset removes and reinstalls every network adapter and resets every network setting — including the Always On VPN tunnel and any third-party VPN client. Microsoft’s troubleshooting guidance explicitly warns that VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] The user now has a worse problem, and IT has to reissue the profile. Coordinate first.
Frequently asked questions
Does a “Connected” indicator mean the tunnel is actually working?
Not always. Microsoft documents that Always On VPN connectivity features — trusted network detection, name-based triggering, and name resolution via the Name Resolution Policy Table — can succeed while the authentication step later fails.[1] Confirm with one named resource behind the VPN, not by the tray icon.
Should I switch to PPTP because it’s the only option that “just works”?
No. Microsoft lists PPTP as one of the four built-in protocols but CISA and NSA’s hardening guidance explicitly recommends against relying on PPTP because of well-known weaknesses.[8][7] Ask your IT owner for IKEv2 or SSTP — those are the modern options.
Will running Network reset fix the VPN?
Sometimes, but at a high cost. Microsoft Q&A respondents and Microsoft’s own network-reset page treat it as a last-step option because it removes installed adapters and their settings, then reinstalls them with defaults — VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] Run the troubleshooters and read the logs first; only invoke Network reset on a device you own end-to-end.
Why does the VPN stay up on another laptop but not on mine?
That is comparison evidence pointing at your device, its profile, its adapter, or its update state. Check that you and the other laptop are connecting to the same gateway with the same protocol, and verify your Windows 11 build matches. If yours is a managed device, ask IT whether your device has the same Always On VPN profile payload as the working one.[2]
Can I test the VPN gateway over the public internet without going through the tunnel?
Yes — and that is a useful step. SSTP uses TCP 443; IKEv2 typically uses UDP 500 and UDP 4500 with NAT traversal. Confirm the gateway hostname is reachable on those ports and resolves to the IP your IT group gave you before the VPN profile is connected. If you can’t reach the gateway at all, the drop isn’t a Windows client problem.
Related guides from The IT Guys
- Remote Access Broke After a Router Upgrade? Check Double NAT and CGNAT — use this when the failure is on the carrier or router side rather than the Windows client.
- Is Remote Desktop Open to the Internet? Close Port 3389 and Use an Approved Remote-Access Plan — use this when Remote Desktop and VPN together are the workflow.
- Connected but No Internet? A 169.254 Address Points to DHCP, Not a Broken NIC — use this when the VPN works, but only certain name lookups fail.
- Weak Cell Signal Indoors? Set Up Wi-Fi Calling — and Fix the 911 Address — use this when the laptop loses both Wi-Fi and the cellular fallback.
Your next action
Capture the exact VPN error and timestamp. Open Event Viewer and read RasClient and RasMan. Run the Network Adapter troubleshooter. If this is a managed work device and the troubleshooter, log review, and adapter power settings don’t identify the cause, contact The IT Guys with the error, the KB number of the most recent cumulative update, and an export of the two logs — never send us a password, certificate, or session key.
Sources
- Microsoft Learn: About Always On VPN for Windows Server Remote Access — accessed October 21, 2026.
- Microsoft Learn: Tutorial — Create Always On VPN Connection on Windows Client Devices — accessed October 21, 2026.
- Microsoft Learn: VPN authentication options in Windows — accessed October 21, 2026.
- Microsoft Learn: Troubleshoot L2TP/IPSec VPN client connection (KB 325034) — last updated February 12, 2026.
- Microsoft Learn Q&A: Always On VPN disconnections — RasClient and RasMan event-log pointers — accessed October 21, 2026.
- Microsoft Learn Q&A: Persistent network connection drops in Windows 11 — accessed October 21, 2026.
- CISA + NSA: Selecting and Hardening Remote Access VPN Solutions — accessed October 21, 2026.
- Microsoft Learn: VPN connection types (IKEv2/L2TP/PPTP/SSTP/Automatic) — accessed October 21, 2026.
- Microsoft Support: Connect to a VPN in Windows — applies to Windows 10 and Windows 11, accessed October 21, 2026.
Stop and call IT if you see these signs
- The VPN profile was installed by your employer, school, or managed device (Intune, Configuration Manager, GPO, MDM) and you are not sure how it was deployed.
- The tunnel used to work this morning and now won’t connect — and a Windows Update ran on the same day.
- The connection drops the moment the laptop sleeps, hibernates, or switches from Ethernet to Wi-Fi.
- The same credentials work on a phone or another PC but not on this Windows 11 device.
- Microsoft Support or your IT helpdesk has asked you to preserve Event Viewer logs under
Applications and Services Logs → Microsoft → Windows → RasClientandRasManbefore changing anything.[5]
Microsoft’s Always On VPN documentation lists connectivity, name resolution, and trusted network detection as the three things the platform tries before authenticating — any one of them failing can cause the exact “connects then drops” symptom you are seeing.[1] Practical guidance: On a managed work device, your IT owner of the VPN profile is the right escalation for client reinstalls, profile reissues, certificate renewals, and Network reset; running those on your own can strip the deployed profile and quietly disable the tunnel for everyone.
Why this problem is easy to miss
Practical observation: A VPN can connect, place you into a private network, and then quietly drop a few minutes later. You may not notice immediately — a browser tab keeps an HTTP connection open, a remote desktop session recovers — until you try to reach a resource on the other side of the tunnel. Microsoft Learn’s Always On VPN overview calls this out: connectivity features include trusted network detection and name-based triggering, which can fail invisibly if the laptop loses the home Wi-Fi for a moment or the laptop’s VPN adapter falls out of the routing table.[1]
Practical scope guidance: The Windows VPN platform supports four built-in tunneling protocols (IKEv2, L2TP, PPTP, and SSTP) plus an Automatic option that tries each one in order.[8] Each protocol has its own authentication and rekey behavior. CISA and NSA’s “Selecting and Hardening Remote Access VPN Solutions” information sheet calls out that protocol choice, authentication strength, and rekey settings directly affect stability and security.[7] Practical inference: “The VPN keeps dropping” is rarely the same root cause across protocols — treat the symptom as a clue, not a verdict.
Practical platform distinction: On Windows 11 you can have a built-in VPN profile or a vendor-installed VPN client such as Cisco AnyConnect, GlobalProtect, FortiClient, WireGuard, or OpenVPN GUI. Microsoft documents that the built-in solution uses Extensible Authentication Protocol (EAP) for username/password and certificate-based authentication and that third-party vendors register their products as Universal Windows Platform VPN plug-ins.[3][8] Practical change-control guidance: Reinstalling the wrong layer, or in the wrong order, can remove the working client and reinstall a built-in profile that nothing on the network will accept.
Who should run this diagnostic?
Treat the following as the scope of the problem — not as proof that the VPN is broken.
Treat as in scope
- Any built-in VPN profile listed under Settings → Network & internet → VPN.
- Any vendor VPN client that came from the Microsoft Store, your employer, or an IT-pushed application.[9]
- Always On VPN user tunnels and device tunnels deployed by Intune, Configuration Manager, or PowerShell.[2]
- Built-in tunneling protocols IKEv2, L2TP/IPSec, SSTP, and PPTP.[8]
- Connections that drop after sleep, after switching between Wi-Fi and Ethernet, after a recent cumulative update, or after a long idle period.[5]
Not automatically a VPN problem
- A flaky public Wi-Fi network that is dropping everything, not just the tunnel.
- An outage on the VPN gateway or corporate firewall itself.
- A captive portal (hotel, café, airport) you haven’t signed into.
- A sleep/hibernate issue, lid-close issue, or power-policy issue that happens to wake up the laptop.
- A certificate that expired on the gateway side, not on your laptop.[7]
Step-by-step: narrow down the cause before changing anything
1. Capture the exact symptom and timing
Practical evidence-preservation guidance: Write down the date, time, Wi-Fi network, what you clicked, the connection entry name, and the precise wording of any error. A message like “The VPN connection failed” or “A connection to the remote computer could not be established” is diagnostic gold for whoever has to fix it. Screenshots or photos of the dialog are acceptable; passwords, certificates, and session keys are not.
Practical platform note: Microsoft Support’s user-facing VPN guide says you can connect or disconnect from the VPN quick setting on the taskbar, and that any sign-in prompt that appears is the gateway’s authentication dialog — not Windows itself.[9] If you suspect a credential issue, the safest first move is to confirm the password still works in the IT-managed webmail or password-reset portal before touching the VPN client.
2. Open the two Event Viewer logs that matter
Microsoft Q&A moderators recommend the same two logs for Always On VPN disconnects: Applications and Services Logs → Microsoft → Windows → RasClient and RasMan. The RasClient log is for client-side events (dial attempts, credential prompts, user actions); the RasMan log is for the Remote Access Connection Manager service that owns the connection.[5]
- Open Event Viewer from the Start menu (run as administrator if you can).
- Expand Applications and Services Logs, then Microsoft, then Windows.
- Click RasClient in the left pane, then click Filter Current Log… on the right and choose Last hour or Last 24 hours, with Critical, Error, and Warning levels checked.
- Repeat for RasMan.
- Look for repeating entries with the same Event ID — that is the diagnostic signature. Common IDs include 20222 (IKE authentication credentials are unacceptable), 20224 (IKE failed to find a valid machine certificate), and Event 4-class messages in RasMan about a connection terminated.
Practical scope guidance: Don’t mail the logs straight to IT. Export them as .evtx from Event Viewer only when the IT owner asks for them; the logs can include host names and timestamps but should not include credentials or session keys at the level of information shown in the user-facing filters.[5]
3. Run the built-in Network troubleshooter first
Before you change anything, run the troubleshooter Microsoft already ships with Windows 11. Microsoft Q&A guidance lists Network Adapter and Internet Connections as the right troubleshooters, and recommends them over a Network reset whenever a connection drops but does not fail outright.[6]
- Open Start → Settings → System → Troubleshoot → Other troubleshooters.
- Run Network Adapter first. If it identifies an adapter-level issue, follow its one recommended fix.
- Run Internet Connections second to verify that the laptop still has working internet in general.
- If the troubleshooter reports “Troubleshooting couldn’t identify the problem,” that is not a clean bill of health — it just means it didn’t have a preset fix. Continue with the Event Viewer evidence.[6]
4. Reconnect once from a known-good network
Practical isolation guidance: Test the VPN from a wired Ethernet connection if you can — Microsoft Q&A respondents specifically recommend this to separate “wired-only, wireless-only, or both” failure modes for persistent drops.[6] If wired works but wireless drops, the cause is Wi-Fi roaming or a weak signal — not the VPN client.
- Disable VPN split tunneling if the IT profile enables it, then reconnect — a poorly framed split-tunnel policy can break name resolution while leaving the tunnel up.[1]
- If you connect from home, also try a phone hotspot for one connection test — that cleanly separates the Wi-Fi network from the laptop’s wireless adapter.
- Move closer to the Wi-Fi access point or restart the access point itself; intermittent wireless can show up as a “VPN drops every 10 minutes” symptom even though the VPN is innocent.
5. Disable hibernation-sleep drop first
Microsoft’s Always On VPN overview documents that the Windows VPN client expects name-based triggering and trusted network detection to work even after the laptop sleeps — but those assumptions rely on drivers and the network stack being idle-aware.[1] A very common drop cause on Windows 11 is the wireless adapter going to sleep with the rest of the laptop, then failing to reconnect the tunnel cleanly afterward.
- Open Control Panel → Power Options → Change plan settings → Change advanced power settings.
- Expand Wireless Adapter Settings → Power Saving Mode and set it to Maximum Performance.
- Expand PCI Express → Link State Power Management and set it to Off.
- Expand Sleep → Allow wake timers and enable it (this lets the VPN client wake the network adapter when needed).
Practical caveat: These settings work for the current power plan. If you switch between “Balanced” and “Power saver” on the road, you may need to repeat them.
6. Mind the protocol — the failure modes are different
The Windows VPN platform ships four built-in tunneling protocols plus an Automatic option. Each one fails in different ways:[8]
Phone readers: swipe the table left to compare protocol-specific failure modes.
| Protocol | Common drop causes | First client-side check |
|---|---|---|
| IKEv2 | Rekey failure, certificate mismatch, NAT traversal blocked upstream. | Run an elevated Get-VpnConnection in PowerShell; verify the certificate under certlm.msc → Personal → Certificates has not expired. |
| L2TP/IPSec | Pre-shared key or certificate mismatch, NAT traversal requires a registry setting. | Confirm the pre-shared key or client certificate; KB 325034 documents the IPSec NAT-T requirements.[4] |
| SSTP | Blocked outbound TCP 443, captive portal, expired server certificate. | Verify the laptop can reach vpn.yourcompany.com on TCP 443 without the VPN profile. |
| PPTP | Deprecated; CISA and NSA recommend against it because the protocol has well-known weaknesses.[7] | Plan a migration to IKEv2 or SSTP with the IT owner; do not try to “fix” PPTP — replace it. |
| Automatic | Falls back to a less-preferred protocol when the first one fails; can mask the real cause. | Ask the IT owner for the explicit list to try, in order, before diagnosing. |
Practical ordering guidance: When in doubt, ask your IT owner which protocol the gateway supports. Always On VPN user tunnels support SSTP and IKEv2; device tunnels support IKEv2 only, with no SSTP fallback.[2][8]
7. Check for a recent cumulative update regression
Microsoft Q&A posts from 2026 show reproducible Always On VPN failures after specific cumulative updates, including the September 2026 KB5124008 rollup affecting certificate-based authentication on Windows 11 24H2/25H2. The documented signature is: VPN works, the rollup installs, Always On VPN stops working, uninstalling the rollup and rebooting restores it. Moderators recommended opening a Microsoft support case with RasClient/RasMan logs and pausing the rollup rollout until a fixed build ships.Microsoft Q&A thread (treated as timing context; not used as a load-bearing claim about your device).
- Open Settings → Windows Update → Update history and look at the last one or two installs.
- If the drop began within a day of a cumulative update, note the KB number but do not uninstall it on your own; unmanaged cumulative-update uninstalls are limited to ten days on Windows 11, and on managed devices only IT can authoritatively revert.
- Cross-check that the Windows 11 build is in a Microsoft-supported branch — Windows 11 26H2 is the current general-availability channel as of late September 2026 per our coverage.
8. Only now — and only if you own the profile — consider the narrowest repair
For a profile you created yourself, the narrowest repairs in order are: re-enter the pre-shared key (L2TP) or password, remove and recreate the built-in VPN profile under Settings → Network & internet → VPN, or run Windows’ msftconnecttest.net reachability check to confirm the DNS layer still works. Microsoft Support’s user guide walks through the GUI add/edit flow for a built-in profile.[9] For a vendor client (Cisco, Palo Alto, Fortinet, etc.), follow the vendor’s guidance; never blanket-uninstall the client and reinstall it without the gateway side information, because a different client bundle can overwrite a working managed profile.[2]
Practical change-control guidance: Network reset is documented as a last step — Microsoft’s network-reset page warns that VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] On a managed work device, schedule that with IT so the profile can be re-issued in the same window.
Good fixes and bad shortcuts
Good
- Record the exact error and timestamp before changing anything.
- Read RasClient and RasMan Event Viewer logs.
- Run Network Adapter and Internet Connections troubleshooters first.
- Test the same credentials from a second network (wired Ethernet or phone hotspot).
- Disable Wi-Fi power-saving on the wireless adapter.
- Ask IT to roll the tunnel to IKEv2 if the gateway supports it.
- Plan a migration away from PPTP — CISA and NSA both recommend against it.[7]
Bad
- Run Network reset on a managed work device without coordinating with IT.
- Uninstall a vendor VPN client on a managed device.
- Open TCP 443 or UDP 500/4500 on the home router “so the VPN can get through.”
- Edit the
AssumeUDPEncapsulationContextOnSendRuleregistry on a work laptop without documentation. - Type VPN credentials into a chat, screenshot, or email.
- Disable the firewall or antivirus “to see if that’s the problem.”
- Assume the VPN is broken because the Wi-Fi is bad.
Two realistic examples
Harmless misalignment: Wi-Fi power-save killing the tunnel
Illustrative example: A remote worker says the VPN drops every 20 to 40 minutes, only on the home Wi-Fi. The Event Viewer logs show repeated Remote Access Connection Manager events flagged as link state changes. The wireline adapter is fine; the Wi-Fi adapter was set to Power Saving Mode on the Balanced plan. Changing the adapter power setting to Maximum Performance on the home and current power plans keeps the tunnel stable for the full work day. The VPN client was never the problem.
Costly wrong turn: Network reset on a managed work device
Illustrative caution: A managed Windows 11 device has an Always On VPN profile delivered by Intune and a third-party EDR client. The user runs Settings → Network & internet → Advanced network settings → Network reset “to fix the VPN.” Network reset removes and reinstalls every network adapter and resets every network setting — including the Always On VPN tunnel and any third-party VPN client. Microsoft’s troubleshooting guidance explicitly warns that VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] The user now has a worse problem, and IT has to reissue the profile. Coordinate first.
Frequently asked questions
Does a “Connected” indicator mean the tunnel is actually working?
Not always. Microsoft documents that Always On VPN connectivity features — trusted network detection, name-based triggering, and name resolution via the Name Resolution Policy Table — can succeed while the authentication step later fails.[1] Confirm with one named resource behind the VPN, not by the tray icon.
Should I switch to PPTP because it’s the only option that “just works”?
No. Microsoft lists PPTP as one of the four built-in protocols but CISA and NSA’s hardening guidance explicitly recommends against relying on PPTP because of well-known weaknesses.[8][7] Ask your IT owner for IKEv2 or SSTP — those are the modern options.
Will running Network reset fix the VPN?
Sometimes, but at a high cost. Microsoft Q&A respondents and Microsoft’s own network-reset page treat it as a last-step option because it removes installed adapters and their settings, then reinstalls them with defaults — VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] Run the troubleshooters and read the logs first; only invoke Network reset on a device you own end-to-end.
Why does the VPN stay up on another laptop but not on mine?
That is comparison evidence pointing at your device, its profile, its adapter, or its update state. Check that you and the other laptop are connecting to the same gateway with the same protocol, and verify your Windows 11 build matches. If yours is a managed device, ask IT whether your device has the same Always On VPN profile payload as the working one.[2]
Can I test the VPN gateway over the public internet without going through the tunnel?
Yes — and that is a useful step. SSTP uses TCP 443; IKEv2 typically uses UDP 500 and UDP 4500 with NAT traversal. Confirm the gateway hostname is reachable on those ports and resolves to the IP your IT group gave you before the VPN profile is connected. If you can’t reach the gateway at all, the drop isn’t a Windows client problem.
Related guides from The IT Guys
- Remote Access Broke After a Router Upgrade? Check Double NAT and CGNAT — use this when the failure is on the carrier or router side rather than the Windows client.
- Is Remote Desktop Open to the Internet? Close Port 3389 and Use an Approved Remote-Access Plan — use this when Remote Desktop and VPN together are the workflow.
- Connected but No Internet? A 169.254 Address Points to DHCP, Not a Broken NIC — use this when the VPN works, but only certain name lookups fail.
- Weak Cell Signal Indoors? Set Up Wi-Fi Calling — and Fix the 911 Address — use this when the laptop loses both Wi-Fi and the cellular fallback.
Your next action
Capture the exact VPN error and timestamp. Open Event Viewer and read RasClient and RasMan. Run the Network Adapter troubleshooter. If this is a managed work device and the troubleshooter, log review, and adapter power settings don’t identify the cause, contact The IT Guys with the error, the KB number of the most recent cumulative update, and an export of the two logs — never send us a password, certificate, or session key.
Sources
- Microsoft Learn: About Always On VPN for Windows Server Remote Access — accessed October 21, 2026.
- Microsoft Learn: Tutorial — Create Always On VPN Connection on Windows Client Devices — accessed October 21, 2026.
- Microsoft Learn: VPN authentication options in Windows — accessed October 21, 2026.
- Microsoft Learn: Troubleshoot L2TP/IPSec VPN client connection (KB 325034) — last updated February 12, 2026.
- Microsoft Learn Q&A: Always On VPN disconnections — RasClient and RasMan event-log pointers — accessed October 21, 2026.
- Microsoft Learn Q&A: Persistent network connection drops in Windows 11 — accessed October 21, 2026.
- CISA + NSA: Selecting and Hardening Remote Access VPN Solutions — accessed October 21, 2026.
- Microsoft Learn: VPN connection types (IKEv2/L2TP/PPTP/SSTP/Automatic) — accessed October 21, 2026.
- Microsoft Support: Connect to a VPN in Windows — applies to Windows 10 and Windows 11, accessed October 21, 2026.
Practical fix: A Windows 11 VPN that connects, then drops a few minutes later — or fails to reconnect — usually has one of a small set of causes. Diagnose the tunnel with the built-in troubleshooter and Event Viewer logs before you reinstall the client, change the registry, or run Network reset, because those “fixes” can remove IT-deployed profiles on managed devices and break unrelated working connections.[1][5]
Stop and call IT if you see these signs
- The VPN profile was installed by your employer, school, or managed device (Intune, Configuration Manager, GPO, MDM) and you are not sure how it was deployed.
- The tunnel used to work this morning and now won’t connect — and a Windows Update ran on the same day.
- The connection drops the moment the laptop sleeps, hibernates, or switches from Ethernet to Wi-Fi.
- The same credentials work on a phone or another PC but not on this Windows 11 device.
- Microsoft Support or your IT helpdesk has asked you to preserve Event Viewer logs under
Applications and Services Logs → Microsoft → Windows → RasClientandRasManbefore changing anything.[5]
Microsoft’s Always On VPN documentation lists connectivity, name resolution, and trusted network detection as the three things the platform tries before authenticating — any one of them failing can cause the exact “connects then drops” symptom you are seeing.[1] Practical guidance: On a managed work device, your IT owner of the VPN profile is the right escalation for client reinstalls, profile reissues, certificate renewals, and Network reset; running those on your own can strip the deployed profile and quietly disable the tunnel for everyone.
Why this problem is easy to miss
Practical observation: A VPN can connect, place you into a private network, and then quietly drop a few minutes later. You may not notice immediately — a browser tab keeps an HTTP connection open, a remote desktop session recovers — until you try to reach a resource on the other side of the tunnel. Microsoft Learn’s Always On VPN overview calls this out: connectivity features include trusted network detection and name-based triggering, which can fail invisibly if the laptop loses the home Wi-Fi for a moment or the laptop’s VPN adapter falls out of the routing table.[1]
Practical scope guidance: The Windows VPN platform supports four built-in tunneling protocols (IKEv2, L2TP, PPTP, and SSTP) plus an Automatic option that tries each one in order.[8] Each protocol has its own authentication and rekey behavior. CISA and NSA’s “Selecting and Hardening Remote Access VPN Solutions” information sheet calls out that protocol choice, authentication strength, and rekey settings directly affect stability and security.[7] Practical inference: “The VPN keeps dropping” is rarely the same root cause across protocols — treat the symptom as a clue, not a verdict.
Practical platform distinction: On Windows 11 you can have a built-in VPN profile or a vendor-installed VPN client such as Cisco AnyConnect, GlobalProtect, FortiClient, WireGuard, or OpenVPN GUI. Microsoft documents that the built-in solution uses Extensible Authentication Protocol (EAP) for username/password and certificate-based authentication and that third-party vendors register their products as Universal Windows Platform VPN plug-ins.[3][8] Practical change-control guidance: Reinstalling the wrong layer, or in the wrong order, can remove the working client and reinstall a built-in profile that nothing on the network will accept.
Who should run this diagnostic?
Treat the following as the scope of the problem — not as proof that the VPN is broken.
Treat as in scope
- Any built-in VPN profile listed under Settings → Network & internet → VPN.
- Any vendor VPN client that came from the Microsoft Store, your employer, or an IT-pushed application.[9]
- Always On VPN user tunnels and device tunnels deployed by Intune, Configuration Manager, or PowerShell.[2]
- Built-in tunneling protocols IKEv2, L2TP/IPSec, SSTP, and PPTP.[8]
- Connections that drop after sleep, after switching between Wi-Fi and Ethernet, after a recent cumulative update, or after a long idle period.[5]
Not automatically a VPN problem
- A flaky public Wi-Fi network that is dropping everything, not just the tunnel.
- An outage on the VPN gateway or corporate firewall itself.
- A captive portal (hotel, café, airport) you haven’t signed into.
- A sleep/hibernate issue, lid-close issue, or power-policy issue that happens to wake up the laptop.
- A certificate that expired on the gateway side, not on your laptop.[7]
Step-by-step: narrow down the cause before changing anything
1. Capture the exact symptom and timing
Practical evidence-preservation guidance: Write down the date, time, Wi-Fi network, what you clicked, the connection entry name, and the precise wording of any error. A message like “The VPN connection failed” or “A connection to the remote computer could not be established” is diagnostic gold for whoever has to fix it. Screenshots or photos of the dialog are acceptable; passwords, certificates, and session keys are not.
Practical platform note: Microsoft Support’s user-facing VPN guide says you can connect or disconnect from the VPN quick setting on the taskbar, and that any sign-in prompt that appears is the gateway’s authentication dialog — not Windows itself.[9] If you suspect a credential issue, the safest first move is to confirm the password still works in the IT-managed webmail or password-reset portal before touching the VPN client.
2. Open the two Event Viewer logs that matter
Microsoft Q&A moderators recommend the same two logs for Always On VPN disconnects: Applications and Services Logs → Microsoft → Windows → RasClient and RasMan. The RasClient log is for client-side events (dial attempts, credential prompts, user actions); the RasMan log is for the Remote Access Connection Manager service that owns the connection.[5]
- Open Event Viewer from the Start menu (run as administrator if you can).
- Expand Applications and Services Logs, then Microsoft, then Windows.
- Click RasClient in the left pane, then click Filter Current Log… on the right and choose Last hour or Last 24 hours, with Critical, Error, and Warning levels checked.
- Repeat for RasMan.
- Look for repeating entries with the same Event ID — that is the diagnostic signature. Common IDs include 20222 (IKE authentication credentials are unacceptable), 20224 (IKE failed to find a valid machine certificate), and Event 4-class messages in RasMan about a connection terminated.
Practical scope guidance: Don’t mail the logs straight to IT. Export them as .evtx from Event Viewer only when the IT owner asks for them; the logs can include host names and timestamps but should not include credentials or session keys at the level of information shown in the user-facing filters.[5]
3. Run the built-in Network troubleshooter first
Before you change anything, run the troubleshooter Microsoft already ships with Windows 11. Microsoft Q&A guidance lists Network Adapter and Internet Connections as the right troubleshooters, and recommends them over a Network reset whenever a connection drops but does not fail outright.[6]
- Open Start → Settings → System → Troubleshoot → Other troubleshooters.
- Run Network Adapter first. If it identifies an adapter-level issue, follow its one recommended fix.
- Run Internet Connections second to verify that the laptop still has working internet in general.
- If the troubleshooter reports “Troubleshooting couldn’t identify the problem,” that is not a clean bill of health — it just means it didn’t have a preset fix. Continue with the Event Viewer evidence.[6]
4. Reconnect once from a known-good network
Practical isolation guidance: Test the VPN from a wired Ethernet connection if you can — Microsoft Q&A respondents specifically recommend this to separate “wired-only, wireless-only, or both” failure modes for persistent drops.[6] If wired works but wireless drops, the cause is Wi-Fi roaming or a weak signal — not the VPN client.
- Disable VPN split tunneling if the IT profile enables it, then reconnect — a poorly framed split-tunnel policy can break name resolution while leaving the tunnel up.[1]
- If you connect from home, also try a phone hotspot for one connection test — that cleanly separates the Wi-Fi network from the laptop’s wireless adapter.
- Move closer to the Wi-Fi access point or restart the access point itself; intermittent wireless can show up as a “VPN drops every 10 minutes” symptom even though the VPN is innocent.
5. Disable hibernation-sleep drop first
Microsoft’s Always On VPN overview documents that the Windows VPN client expects name-based triggering and trusted network detection to work even after the laptop sleeps — but those assumptions rely on drivers and the network stack being idle-aware.[1] A very common drop cause on Windows 11 is the wireless adapter going to sleep with the rest of the laptop, then failing to reconnect the tunnel cleanly afterward.
- Open Control Panel → Power Options → Change plan settings → Change advanced power settings.
- Expand Wireless Adapter Settings → Power Saving Mode and set it to Maximum Performance.
- Expand PCI Express → Link State Power Management and set it to Off.
- Expand Sleep → Allow wake timers and enable it (this lets the VPN client wake the network adapter when needed).
Practical caveat: These settings work for the current power plan. If you switch between “Balanced” and “Power saver” on the road, you may need to repeat them.
6. Mind the protocol — the failure modes are different
The Windows VPN platform ships four built-in tunneling protocols plus an Automatic option. Each one fails in different ways:[8]
Phone readers: swipe the table left to compare protocol-specific failure modes.
| Protocol | Common drop causes | First client-side check |
|---|---|---|
| IKEv2 | Rekey failure, certificate mismatch, NAT traversal blocked upstream. | Run an elevated Get-VpnConnection in PowerShell; verify the certificate under certlm.msc → Personal → Certificates has not expired. |
| L2TP/IPSec | Pre-shared key or certificate mismatch, NAT traversal requires a registry setting. | Confirm the pre-shared key or client certificate; KB 325034 documents the IPSec NAT-T requirements.[4] |
| SSTP | Blocked outbound TCP 443, captive portal, expired server certificate. | Verify the laptop can reach vpn.yourcompany.com on TCP 443 without the VPN profile. |
| PPTP | Deprecated; CISA and NSA recommend against it because the protocol has well-known weaknesses.[7] | Plan a migration to IKEv2 or SSTP with the IT owner; do not try to “fix” PPTP — replace it. |
| Automatic | Falls back to a less-preferred protocol when the first one fails; can mask the real cause. | Ask the IT owner for the explicit list to try, in order, before diagnosing. |
Practical ordering guidance: When in doubt, ask your IT owner which protocol the gateway supports. Always On VPN user tunnels support SSTP and IKEv2; device tunnels support IKEv2 only, with no SSTP fallback.[2][8]
7. Check for a recent cumulative update regression
Microsoft Q&A posts from 2026 show reproducible Always On VPN failures after specific cumulative updates, including the September 2026 KB5124008 rollup affecting certificate-based authentication on Windows 11 24H2/25H2. The documented signature is: VPN works, the rollup installs, Always On VPN stops working, uninstalling the rollup and rebooting restores it. Moderators recommended opening a Microsoft support case with RasClient/RasMan logs and pausing the rollup rollout until a fixed build ships.Microsoft Q&A thread (treated as timing context; not used as a load-bearing claim about your device).
- Open Settings → Windows Update → Update history and look at the last one or two installs.
- If the drop began within a day of a cumulative update, note the KB number but do not uninstall it on your own; unmanaged cumulative-update uninstalls are limited to ten days on Windows 11, and on managed devices only IT can authoritatively revert.
- Cross-check that the Windows 11 build is in a Microsoft-supported branch — Windows 11 26H2 is the current general-availability channel as of late September 2026 per our coverage.
8. Only now — and only if you own the profile — consider the narrowest repair
For a profile you created yourself, the narrowest repairs in order are: re-enter the pre-shared key (L2TP) or password, remove and recreate the built-in VPN profile under Settings → Network & internet → VPN, or run Windows’ msftconnecttest.net reachability check to confirm the DNS layer still works. Microsoft Support’s user guide walks through the GUI add/edit flow for a built-in profile.[9] For a vendor client (Cisco, Palo Alto, Fortinet, etc.), follow the vendor’s guidance; never blanket-uninstall the client and reinstall it without the gateway side information, because a different client bundle can overwrite a working managed profile.[2]
Practical change-control guidance: Network reset is documented as a last step — Microsoft’s network-reset page warns that VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] On a managed work device, schedule that with IT so the profile can be re-issued in the same window.
Good fixes and bad shortcuts
Good
- Record the exact error and timestamp before changing anything.
- Read RasClient and RasMan Event Viewer logs.
- Run Network Adapter and Internet Connections troubleshooters first.
- Test the same credentials from a second network (wired Ethernet or phone hotspot).
- Disable Wi-Fi power-saving on the wireless adapter.
- Ask IT to roll the tunnel to IKEv2 if the gateway supports it.
- Plan a migration away from PPTP — CISA and NSA both recommend against it.[7]
Bad
- Run Network reset on a managed work device without coordinating with IT.
- Uninstall a vendor VPN client on a managed device.
- Open TCP 443 or UDP 500/4500 on the home router “so the VPN can get through.”
- Edit the
AssumeUDPEncapsulationContextOnSendRuleregistry on a work laptop without documentation. - Type VPN credentials into a chat, screenshot, or email.
- Disable the firewall or antivirus “to see if that’s the problem.”
- Assume the VPN is broken because the Wi-Fi is bad.
Two realistic examples
Harmless misalignment: Wi-Fi power-save killing the tunnel
Illustrative example: A remote worker says the VPN drops every 20 to 40 minutes, only on the home Wi-Fi. The Event Viewer logs show repeated Remote Access Connection Manager events flagged as link state changes. The wireline adapter is fine; the Wi-Fi adapter was set to Power Saving Mode on the Balanced plan. Changing the adapter power setting to Maximum Performance on the home and current power plans keeps the tunnel stable for the full work day. The VPN client was never the problem.
Costly wrong turn: Network reset on a managed work device
Illustrative caution: A managed Windows 11 device has an Always On VPN profile delivered by Intune and a third-party EDR client. The user runs Settings → Network & internet → Advanced network settings → Network reset “to fix the VPN.” Network reset removes and reinstalls every network adapter and resets every network setting — including the Always On VPN tunnel and any third-party VPN client. Microsoft’s troubleshooting guidance explicitly warns that VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] The user now has a worse problem, and IT has to reissue the profile. Coordinate first.
Frequently asked questions
Does a “Connected” indicator mean the tunnel is actually working?
Not always. Microsoft documents that Always On VPN connectivity features — trusted network detection, name-based triggering, and name resolution via the Name Resolution Policy Table — can succeed while the authentication step later fails.[1] Confirm with one named resource behind the VPN, not by the tray icon.
Should I switch to PPTP because it’s the only option that “just works”?
No. Microsoft lists PPTP as one of the four built-in protocols but CISA and NSA’s hardening guidance explicitly recommends against relying on PPTP because of well-known weaknesses.[8][7] Ask your IT owner for IKEv2 or SSTP — those are the modern options.
Will running Network reset fix the VPN?
Sometimes, but at a high cost. Microsoft Q&A respondents and Microsoft’s own network-reset page treat it as a last-step option because it removes installed adapters and their settings, then reinstalls them with defaults — VPN client software and virtual switches may need to be reinstalled or set up again afterward.[6] Run the troubleshooters and read the logs first; only invoke Network reset on a device you own end-to-end.
Why does the VPN stay up on another laptop but not on mine?
That is comparison evidence pointing at your device, its profile, its adapter, or its update state. Check that you and the other laptop are connecting to the same gateway with the same protocol, and verify your Windows 11 build matches. If yours is a managed device, ask IT whether your device has the same Always On VPN profile payload as the working one.[2]
Can I test the VPN gateway over the public internet without going through the tunnel?
Yes — and that is a useful step. SSTP uses TCP 443; IKEv2 typically uses UDP 500 and UDP 4500 with NAT traversal. Confirm the gateway hostname is reachable on those ports and resolves to the IP your IT group gave you before the VPN profile is connected. If you can’t reach the gateway at all, the drop isn’t a Windows client problem.
Related guides from The IT Guys
- Remote Access Broke After a Router Upgrade? Check Double NAT and CGNAT — use this when the failure is on the carrier or router side rather than the Windows client.
- Is Remote Desktop Open to the Internet? Close Port 3389 and Use an Approved Remote-Access Plan — use this when Remote Desktop and VPN together are the workflow.
- Connected but No Internet? A 169.254 Address Points to DHCP, Not a Broken NIC — use this when the VPN works, but only certain name lookups fail.
- Weak Cell Signal Indoors? Set Up Wi-Fi Calling — and Fix the 911 Address — use this when the laptop loses both Wi-Fi and the cellular fallback.
Your next action
Capture the exact VPN error and timestamp. Open Event Viewer and read RasClient and RasMan. Run the Network Adapter troubleshooter. If this is a managed work device and the troubleshooter, log review, and adapter power settings don’t identify the cause, contact The IT Guys with the error, the KB number of the most recent cumulative update, and an export of the two logs — never send us a password, certificate, or session key.
Sources
- Microsoft Learn: About Always On VPN for Windows Server Remote Access — accessed October 21, 2026.
- Microsoft Learn: Tutorial — Create Always On VPN Connection on Windows Client Devices — accessed October 21, 2026.
- Microsoft Learn: VPN authentication options in Windows — accessed October 21, 2026.
- Microsoft Learn: Troubleshoot L2TP/IPSec VPN client connection (KB 325034) — last updated February 12, 2026.
- Microsoft Learn Q&A: Always On VPN disconnections — RasClient and RasMan event-log pointers — accessed October 21, 2026.
- Microsoft Learn Q&A: Persistent network connection drops in Windows 11 — accessed October 21, 2026.
- CISA + NSA: Selecting and Hardening Remote Access VPN Solutions — accessed October 21, 2026.
- Microsoft Learn: VPN connection types (IKEv2/L2TP/PPTP/SSTP/Automatic) — accessed October 21, 2026.
- Microsoft Support: Connect to a VPN in Windows — applies to Windows 10 and Windows 11, accessed October 21, 2026.
