VPN connection

[StuartE_Zarahn]

Note: Please do not post Personally Identifiable Information like email address, personal phone number, physical home address, product key etc.

Issue abstract:No matter where the VPN is or the time of day I get this “Secure VPN Reconnecting. It might last 2 seconds

Detailed description:

Product & version number:

OS details:

What is the error message you are seeing?

If you have any supporting screenshots, please add them:

[bjm]

@StuartE_Zarahn

No matter where the VPN is or the time of day I get this “Secure VPN Reconnecting. It might last 2 seconds

Hello @StuartE_Zarahn
Welcome to the Norton Community!
Are you running Norton 360 for Windows or the standalone Norton VPN app?
Is “Secure VPN Reconnecting" persistent or occasional?
Is your Auto-Connect set to Always or Custom (any parameters)?
Are you Wi-Fi or Ethernet cable?

The 2-second reconnect loop usually means the secure VPN tunnel is dropping due to underlying network noise, strict leak-protection triggers, or a conflict with Windows network adapters.

1. Is the loop persistent or occasional? Does this happen continuously every single time you toggle the VPN on without exception (persistent), or does it happen in frustrating bursts but sometimes hold a stable connection (occasional)? A continuous loop points to a broken Windows driver or firewall rule block, while occasional bursts point to physical Wi-Fi drops or ISP packet loss.
2. Are any of your VPN protocols grayed out? Go to your Secure VPN Settings and look under the Protocol tab. If options like WireGuard or OpenVPN are grayed out, Windows has corrupted or blocked your underlying system drivers. If they are all active, your system files are healthy, and you should manually switch from Automatic to WireGuard or OpenVPN (TCP) to see if it stabilizes the line.
3. Is Auto-Connect set to Always or Custom? Under Auto-Connect, check if this is toggled to Always. If it is, the app will violently loop trying to force an unbroken tunnel during minor network dips. Try switching it to Custom to see if the loop breaks on your trusted home network.

If the underlying internet connection experiences even a tiny flash of network noise or a micro-drop in packets, a secure VPN tunnel will collapse instantly. Because Norton 360’s VPN or the standalone Norton Secure VPN app is hardwired to be incredibly strict, it immediately enters that hyper-aggressive 2-second reconnect loop trying to protect your data.

Since the base connection noise is likely triggering this within the Windows environment, let’s stabilize how Windows handles your network hardware to stop the drops:

1. Disable IPv6 in Windows (Highly Effective for Network Noise)
   Many internet service providers experiment with IPv6 routing, which introduces heavy “noise” and packet loss into VPN tunnels that primarily rely on IPv4 protocols. Disabling it forces a clean, unified path.

2. Press the Windows Key + R to open the Run box.

3. Type ncpa.cpl and hit Enter. This opens your Network Connections window.

4. Right-click your active connection (Wi-Fi or Ethernet) and select Properties.

5. In the list, scroll down and uncheck the box next to Internet Protocol Version 6 (TCP/IPv6).

6. Click OK to apply.

7. Flush the Windows Network Stack
   If your router or local network has accumulated DNS cache noise, it will keep dropping the VPN handshake.

8. Type cmd into your Windows search bar, right-click Command Prompt, and select Run as Administrator.

9. Type the following commands one by one, pressing Enter after each:

• ipconfig /release
• ipconfig /renew
• ipconfig /flushdns
• netsh winsock reset

3. Restart your computer.

4. Change Your DNS Servers
   Sometimes your ISP’s local DNS servers are unstable, causing micro-disconnects. Switching to a stable public DNS can quiet that noise.

5. Go back to ncpa.cpl (Network Connections), right-click your connection, and select Properties.

6. Double-click Internet Protocol Version 4 (TCP/IPv4).

7. Select Use the following DNS server addresses and enter:

• Preferred DNS server: 8.8.8.8 (Google DNS)
• Alternate DNS server: 8.8.4.4

4. Click OK

Are you on Wi-Fi, or can you test it with a temporary Ethernet cable to see if the noise drops?

1. Change the Norton VPN Protocol Settings
   By default, Norton utilizes an “Automatic” protocol selector. If it is trying to use an older protocol that conflicts with a recent Windows network adapter update, it will drop every 2 seconds.

• Open Norton 360 or the standalone Norton Secure VPN app.
• Navigate to the Settings (the gear icon) usually located at the top-right or inside the Privacy/VPN menu.
• Look for VPN Protocol Settings.
• Change it from Automatic to WireGuard.
• Note: If WireGuard is unavailable, try OpenVPN (TCP). TCP is slower than UDP but drastically more stable on connections prone to dropping.

