Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

License Error 809

VPN error 809 and 800: IKE traffic blocked before the tunnel can open

11 min read Updated October 5, 2026 Networking, Sharing & Printing

Fix it now

The client sent its opening packets and nothing usable came back, so no credentials have been exchanged yet and nothing is wrong with the account. Microsoft publishes 800 as the VPN server being unreachable or the security parameters not being configured properly; 809 is the client’s own number for the same silence and Microsoft publishes no meaning for it.

Run these on the failing client, in an elevated PowerShell session

Get-Service IKEEXT, RasMan
Test-NetConnection vpn.example.com -Port 443
Get-NetFirewallProfile | Format-List Name,Enabled
  1. Both IKEEXT and RasMan must be running. A stopped keying service produces an instant failure with none of the pause you would expect while the client waits for a reply.
  2. The port test only tells you anything for a tunnel published over TCP. IPsec runs on UDP 500 and UDP 4500 and cannot be tested this way, so treat a TCP result as a statement about the path, not about IKE.
  3. Stop the endpoint security product’s firewall module for two minutes and retry. If the tunnel opens, you need a rule in that product, not a permanent exemption.
  4. Ask whoever runs the perimeter to permit UDP 500, UDP 4500 and the ESP protocol between the client networks and the VPN server.
  5. If the VPN server sits behind address translation, apply the registry value in the reference section on both the client and the server, and restart both.

Test the same account from a second network before changing anything on the client. Guest, hotel and mobile networks block IPsec often enough that a five-minute test can save an afternoon.

If the tunnel comes up you are done. If not, the next section covers what has to happen before a tunnel exists and which link in that chain is broken.

Why it happens

An IPsec-based VPN begins with a key exchange on UDP 500. If either end detects address translation on the path, both move to UDP 4500 and wrap the encrypted payload inside UDP so it survives translation. Without that move, the encrypted payload travels as ESP, which is a protocol in its own right with no ports at all, and which most consumer routers and a good many firewalls will not forward. 800 and 809 are what you get when none of that produced a reply.

Windows adds a restriction of its own. Microsoft states that by default Windows does not support IPsec NAT traversal security associations to a server that sits behind a NAT device, because of the way NAT devices translate traffic. A registry value under the policy agent service key relaxes it, and the detail people get wrong is that Microsoft’s own article puts that value on both the VPN client computer and the VPN server, with a restart on each.

Local security software matters more here than in most network faults, because it filters below the VPN client at the platform’s filtering layer. From the client’s point of view the packets simply disappear. That is how a machine can pass every connectivity test you throw at it and still fail to build a tunnel, and why the same account works from a colleague’s laptop on the same network at the same moment.

Endpoint security or the local firewall is dropping the key exchange

You have this one if The same profile and account work from another machine on the same network at the same time.

  1. Stop the product’s firewall module briefly and retry, to confirm the diagnosis rather than assume it.
  2. Write explicit rules for UDP 500, UDP 4500 and ESP rather than leaving protection off.
  3. Read the product’s own logs, which normally name the rule or module that dropped the traffic.

The VPN server is behind address translation

You have this one if Connections from inside the network succeed and every external client fails at the same point.

  1. Set AssumeUDPEncapsulationContextOnSendRule under the PolicyAgent service key on both the client and the VPN server, then restart both.
  2. Use 1 where only the server is behind a NAT device and 2 where both ends are.
  3. Confirm the firewall in front of the server forwards UDP 500 and UDP 4500 to it.

Prove it on one client first, then deploy the value through your management tool. Microsoft’s article is explicit that the value belongs on both machines, which is the step most write-ups drop.

The path blocks IPsec outright

You have this one if The tunnel fails on a guest, hotel or mobile network and works everywhere else.

  1. Prove it by testing from a different network, ideally a phone hotspot on another carrier.
  2. Publish an alternative tunnel that travels over TCP 443, which survives restrictive networks, and offer it as a fallback in the profile.
  3. Where the blocking network is one you control, permit UDP 500, UDP 4500 and ESP outbound.

A service the client needs is not running

You have this one if The failure is instant, with none of the pause you would expect while the client waits for an answer.

  1. Run Get-Service IKEEXT, RasMan and start anything stopped.
  2. Set both to start automatically. A disabled keying service is usually the work of a tuning script or an optimiser.
  3. Retry once both are running.

The two ends do not have a policy in common

You have this one if The failure changes to 13868, 788 or 792 once traffic is plainly reaching the server, or it fails only after a pause.

  1. Check that both ends expect the same authentication for the tunnel. A pre-shared key on one side and a certificate on the other will never agree.
  2. Compare the encryption and integrity proposals the server accepts with what the client offers.
  3. Where the server is an appliance rather than Windows, take its proposal list from the vendor’s documentation and match it exactly.

Full reference

The NAT traversal value, in full

Item Value
Key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent
Value name AssumeUDPEncapsulationContextOnSendRule
Type DWORD (32-bit)
0 The default. Windows cannot establish security associations with servers behind NAT devices
1 Windows can establish security associations with servers behind NAT devices
2 Windows can establish security associations when both the server and the client are behind NAT devices
Where On the VPN client computer and on the VPN server
After Restart the computer

