How to fix Windows error 651 on a PPPoE connection

Windows Error 651 shows up as The modem (or other connecting device) has reported an error the moment you try to bring up a broadband (PPPoE) connection. On Windows 11 it almost always traces back to one of three things: a modem or router that has stalled, a corrupt PPPoE profile, or a network stack that needs a reset. Work through the steps below in order, from the fastest to the most involved, and stop as soon as the connection comes up.

What Error 651 actually means#

Error 651 is a PPPoE session failure, not usually a sign that hardware has died. Windows uses a Remote Access PPPoE driver (raspppoe.sys) to negotiate the broadband session with your provider, and 651 is the generic “the session could not be established” result. Because the code is generic, there is no single cure. You rule out causes from the outside in: the physical link first, then the saved connection, then the software stack underneath it.

Symptom	Likely cause	First fix
651 the instant you click Connect	Stalled modem/router or a loose cable	Power-cycle both, reseat the Ethernet cable
651 that started after a Windows update	Network driver mismatch	Update or roll back the adapter driver
651 that returns after every reboot	Corrupt PPPoE profile or TCP/IP stack	Rebuild the connection, reset TCP/IP and Winsock

Restart the modem, then check every cable#

Start with the cheapest fix, because a stalled modem causes a large share of 651 errors. Microsoft’s guidance is to power-cycle the whole link: unplug the power cable from the router, unplug the power cable from the modem, wait at least 30 seconds, plug the modem back in and let its lights settle, then plug the router back in (Microsoft Support: fix Ethernet connection problems in Windows). Restart the PC while you wait.

Then look at the cable itself. Make sure the Ethernet cable is seated firmly in the port on both the modem and the PC, try a different cable if you have one, and move it to another port on the modem. If the connection you are fixing is wireless rather than wired, the drop is a different problem — see how to fix Wi-Fi that keeps disconnecting on Windows 11.

Rebuild the broadband (PPPoE) connection#

A saved PPPoE profile can go stale or store the wrong credentials, and that produces a clean 651 every time. The reliable fix is to delete the old connection and create a fresh one. Open Control Panel > Network and Sharing Center > Set up a new connection or network, choose Connect to the Internet, then pick Broadband (PPPoE). Enter the exact username and password your internet provider gave you — many providers include a realm on the username, so type it exactly as issued.

If the new connection still returns 651, confirm the credentials with your provider before going further. A password that changed or an account that is suspended looks identical to a software fault from the PC’s side.

Reset the network stack and fix the driver#

If the link and the profile are both good, reset the software underneath. Open Command Prompt or Windows Terminal as an administrator and run the commands below, then restart the PC. These reset the Winsock catalog and rebuild the TCP/IP stack, which clears the corruption behind a stubborn 651 (Microsoft Support: fix Ethernet connection problems in Windows).

Command	What it does
netsh winsock reset	Resets the Winsock catalog to its defaults
netsh int ip reset	Rebuilds the TCP/IP stack
ipconfig /release	Drops the current IP lease
ipconfig /renew	Requests a fresh IP lease
ipconfig /flushdns	Clears the DNS resolver cache

Next, look at the network adapter driver. If 651 appeared right after a Windows or driver update, open Device Manager > Network adapters, right-click your Ethernet adapter, and either update the driver or roll it back to the previous version. You can also uninstall the adapter and restart — Windows reinstalls the driver automatically, which is often enough to clear a mismatch. When nothing else works, run a full Network reset from Settings > Network & internet > Advanced network settings > Network reset, which removes and reinstalls every adapter with default settings (Microsoft Support: fix Wi-Fi connection issues in Windows). Expect to sign back into a VPN afterward.

Rule out IPv6, the firewall, and a corrupt driver file#

If the connection still fails, isolate the cause with two reversible tests. Open the adapter’s Properties and uncheck Internet Protocol Version 6 (TCP/IPv6), then try to connect. Separately, temporarily turn off any third-party firewall or security suite and test again. Neither is a permanent fix — turn IPv6 and the firewall back on once you know which one changes the result, and treat the answer as a pointer to the real setting to adjust.

The old advice to download a replacement raspppoe.sys from a random site is a bad idea and a security risk. If you suspect the PPPoE driver file itself is damaged, repair Windows system files the safe way instead: run sfc /scannow, and if that cannot fix everything, follow it with DISM /Online /Cleanup-Image /RestoreHealth. Both pull clean copies from Windows rather than the open internet.

Most 651 cases clear at the power-cycle or the PPPoE rebuild, and the network reset is the dependable fallback when they do not. If the error only appears at certain times of day, or on one device out of several, the trouble is likely upstream at your provider — call them with the exact times it failed. None of this replaces basic upkeep: a machine that is also cramped or sluggish is worth tuning with the fixes for a slow Windows PC and a round of freeing up space on Windows 11.