2. Turn Off the VPN Kill Switch Temporarily
   The Kill Switch is designed to pull the plug on your entire internet if the VPN drops for even a millisecond. If your connection experiences tiny fluctuations, the Kill Switch can cause an aggressive reconnection loop.

• In the Secure VPN Settings, locate the Kill Switch toggle.
• Turn it Off.
• Check if the VPN settles down and stops the 2-second reconnect loop.

3. Check for Concurrency Restrictions
   If you run other software that modifies your network routing—such as a secondary corporate VPN (like Cisco AnyConnect or Check Point) or a third-party firewall—Norton will fight for control of the Windows network stack.

• In Norton’s VPN Settings, look for an option titled “Enable multiple active VPNs”.
• If it is disabled, turn it On. This permits Norton to coexist gracefully with other virtual network adapters on your Windows machine.

4. Fix Power Management on Your Network Adapter
   Windows frequently tells network hardware to go to sleep briefly to conserve power, which snaps the secure VPN tunnel instantly.

• Right-click the Windows Start button and select Device Manager.
• Expand the Network adapters list.
• Right-click your main Wi-Fi or Ethernet adapter (e.g., Intel Wireless, Realtek) and choose Properties.
• Go to the Power Management tab.
• Uncheck the box that says “Allow the computer to turn off this device to save power.” Click OK.

The precise interaction of the Custom parameters has a direct impact on the stability of a manually established VPN tunnel.

Understanding how these specific parameters behave under the hood explains why they can easily trigger the 2-second reconnect loop.

1. What the Custom Parameters Are
   When the master dropdown is set to Custom, Norton 360 acts as a passive network monitor. It checks every network packet passing through your hardware against four distinct criteria:

• Public networks: Flags networks where your machine shares a broadcast domain with unknown devices.
• Compromised networks: Flags networks actively showing signs of man-in-the-middle attacks or spoofing.
• Unsecured networks: Flags Wi-Fi networks completely lacking standard password encryption (WPA2/WPA3).
• P2P: Flags when your device initiates peer-to-peer torrenting protocol traffic.

2. How These Parameters Directly Affect Stability
   If you turn ON any of these sliders, Norton gives those specific parameters priority over your manual choices. This causes a fundamental stability conflict in two ways:

• The Local Network Profile Conflict: If you toggle the Public networks or Unsecured networks slider to ON while sitting on your home Wi-Fi, Norton will constantly run network background scans to verify the network profile status. If Windows experiences a momentary drop in network packets, Norton will momentarily misidentify your home Wi-Fi as “unsecured” or “unknown”. It will immediately rip down your manual VPN tunnel to force a brand new, policy-compliant tunnel based on that auto-trigger rule—instantly starting the 2-second reconnect loop.
• The P2P Threshold Spike: If the When connecting P2P parameter is turned ON, Norton aggressively monitors network sockets for torrent behavior. Because many standard Windows applications (like background Windows Updates) utilize decentralized peer-to-peer architectures to distribute data, Norton can misinterpret standard Windows background noise as a P2P trigger. It drops the existing manual tunnel to force open a dedicated P2P-optimized VPN server, throwing the client into a connection loop.

Summary of Stability
Keeping the master setting on Custom with all toggles turned completely off is the most stable configuration for manual use. It strips away all background network monitoring rules, ensuring that Norton will never drop or cycle your manual VPN connection based on ambient network changes.

1. Extreme Sensitivity (The Trigger)
   Norton’s VPN is built to prioritize data security above user convenience. It monitors your internet connection at a microscopic level. If your local Wi-Fi drops a single data packet due to brief background noise or a tiny routing hiccup, Norton’s code immediately treats it as a critical security threat (like a data leak or a compromised network step). It pulls the plug on the secure tunnel instantly.

2. Aggressive Behavior (The Action)
   Once the hyper-sensitive trigger snaps the connection shut, Norton’s background engine immediately takes over. Instead of waiting a few seconds to let the underlying network noise pass, the application demands an immediate secure connection. It fires off an instant reconnection request to the server, fails if the line noise is still present, drops, and tries again exactly 2 seconds later.

Summary
The sensitivity is what causes the VPN to drop in the first place, while the aggressive zero-delay programming is what locks it into that continuous, rapid flashing cycle instead of letting your PC’s network card quietly stabilize.

Manually switching from Automatic to a protocol like WireGuard or OpenVPN (TCP) fixes this issue by essentially lowering that extreme sensitivity. Those protocols are naturally designed to handle minor data packet fluctuations smoothly, allowing the VPN tunnel to absorb the network noise without instantly panicking and entering a loop.