Export the key before you change it, and expect a reboot on each machine. Turning a security product’s firewall off to test is fine for two minutes on one laptop; leaving it off, or telling users to disable protection whenever the VPN misbehaves, trades a working tunnel for an unprotected machine.

Working out which link is broken

What you see Where the fault is
Works on one laptop, fails on another on the same network Local firewall or endpoint security on the failing machine
Every external client fails, internal tests succeed Address translation in front of the server, or missing perimeter rules
Fails on one network only, a phone hotspot works That network blocks IPsec
Fails instantly with no delay at all A required service is stopped, or the profile points at nothing
The number changes to 13868, 788 or 792 Traffic is reaching the server and the two ends cannot agree a policy

What each companion code is telling you

These three are worth separating because they mean the traffic is getting through. 13868 is ERROR_IPSEC_IKE_POLICY_MATCH, published simply as a policy match error, and it is the one that says the two ends have no proposal in common. 788 is the L2TP connection failing because the security layer could not authenticate the remote computer, which is a certificate or key problem rather than a filtering one. 792 is the same connection failing because security negotiation timed out, which usually means one direction of the exchange is being dropped rather than both.

Ports and protocols to ask for by name

Tunnel What has to be permitted
IKEv2 or L2TP over IPsec UDP 500 and UDP 4500, plus ESP where no address translation is in the path
A tunnel published over TLS TCP 443 only, which is why it survives restrictive networks
PPTP TCP 1723 and the GRE protocol, which most networks now drop

Ask for these by name rather than asking for the VPN to be allowed. ESP is a protocol number, not a port, so a rule that forwards ports does nothing for it, and a request phrased as a port range will be met with a rule that cannot work.

When everything checks out and it still fails

  • Confirm the profile’s tunnel type is explicit rather than automatic while you test, so you know which one is being negotiated.
  • Check whether a management tool is pushing a VPN profile that overwrites the one you are editing.
  • On the server, confirm the tunnel type has free ports configured. An exhausted port pool produces a failure that looks like filtering.
  • Check the certificate on the server if the tunnel is certificate-authenticated, because an expired one fails before any user is involved.
  • Look at what changed. This error very rarely appears on a working estate without a firewall rule, an endpoint policy or a network address changing first.

When a licence is the actual fix

Rules, services and a registry value cost nothing, and for one laptop that is the whole answer. The recurring version of this problem is different: where every user can configure or switch off their own endpoint firewall, VPN faults like this reappear indefinitely, because the policy on one machine is never quite what it is on the next and the quickest fix a frustrated user finds is to turn protection off. Managed endpoint protection removes that. Policy is written once in a console and applied to every machine, exceptions are recorded rather than improvised, and the logs tell you which machine dropped what. ESET PROTECT Entry is the entry point for that model, pairing ESET’s business endpoint protection with central management, and Arco can size it to your device count. If you already run a managed product, write the rule in its console and buy nothing.

Every code this article covers

Code What it points at Source
809 Reported by the Windows VPN client when the connection attempt ends with no usable reply. Microsoft publishes no meaning for this number, so diagnose it by the path rather than by the digits not published by the vendor
800 Unable to establish the VPN connection. The VPN server may be unreachable, or security parameters may not be configured properly for this connection Microsoft Learn
13868 ERROR_IPSEC_IKE_POLICY_MATCH: policy match error. The two ends have no proposal in common Microsoft Learn
788 The L2TP connection attempt failed because the security layer could not authenticate the remote computer Microsoft Learn
792 The L2TP connection attempt failed because security negotiation timed out Microsoft Learn

Confirm the fix worked

  1. Connect and confirm the client receives an address on the internal range.
  2. Open an internal resource by name, which proves name resolution through the tunnel as well as routing.
  3. Reconnect from a second network, to confirm the fix is on the client or the server rather than on one path.
  4. Confirm the endpoint security product is fully enabled again, with the new rule in place rather than the module switched off.
  5. If you set the NAT traversal value, confirm it is present on both the client and the server and that both have been restarted.

Questions people ask about this

Which ports does the VPN actually need?

For an IPsec-based tunnel, UDP 500 and UDP 4500, plus the ESP protocol where address translation is not in the path. A tunnel published over TLS needs only TCP 443, which is why it survives networks that drop everything else.

Is the NAT traversal registry value safe?

It is Microsoft’s own documented answer for a VPN server behind a NAT device, and it relaxes a default restriction rather than switching security off. Apply it deliberately, put it on both the client and the server as the article requires, and record where you have deployed it.

Do I need to buy security software to fix this?

No. Windows Firewall rules cost nothing and are sufficient, and if your existing endpoint product has a console you can write the rule there. A managed product helps with the estate-wide version of this problem, not with the single laptop in front of you.

Why does it work from home but not from the office?

Almost always outbound filtering. Home routers pass IPsec by default; a managed network may not, and guest networks often block it deliberately.

Microsoft does not publish a meaning for 809. Does that matter?

Only in that you should not trust a page that gives you one. The number tells you the attempt ended without a usable reply and nothing more, which is why the diagnosis here is a sequence of tests on the path rather than a lookup.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Error 0x80070035: the network path was not found when opening a share Free Fix 0xC0000234 account locked out and other logon states that block shares License Error Windows cannot connect to the printer: error 0x0000011B and 0x00000709 Free Fix VPN error 868: the remote access server name could not be resolved
โ† Back to Knowledge Base