Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Windows Error 734, “The PPP link control protocol was terminated,” means the Point-to-Point Protocol (PPP) link failed during Link Control Protocol (LCP) negotiation. Windows and the remote peer could not agree on the connection parameters, so the session stopped before normal network traffic could begin. For a dial-up connection, first clear Negotiate multi-link for single link connections; if that does not work, review the connection’s security setting and allow an unsecured password only when the peer requires it. For an L2TP VPN, also investigate the VPN gateway, tunnel state, and the network path between the PC and gateway.
What Error 734 actually means
PPP is used by several kinds of point-to-point connections, including traditional dial-up, some cellular or WWAN links, and Windows’ native L2TP VPN client. Before PPP can carry IP traffic, its Link Control Protocol negotiates link parameters with the peer. Error 734, internally identified as ERROR_PPP_LCP_TERMINATED, says that this negotiation was terminated.
As an Amazon Associate I earn from qualifying purchases.
That wording is an outcome, not a complete diagnosis. It does not prove that a modem, cable, network adapter, or VPN server has failed. The peer may have rejected an option Windows proposed, Windows may require an authentication method the peer does not support, or a network device may be preventing the VPN session from completing. The correct fix depends on the connection type and on which negotiation stage failed.
Microsoft’s documented dial-up causes are particularly specific: a multi-link negotiation option can be enabled for a connection that has only one physical link, or the security setting can require a secured password that the remote peer cannot provide. Those are the first settings to check before replacing hardware or reinstalling networking components.
#1 Best Overall
- DIAL-UP & FAX SUPPORT: Hardware-based USB 2.0 Fax modem adds data and fax functionality to your computer / laptop via USB without putting additional load on your CPU; For faxing, rural internet access, security systems, POS credit authorization
- VOICE AND CALLER ID SUPPORT: Make and receive phone calls through your desktop / laptop computer; This portable USB modem supports Caller ID functionality and is compatible with most dial-up ISP (Internet Service Provider) networks
- DATA/FAX MODE SUPPORT: Data: V.92, V.90, V.34, V.32bis, V.32, V.22bis, V.22, V.23, V.21 Bell 212A & Bell 103; Fax: V.17, V.29, V.27, V.21 Ch 2, EIA/TIA 578 Class 1 and T.31 Fax Class 1.0; DTMF support
- TECH SPECS: External 56K Modem; Data Fax; USB Type A; 1 x RJ11 Telephone Jack; 56 Kbps Down, 33.6 Kbps Up Data; 14.4 Kbps Fax V.92; V.44 Compression; Conexant CX93010-21Z; USB Powered; TAA Compliant
- COMPATIBILITY: Drivers available for Windows, Windows Server, macOS (10.9 to 12.x) and Linux (kernel 3.16 and up); Windows Drivers available for download
Identify the connection before changing settings
Use the row that matches the connection producing the message. The location of the evidence and the likely corrective action differ by connection type.
| Connection type | What PPP is negotiating | First place to inspect | Additional evidence |
|---|---|---|---|
| Single-link dial-up | A single modem link and its authentication parameters | The affected connection’s Properties, Networking settings, and Security settings | Whether multi-link negotiation is enabled and whether the password requirement matches the peer |
| Cellular or WWAN PPP | A point-to-point session over the carrier connection | The carrier or device connection profile and its PPP authentication choices | Whether the peer accepts the proposed negotiation; the exact device software may use different labels |
| Windows native L2TP VPN | PPP inside an L2TP tunnel, with the VPN gateway acting as the peer | The Windows VPN profile and its authentication/security choices | VPN gateway tunnel and session status, plus firewall or router treatment of required traffic |
If you are unsure, note when the error appears. A dial-up prompt that fails immediately points you toward the connection Properties. A VPN profile that reaches a server and then reports Error 734 requires both client-side checks and gateway or path checks.
Microsoft’s repair sequence for dial-up Error 734
Microsoft’s support material uses legacy Windows menu names. Windows 10 and Windows 11 may expose the same controls through a different Settings page, the classic Network Connections window, or a connection-specific Properties dialog. The labels below are the important part; use the current Windows route that opens the affected connection’s Properties.
- Open the affected connection’s Properties. Select the dial-up connection that produces Error 734 rather than changing an unrelated adapter.
- Open the Networking tab and select Settings. This opens the PPP options associated with that connection.
- Clear “Negotiate multi-link for single link connections.” This option is inappropriate when the connection has only one link. Clearing it prevents Windows from proposing a multi-link arrangement that the peer cannot accept.
- Save the change and retry. Disconnect first if Windows leaves a partial session, then make one fresh connection attempt.
- If the error remains, open the Security settings. Look for the validation choice that requires a secured password.
- Allow an unsecured password only if the peer requires it. Save the setting and retry. Do not change this merely because it is an available option; it changes the authentication requirement and should match the service’s documented policy.
These two checks address the specific incompatibilities Microsoft identifies for this error. If neither changes the result, restore any setting that was changed unnecessarily and continue with the connection-type diagnosis rather than repeatedly toggling unrelated options.
Why the multi-link option can stop a single-link connection
Multi-link PPP is intended for negotiating more than one physical link as part of a single logical connection. A conventional dial-up session has one link. When Windows proposes multi-link negotiation on that session and the peer does not support or expect it, LCP can be terminated before authentication and IP configuration begin. Clearing the option removes that proposal; it does not disable the modem or prevent an ordinary single-link call.
Rank #2
- 𝐋𝐨𝐧𝐠 𝐑𝐚𝐧𝐠𝐞 𝐀𝐝𝐚𝐩𝐭𝐞𝐫 – This compact USB Wi-Fi adapter provides long-range and lag-free connections wherever you are. Upgrade your PCs or laptops to 802.11ac standards which are three times faster than wireless N speeds.
- 𝐒𝐦𝐨𝐨𝐭𝐡 𝐋𝐚𝐠 𝐅𝐫𝐞𝐞 𝐂𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐨𝐧𝐬 – Get Wi-Fi speeds up to 200 Mbps on the 2.4 GHz band and up to 433 Mbps on the 5 GHz band for upgraded web surfing, gaming, and streaming. Performance varies by conditions, distance to devices, and obstacles such as walls.
- 𝐃𝐮𝐚𝐥-𝐛𝐚𝐧𝐝 𝟐.𝟒 𝐆𝐇𝐳 𝐚𝐧𝐝 𝟓 𝐆𝐇𝐳 𝐁𝐚𝐧𝐝𝐬 – Dual-bands provide flexible connectivity, giving your devices access to the latest routers for faster speeds and extended range. Wireless Security - WEP, WPA/WPA2, WPA-PSK/WPA2-PSK
- 𝟓𝐝𝐁𝐢 𝐇𝐢𝐠𝐡 𝐆𝐚𝐢𝐧 𝐀𝐧𝐭𝐞𝐧𝐧𝐚 – The high gain antenna of the Archer T2U Plus greatly enhances the reception and transmission of WiFi signal strengths.
- 𝐀𝐝𝐣𝐮𝐬𝐭𝐚𝐛𝐥𝐞, 𝐌𝐮𝐥𝐭𝐢-𝐃𝐢𝐫𝐞𝐜𝐭𝐢𝐨𝐧𝐚𝐥 𝐀𝐧𝐭𝐞𝐧𝐧𝐚: Rotate the multi-directional antenna to face your router to improve your experience and performance
Why the secured-password setting matters
The Security tab controls what authentication methods Windows will accept or require from the peer. If the profile insists on a secured password while the remote system supports only an unsecured password method, the peers cannot complete authentication and the PPP session ends. “Allow an unsecured password” is therefore a compatibility setting, not a general performance fix.
Use it only when the service owner, dial-up host, or VPN administrator confirms that this is the required method. An unsecured password can expose credentials more readily than a secured method, so it is not an appropriate downgrade when a stronger method is available. For a business or managed connection, obtain the approved authentication policy before changing it.
When Error 734 appears on an L2TP VPN
The same exact message is documented for the Windows native L2TP VPN client. In this situation, the PPP peer is normally the VPN gateway, and changing a dial-up-only option may not solve the problem. Treat the error as a negotiation failure that can involve the Windows profile, the gateway’s tunnel policy, or the path between them.
Check the Windows VPN profile
- Open the profile that fails, then inspect its connection and security properties rather than the settings for another VPN.
- Compare the authentication requirement with the VPN gateway’s policy. A client that requires a secured password while the gateway offers a different method can terminate PPP during negotiation.
- Review whether a multi-link option is present and enabled. If the profile exposes the single-link multi-link setting, clear it for a normal one-link VPN connection and retry.
- Make one clean attempt after saving changes. Record whether the failure occurs immediately or only after the VPN appears to contact the gateway; that timing helps separate profile negotiation from path problems.
Check the gateway and tunnel state
Fortinet documents this message in a Windows native L2TP scenario and directs administrators to inspect the VPN gateway’s L2TP status and tunnel diagnostics. A gateway administrator should verify whether an L2TP tunnel is created, whether the user session reaches the gateway, and where the session is released. If the gateway never sees the attempt, investigate the path or firewall before changing Windows authentication settings. If it sees the tunnel but rejects the session, compare the client’s PPP and authentication choices with the gateway policy.
Do not assume that a successful username and password prompt proves the tunnel is healthy. L2TP can reach the gateway while PPP negotiation still fails, which is why the Windows error can appear after an apparently valid VPN connection attempt.
Rank #3
- Performance: Support automatic dialing, tone and pulse dialing, automatic answering, automatic fax sending and receiving. Support caller ID, automatic format/speed sensing, data/fax/voice call, single profile stored on the host, call forward/backward.
- Plug and Play: The USB 2.0 fax modem dial-up adapter is suitable for WIN 98 / 2000 / ME / XP / Vista / CE5.0 / 10 / 8.1 / 8 / 7. No need for any external driver.
- Data/Fax Mode: Comply with V.92, V.90 and V.42, V.42bis / MNP5 protocol. Meets V.17, V.29, and V.27ter Group 3 fax protocols. For GRIS fax cats can dial the Internet, send and receive faxes, but do not support voice calls.
- Tech Specs: Up to 56k data download, 48k data upload, and 14.4k fax communication. The 56k data/fax modem uses USB 2.0 Type A with a full speed of 56kb/s.
- Compatibility: Standard and expanded AT command set compatibility. Provides fast connection and maintenance function on the modem.
Check the network path and firewall policy
Microsoft’s remote-access error reference notes that, for related PPP and VPN failures, an intervening firewall or router may need to allow GRE packets. This is a path and policy check, not a universal statement that every Error 734 is caused by GRE. If the Windows PPP settings match the service requirements but an L2TP VPN still fails, have the network administrator review the firewall and router rules for the VPN traffic used by the deployment, including the GRE consideration documented by Microsoft.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Testing from another network can help isolate the path: if the same VPN profile works elsewhere, the original router, firewall, or upstream network policy becomes more likely than a Windows profile error. If it fails identically on multiple networks, focus on the profile, gateway policy, or the account’s permitted authentication method.
Use the symptom to choose the next check
| Observed behavior | Most useful interpretation | Next action |
|---|---|---|
| Single-link dial-up fails immediately with Error 734 | The peer may be rejecting the proposed multi-link option or password requirement | Clear the multi-link option, retry, then review Security and the secured-password requirement |
| The error appears only after moving to a secured-password requirement | The peer may not support that authentication method | Confirm the peer’s policy; allow an unsecured password only when explicitly required |
| Windows native L2TP VPN fails, and the gateway records no attempt | The network path or an intervening firewall/router may be blocking required traffic | Have the network administrator inspect path rules and VPN traffic handling |
| The L2TP gateway records a tunnel or session, then releases it | The client and gateway may disagree about PPP or authentication parameters | Compare the Windows profile with gateway policy and review gateway tunnel diagnostics |
| Changing the two documented dial-up settings has no effect | The cause may be outside those settings | Identify whether the connection is WWAN or VPN, then inspect the peer, gateway, and network path |
A disciplined troubleshooting workflow
1. Capture the exact context
Write down whether the failing connection is dial-up, cellular/WWAN, or L2TP VPN; the Windows edition and current interface; and whether the failure occurs on every network or only one. Keep the exact wording and number: “The PPP link control protocol was terminated” and Error 734. This prevents a generic VPN failure from being treated as a modem problem.
2. Change one setting at a time
For a dial-up connection, clear the multi-link option, save, and test. Only after that test should you review the password requirement. Changing several authentication choices at once removes the evidence needed to tell which incompatibility was present and can leave the profile weaker than necessary.
3. Confirm the peer’s requirements
PPP negotiation succeeds only when both sides accept the proposed parameters. Ask the dial-up provider, cellular service administrator, or VPN administrator which authentication method and link arrangement are supported. A setting that is valid for one service can be rejected by another, even when both use PPP.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Rank #4
- AC1300 Dual Band Wi-Fi Adapter for PC, Desktop and Laptop. Archer T3U provides 2.4G/5G strong high speed connection throughout your house.
- Archer T3U also provides MU-MIMO, which delivers Beamforming connection for lag-free Wi-Fi experience.
- Usb 3.0 provides 10x faster speed than USB 2.0, along with mini and portable size that allows the user to carry the device everywhere.
- World's 1 provider of consumer Wi-Fi for 7 consecutive years - according to IDC Q2 2018 report
- Supports Windows 11, 10, 8.1, 8, 7, XP/ Mac OS X 10.9-10.14
4. Separate client failures from path failures
For VPNs, compare a gateway-side record with the Windows result. No gateway record points toward the path; a recorded tunnel that is released during PPP points toward a policy or authentication mismatch. Testing from a different network is another practical way to distinguish a local firewall or router problem from a profile or gateway problem.
5. Restore unnecessary changes
Once testing is complete, leave only the settings required by the peer. In particular, do not leave an unsecured-password allowance enabled when the service supports and requires a secured method. The goal is compatibility with the documented peer policy, not the loosest possible setting.
Common mistakes that waste time
- Replacing the modem first: Error 734 identifies a terminated PPP negotiation and does not by itself establish a hardware failure.
- Changing every VPN option at once: This makes it impossible to identify whether multi-link negotiation, authentication, or the path caused the failure.
- Assuming every instance is a Windows bug: An L2TP gateway or intervening firewall can produce the same wording when the client cannot complete the tunnel.
- Enabling an unsecured password permanently: This may make a particular peer compatible but can violate the service’s security policy.
- Ignoring the connection type: A dial-up Properties fix is not a substitute for gateway diagnostics when the failing profile is an L2TP VPN.
When to escalate
Escalate to the service or network administrator when the multi-link option is clear, the authentication setting matches the documented policy, and the error persists. Provide the connection type, exact Error 734 text, the settings tested, the time of the attempt, and whether the gateway recorded a tunnel or session. For an L2TP VPN, request the gateway’s tunnel and session diagnostics and a review of firewall/router handling. For a managed dial-up or WWAN service, ask the provider to confirm the supported PPP authentication method and whether the account is permitted to establish the session.
Bottom line
Error 734 means LCP negotiation was terminated; it is not a single hardware diagnosis. On a single-link dial-up connection, clear Negotiate multi-link for single link connections, retry, and then check whether the secured-password requirement matches the peer. On a Windows L2TP VPN, make the same client-side comparison but also verify gateway tunnel state and the intervening network path, including the GRE consideration in Microsoft’s related error guidance. Leave the final configuration aligned with the peer’s documented security policy.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