• Configure settings in Norton VPN
• Learn more about Auto Connect and Reconnect after restarting features in Norton VPN

When you break down how network data actually flows, each of these conditions forces the hyper-sensitive Norton software to panic and tear down the connection.

1. Unstable Wi-Fi Connection (The Most Common Trigger)
   Wi-Fi inherently suffers from ambient environmental interference. If your router shifts your device between the 2.4 GHz and 5 GHz bands, or if a neighbor’s Wi-Fi channel overlaps with yours, a burst of packet loss occurs.

• What Norton Does: Norton’s VPN sees that data packets have stopped arriving for a split second. Fearing that your true IP address is about to leak onto the public web, it forces the secure tunnel shut instantly and shifts into the aggressive 2-second reconnect cycle.

2. Noise on a Stable Ethernet Connection (The Sneaky Trigger)
   Even a physical Ethernet cable can suffer from network “noise.” This doesn’t mean the cable is broken; it refers to data congestion or conflicts at the software level. For example, if your router experiences a micro-second DHCP lease renewal glitch or an IPv6 routing conflict, the physical line stutters.

• What Norton Does: Even though the physical link is solid, the data stream itself becomes momentarily corrupted. The VPN treats this data corruption as a handshake failure, drops the tunnel, and continuously tries to rebuild it.

3. Smart Firewall Profile Flipping (The Logic Trigger)
   Windows and Norton’s Smart Firewall constantly monitor your local network profile to classify it as Private (trusted) or Public (untrusted/secure). If a Windows update or a driver refresh glitches, Windows may suddenly drop your home network profile and re-classify it from Private to Public.

• What Norton Does: The second the Smart Firewall detects that the underlying network profile has flipped, it re-evaluates all active security rules. This sudden shift forces the active VPN adapter to reset its routing tables to match the new profile, causing the existing tunnel to snap and putting the app into a 2-second reconnecting tailspin while it tries to sort out the rules.

It really is a massive jigsaw puzzle under the hood. When you use a VPN, you aren’t just running a regular app; you are running a piece of software that essentially tries to completely hijack your computer’s internet architecture to rebuild a secure pipeline.

Because of that, the VPN is constantly trying to balance and stay in perfect sync with a dozen moving parts at the exact same time:

• Your Physical Hardware: The actual Wi-Fi chips, Ethernet ports, and the router sitting on your shelf.
• The Windows OS Layer: Power management modes, network adapter drivers, and fluctuating IP profiles (Private vs. Public).
• The Security Software Engine: Hardwired data-leak protection rules, the Smart Firewall, and real-time socket monitoring.
• The External Server: Physical distance, ISP routing pathways, and server handshake protocols.

If even one of those components takes a microscopic break or hits a tiny hiccup, the whole house of cards collapses, and the VPN panics into that 2-second loop to protect your data.

The good news is that by keeping Auto-Connect set to Custom with all parameters turned off, you have turned off one of the biggest, most chaotic moving parts in the system. Your Norton app is no longer trying to constantly analyze your network profiles, which heavily stabilizes the software.

On a trusted, secured home network, a VPN is rarely necessary for day-to-day security.

The primary job of a VPN is to protect your data from bad actors sitting on the same network as you—which is why it is absolutely vital on public, unencrypted, or sketchy Wi-Fi networks (like at a coffee shop, airport, or hotel).

At home, you already control the environment:

• Your Wi-Fi is protected by your own password encryption (WPA2 or WPA3).
• Your modern home router has a built-in hardware firewall.
• Almost every website you visit now uses HTTPS encryption anyway, meaning your passwords, credit cards, and banking data are already fully encrypted between your browser and the website, even without a VPN.

When would you turn it on at home?

If you choose to leave it off at home to avoid the 2-second reconnect loop headache, you aren’t really missing out on core security. The only reasons to manually switch it on at home are for privacy preferences, such as:

• Hiding browsing traffic from your ISP: Preventing your Internet Service Provider from logging which websites you visit.
• Bypassing geo-restrictions: Changing your virtual region to access streaming content or websites blocked in your country.

On a secure home network, you can comfortably leave the Norton VPN toggled Off. It saves your computer from fighting that endless loop of moving parts, and your data remains perfectly safe behind your home router and Norton 360.

AI sourced content may make mistakes

[bjm]

Hello @StuartE_Zarahn
Care to share your progress

[bjm]

~ may be related:
https://community.norton.com/t/norton-vpn-keeps-disconnecting-and-connecting/529422

Norton VPN stays at “Connecting” and returned to disconnected state

[bjm]

Hello @StuartE_Zarahn
Care to share your progress