Fix it now
Microsoft publishes 741 as the local computer not supporting encryption and 742 as the remote server not supporting it. Neither is a credential problem and neither means the tunnel is insecure. The usual cause is a connection asking for point-to-point encryption on a tunnel type that does not use it, or an authentication method that cannot produce encryption keys at all.
ncpa.cpl
- Right-click the VPN connection, choose Properties and open the Security tab. Note two things: the tunnel type, and the position of the Data encryption list.
- If the tunnel type is an IPsec-based one, move the Data encryption list off its strongest position. The strongest setting asks for point-to-point encryption, which IPsec tunnels do not use, so it can never be satisfied.
- Check the authentication method on the same tab. Point-to-point encryption keys come out of the authentication exchange, so a method that verifies the password without producing key material makes encryption impossible however the list is set.
- On the policy server, open the network policy that matches these connections and check its encryption settings, so the strengths your clients offer are among the ones it accepts.
- Reconnect and confirm the connection completes rather than failing at the same point.
Never solve this by permitting an unencrypted connection. On an IPsec tunnel that setting refers to a second layer that is not in use, but on a link-encrypted tunnel it sends credentials and traffic across the internet in the clear.
If the connection completes you can stop here. If it does not, the next section explains where encryption is negotiated and why the two ends are disagreeing.
Why it happens
A remote access connection can be encrypted in two quite different places. The older mechanism is point-to-point encryption, negotiated as part of the link setup and used by PPTP. The modern mechanism is IPsec, which encrypts the tunnel before any link negotiation happens at all, and is what L2TP and IKEv2 use. Asking for point-to-point encryption on an IPsec tunnel is asking for something that is not there, which is exactly what the strongest position in the Data encryption list does.
Point-to-point encryption also depends on the authentication method, because its keys are derived from the credentials exchange. A method that carries or verifies the password without producing key material cannot support it at all. That is why changing the authentication method to something simpler, in an attempt to get a stubborn connection working, so often turns a credentials error into 741 instead.
The policy server has a view of its own. Each network policy carries encryption settings listing which strengths it will accept, and if the client’s offer is not among them the connection is refused even though both machines are perfectly capable. Where every client fails at once and nothing changed on the clients, that list is the first place to look, and the policy that matched is not always the one you assume.
Two of the companion codes belong to a different stage. Microsoft publishes 734 as the PPP link control protocol terminating and 733 as the PPP control protocol for a network protocol not being available on the server. Both mean the two ends got as far as negotiating the link and could not complete it, so they point at protocol configuration rather than at encryption strength.
The strongest encryption setting on a tunnel that does not use it
You have this one if An IPsec-based connection fails at 741 immediately, and moving the Data encryption list one position down makes it work.
- On the Security tab, move Data encryption off its strongest position for IPsec-based tunnels.
- Set the tunnel type explicitly rather than leaving it automatic while you test, so you know which one is being negotiated.
- Reconnect, then confirm the tunnel is still encrypted – it is, by IPsec, before the link is negotiated.
Weakening the list is a diagnostic step on an IPsec tunnel and a real weakening on a link-encrypted one. Know the tunnel type before you touch it.
The authentication method cannot produce encryption keys
You have this one if Encryption is required and the only methods enabled are ones that carry the password without generating key material.
- On the Security tab, enable a challenge-based or certificate-based method that produces key material.
- Match the same method in the network policy on the server, so both ends agree.
- Reconnect, then remove the weaker methods from both ends once it works.
The policy will not accept what the client offers
You have this one if Every client fails at once, shortly after somebody edited a network policy, and nothing changed on the clients.
- Open the matching network policy on the policy server and review its encryption settings.
- Accept the strengths your clients actually offer, and remove the no-encryption option entirely.
- Confirm which policy is matching before editing, since the first policy whose conditions match is the one that applies.
The server requires encryption the client is configured to refuse
You have this one if Error 743, with the client set to allow no encryption.
- Change the client to require encryption, which is what the server is insisting on.
- Check whether a management tool or a deployed profile applied that setting, and fix it at the source rather than machine by machine.
- Reconnect and confirm the connection completes.
The link negotiation fails for a neighbouring reason
You have this one if 734 or 733 rather than 741, meaning the two ends negotiated and could not finish.
- Check the required network protocol is enabled both in the connection’s networking settings and in the server configuration.
- Read the server’s remote access log for the same attempt, which identifies the stage that failed.
- Where a third-party client or an appliance is involved, compare its settings against a Windows client that works.
Full reference
What each of the five codes is published as
| Code | Published meaning |
|---|---|
| 741 | The local computer does not support encryption |
| 742 | The remote server does not support encryption |
| 743 | The remote server requires encryption |
| 734 | The PPP link control protocol terminated |
| 733 | The PPP control protocol for this network protocol is not available on the server |
Read 741 and 742 as statements about capability, not preference. The machine named in the code cannot provide what the connection has been configured to require, and the fix is to change the requirement or change the method that would supply it – not to force the same demand harder.
Which layer is actually protecting the traffic
| Tunnel type | Where encryption happens | What the Data encryption list controls |
|---|---|---|
| PPTP | Point-to-point encryption, negotiated during link setup | The real protection on the connection |
| L2TP over IPsec | IPsec, before the link is negotiated | A second layer that is not in use |
| IKEv2 | IPsec, before the link is negotiated | A second layer that is not in use |
| SSTP | TLS, before the link is negotiated | A second layer that is not in use |
This table is the whole article in five rows. On the bottom three, moving the Data encryption list down does not reduce the protection on the tunnel, because the tunnel was encrypted before that negotiation began. On the top row it does, and on the top row you should be reading article 497 about retiring PPTP instead.
Where each setting lives
| Setting | Where |
|---|---|
| Tunnel type and Data encryption | The VPN connection’s Properties, Security tab, on the client |
| Authentication methods offered | The same Security tab |
| Authentication methods permitted | The matching network policy, Constraints, on the policy server |
| Encryption strengths permitted | The matching network policy, Settings, on the policy server |
| Which policy matched | The Network Policy Server event in Windows Logs, Security |
Diagnosing it from two machines at once
- Fix the tunnel type explicitly on one test client, so nothing is being negotiated behind your back.
- Connect, and read the policy server event for that attempt before touching a setting.
- If the event names a policy, edit that policy. If it names none, your problem is policy matching and not encryption.
- Change one thing, retest, and write down what you changed. Encryption faults produce identical symptoms from three different causes and it is easy to lose track.
- Once it works, put anything you loosened for testing back, on both ends.
What not to do
- Do not enable every authentication method on both ends. It will often produce a working connection and it leaves the weakest method available afterwards.
- Do not set the client to allow no encryption to get past 743. That is the server telling you it insists on protection, and it is right.
- Do not change the policy for everyone to fix one client. Confirm which policy matched first; it is frequently not the one whose name suggests it.
- Do not assume the tunnel is unencrypted because you moved the Data encryption list. On an IPsec or TLS tunnel that list refers to a layer that is not carrying your traffic.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
741 |
The local computer does not support encryption | Microsoft Learn |
742 |
The remote server does not support encryption | Microsoft Learn |
743 |
The remote server requires encryption | Microsoft Learn |
734 |
The PPP link control protocol terminated | Microsoft Learn |
733 |
The PPP control protocol for this network protocol is not available on the server | Microsoft Learn |
Confirm the fix worked
- Reconnect and confirm the connection completes without an encryption error.
- On the server, confirm the session appears with the tunnel type and encryption strength you intended.
- Read the policy server event for that connection and confirm the policy you expected is the one that matched.
- Test from a second client, to prove the fix was in the policy or the profile rather than on one machine.
- Confirm no client has been left configured to allow an unencrypted connection.
Questions people ask about this
Is there anything to buy to fix this?
No. Every setting involved is part of Windows on the client and part of the remote access and policy roles on the server. This is a mismatch to correct, not a capability to purchase.
If I lower the Data encryption setting, is my traffic unprotected?
On an IPsec or TLS-based tunnel, no. Those tunnels are encrypted before the link is negotiated, so that setting refers to a second layer that is not in use. On PPTP it matters, which is why you need to know the tunnel type before changing it.
Why did this start after a change on the server?
Encryption strengths are listed per network policy. Editing a policy, or adding one that matches ahead of the existing one, changes what clients are allowed to offer and can break every connection at once.
Should I enable every authentication method to be safe?
No. Enabling weak methods to get a connection working leaves them available afterwards. Agree on one strong method both ends support and turn the rest off on both sides.
I get 742 rather than 741. Does that change the fix?
It changes which machine you look at. 741 is published as the local computer not supporting encryption and 742 as the remote server not supporting it, so 742 sends you to the server’s configuration and to the matching network policy rather than to the client’s Security tab.
