Fix it now
These three numbers come from the Windows remote access layer, and Microsoft publishes what each means: 691 is credentials refused, 720 is no PPP control protocols configured, 813 is a second connection attempted while the first still holds the device or port. Norton’s own remedy for a VPN that will not connect is to reinstall the client.
- Confirm your Norton plan actually includes the VPN and that the app is signed in to the account holding it. Not every tier includes one, and what is bundled varies by market.
- Sign out of the Norton account in the app and back in. A stale sign-in produces a credential refusal even though you never typed a password.
- Open Settings, Network & internet, VPN and remove leftover entries from products you no longer use. 813 clears with a restart once nothing else holds the port.
- Disconnect every other VPN client, restart, and connect once before opening anything else.
- If it still fails, follow Norton’s published remedy: uninstall Norton VPN on this device and reinstall it.
- Test on a phone hotspot. Connecting there puts the fault on the network you were on rather than on the PC.
Norton now publishes the product as Norton VPN. The older Secure VPN name is still what appears on many installations and in most searches, and the troubleshooting is the same.
If the tunnel comes up and survives a reconnect you are done. If not, the next section explains what each number is actually reporting.
Why it happens
Norton VPN does not implement its own dial-up stack. Where the connection runs through the Windows remote access components, the failures surface as classic RAS error numbers that predate consumer VPNs by decades. Those numbers are precise, and the precision is useful once you know what each layer does – but they are Microsoft’s codes, not Norton’s, which is why Norton’s own support page for a VPN that will not connect names no codes at all and simply tells you to reinstall the client.
Authentication is handled for you. The client obtains a session credential from Norton on the strength of your account and subscription, then presents it to the gateway. So a 691, which Microsoft publishes as access denied because the user name, password or both is not valid, almost never means a password you typed. It means the credential the client presented was refused, and the usual reason is that the account is not signed in properly or the entitlement behind it is not current.
720 is the one most often mis-explained. Microsoft’s published text is short and specific: no PPP control protocols are configured. That is the negotiation failing to agree on anything to carry, not a licence problem and not a server problem. Rebuilding the WAN miniport adapters is the field remedy people reach for and it frequently works, but Microsoft does not publish that link – treat it as a thing to try rather than as the documented cause.
813 is the most literal of the three: you have attempted to establish a second broadband connection while a previous one is already established using the same device or port. A restart clears it, and if it comes back immediately, something is reconnecting on its own.
The plan does not cover the VPN, or the app is not signed in
You have this one if 691 on every network, including a phone hotspot, while the antivirus side of Norton works normally.
- Sign in to your Norton account and read which products your subscription includes, not merely that it is active.
- In the Norton app, sign out and back in with that account.
- If the VPN is not part of your plan, move to a tier that includes it or use a separate VPN. No client-side change conjures an entitlement.
The PPP negotiation agrees on nothing
You have this one if 720 on every network, and often other VPN clients on the same machine fail too.
- Follow Norton’s published route first: uninstall Norton VPN on this device and reinstall it.
- If it persists, open Device Manager, choose View then Show hidden devices, and expand Network adapters.
- Uninstall the WAN Miniport entries one after another, then choose Action, Scan for hardware changes, or simply restart. Windows recreates them.
- Reconnect once the machine is back up.
Removing those adapters is safe in the sense that Windows rebuilds them, but do it when you can restart – not in the middle of a call, and never on a machine you can only reach remotely.
A previous connection still owns the port
You have this one if 813 immediately after an attempt that failed or was cancelled, and a restart buys you one clean try.
- Open Settings, Network & internet, VPN and disconnect anything showing as connected or connecting.
- Remove duplicate or stale VPN entries left by other products.
- Restart, connect once, and let it complete before pressing anything else.
The network blocks the tunnel
You have this one if It connects on a phone hotspot and fails at the office, a hotel or a school.
- Ask the network owner to permit the outbound ports the tunnel needs. Microsoft’s Always On VPN guidance names UDP 500 and 4500 being blocked as the cause of the timeout class of failure on IPsec-based connections.
- Enable VPN passthrough on your own router if it exposes the setting.
- Accept that many managed networks block consumer VPNs deliberately, and take it up with whoever runs the network rather than looking for a workaround.
The installation is damaged
You have this one if Everything above checks out and the client still fails identically on every network.
- Uninstall Norton VPN and reinstall it, which is exactly what Norton’s own support page prescribes.
- Restart between the two halves rather than installing straight over the top.
- Sign in with the account that holds the subscription and connect once before launching anything else.
Full reference
What Microsoft publishes for each number
| Code | Microsoft’s published meaning | Practical reading |
|---|---|---|
691 |
Access denied because the user name, password, or both is not valid on the domain | The session credential the client fetched was refused – look at the account and the entitlement |
720 |
No PPP control protocols are configured | The negotiation agreed on nothing to carry; reinstall, then rebuild the WAN miniports |
813 |
You have attempted to establish a second broadband connection while a previous broadband connection is already established using the same device or port | Something else still owns the port; disconnect it or restart |
The third column is interpretation, not vendor text, and it is worth keeping the two apart. Microsoft publishes the middle column. Everything about miniport drivers and stale session credentials is field practice built on top of it.
Working out which one you have
| Code and behaviour | Where to look |
|---|---|
| 691, on every network | Account sign-in state or VPN entitlement |
| 720, on every network | The client installation, then the WAN miniport adapters |
| 813 after a failed attempt | A previous connection still holds the device; restart |
| Any of them on one network only | That network blocks the tunnel |
| Started after removing another VPN product | Leftover adapters or connection entries |
If you go on to reset the network stack with netsh winsock reset and netsh int ip reset, understand that these reset network configuration to defaults and require a restart. Write down any manual network configuration first, and do not run either on a machine you cannot get back to physically.
What Norton actually publishes for this
Norton’s support page for being unable to connect to the VPN gives one remedy: uninstall and reinstall Norton VPN on the device, with platform-specific steps for Windows, Mac and iOS, and an extra step on iOS to update the app first. It names no error codes. That is worth knowing before you spend an afternoon on driver archaeology – the vendor’s own answer is short, and it is the first thing to try after the account check.
Checking the entitlement rather than assuming it
- Sign in to your Norton account and open My Subscriptions.
- Read the product list attached to your subscription, not just its status. An active subscription tells you nothing about whether the VPN is in it.
- Confirm this device is listed under Manage Devices for that subscription.
- In the app, sign out and back in with the same account, then connect.
What is bundled differs by tier and by the market a plan is sold in, so a comparison chart written for another country is not evidence about your subscription. Norton publishes only that most plans allow protection on 3, 5 or 10 devices depending on the plan, and points at the store for product specifics.
When it is not worth fixing
If the VPN is not part of your plan, no amount of adapter rebuilding produces one, and that is a purchase decision rather than a troubleshooting one. If it is part of your plan and the tunnel still will not build after a reinstall and a hotspot test, the fault is either the network you are on or the gateway, and both are somebody else’s to fix.
When a licence is the actual fix
If the sticking point is entitlement rather than plumbing, no client-side work will help: the VPN has to be part of the plan your account holds, and an active antivirus subscription is not evidence that it is. Norton sells tiers that bundle its VPN with the rest of the suite, including Norton 360 with LifeLock Select, and both the VPN and the identity features attached to those tiers vary by country. Arco will tell you which Norton 360 tier is sold in your region, whether the VPN is included in it, and how many devices it covers, before you buy rather than after. If My Subscriptions already lists the VPN against your plan, this is a technical fault and there is nothing here to purchase – start with Norton’s own remedy, which is to uninstall and reinstall the client.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
691 |
Access denied because the user name, password, or both is not valid on the domain | Microsoft Learn |
720 |
No PPP control protocols are configured | Microsoft Learn |
813 |
A second broadband connection was attempted while a previous one is already established using the same device or port | Microsoft Learn |
Confirm the fix worked
- The VPN app reports a connected state with a named region.
- A site that reports your public IP address shows the VPN endpoint rather than your own connection.
ipconfig /allshows the virtual adapter with an address assigned.- My Subscriptions lists the VPN against your plan and this device under Manage Devices.
- Disconnect and reconnect once to confirm the fix survives more than the first attempt.
Questions people ask about this
Why does it say my credentials were rejected when I never entered any?
Because the client fetches a session credential from Norton on your behalf. Microsoft publishes 691 as access denied because the user name, password or both is not valid – that refusal traces back to the account sign-in or the subscription behind it, not to anything you typed.
Does every Norton plan include the VPN?
No. What is bundled differs by tier and by the market a plan is sold in. Read the product list against your own subscription rather than relying on a comparison chart from another country.
Is it safe to uninstall the WAN miniport adapters?
Yes, in the sense that Windows recreates them on the next scan or restart. Do it when a restart is acceptable, and never on a machine you are connected to remotely. Note that Microsoft does not publish a link between those adapters and error 720 – it is field practice, and Norton’s own first remedy is to reinstall the client.
What does 720 actually mean?
Microsoft publishes it as ERROR_PPP_NO_PROTOCOLS_CONFIGURED: no PPP control protocols are configured. The two ends completed enough of the exchange to negotiate and agreed on nothing to carry.
Norton calls it Norton VPN now. Is that the same product?
Yes. The current support pages use Norton VPN; many installations and most searches still say Secure VPN. The connection errors and the published remedy are the same either way.
