If Ethernet has no internet until restart, the likely causes are stale DHCP lease, driver state, DNS cache, VPN route, power saving, router DHCP issue or a network service that only refreshes on reboot.
Start by comparing what still works: browser versus app, Wi-Fi versus mobile data, Ethernet link versus DNS, or restart versus smaller network refresh. That comparison tells you where the fix belongs.
Start with the exact layer that still works
Ethernet that only works again after a restart is a pattern worth taking seriously. The cable may stay connected, the LAN light may blink and Windows may show a network, but nothing loads until the computer restarts. That usually means rebooting is refreshing something stuck: the adapter driver, DHCP lease, DNS cache, routing table, VPN route or network service. Restarting feels like a fix because it works, but it is really a clue. The goal is to find what the restart is clearing.
The best approach is to reproduce the failure, then try smaller refreshes before rebooting. Renew the IP lease, flush DNS, disable and re-enable the adapter, disconnect VPN and restart router services only when the evidence points there. If one smaller action fixes it, you know the layer that failed and can make a more permanent change.
Quick diagnosis table
Try these fixes in order
Use this order so you prove the failure point before changing broad settings.
- 01
Renew IP before restarting
When the problem appears, release and renew the IP address. If that fixes it, the restart was clearing a DHCP lease problem.
- 02
Flush DNS
Clear DNS cache and test the same website. If it works, DNS cache or resolver state was the likely issue.
- 03
Disable and re-enable Ethernet adapter
This restarts the adapter without rebooting the whole computer. If it works, driver state is the suspect.
- 04
Check VPN routes
Disconnect VPN fully and disable kill switch for a test. VPN routes can survive in a broken state until reboot.
- 05
Turn off adapter power saving
If the issue appears after sleep or idle time, stop the computer from powering down the Ethernet adapter.
- 06
Update Ethernet and chipset drivers
A repeat restart-only fix often points to driver state. Use the computer or motherboard maker's driver.
- 07
Check router DHCP if several devices need restart
If multiple devices have the same problem, the router may be handing out bad leases or DNS. Restart and update router firmware.
- 08
Use network reset only after targeted tests
Network reset can clear damaged configuration, but it is broad. Use it after you learn whether DHCP, DNS, VPN or driver state is the cause.
- 09
Retest after a restart or reconnect
After the fix appears to work, restart the app, reconnect the adapter or reboot the device once. A fix that survives the next restart is much more reliable than one lucky successful load.
Detailed checks
Restart is evidence, not the final fix
A restart clears many layers at once. That is useful but vague. Smaller refreshes reveal which layer actually needed clearing.
- Try lease renew, DNS flush or adapter disable before rebooting.
DHCP lease problems are common
The computer may keep an address that no longer routes correctly. Renewing the lease can fix it without touching cables.
- If this happens often, check router DHCP and consider a firmware update.
Driver state can get stuck
Ethernet drivers can hold a bad state after sleep, VPN changes or network switches.
- Updating the driver and chipset is the long-term fix when adapter disable/enable works.
The repeat pattern matters
If the failure happens after sleep, after VPN, after moving rooms or after long idle time, that trigger matters.
- The trigger tells you whether the fix belongs in power settings, VPN or router DHCP.
Why repeat testing matters
A single successful load can be a cached page, a lucky route or a temporary service recovery. Repeat testing shows whether the fix changed the actual broken layer.
- Use the exact same app, website or connection state that failed before. That keeps the confirmation honest.
Mistakes to avoid
Do not assume one working browser proves every app has clean internet.
Do not blame the router when the pattern follows one device, app, VPN or adapter.
Do not change DNS, VPN, firewall and drivers all at once. Test one layer at a time.
FAQ
Why does Ethernet only work after restart?
Because restart clears the stuck network layer, such as DHCP lease, DNS cache, adapter driver or VPN route.
The goal is to find which smaller refresh does the same thing.
Is restarting bad?
No, but it is not a diagnosis. It hides the specific cause.
Use it when needed, then test smaller fixes next time.
Can renewing IP fix it?
Yes. If DHCP lease state is stale, renew can restore internet without rebooting.
If renew works repeatedly, check router DHCP settings.
Can DNS cache cause restart-only internet?
Yes. Bad cached DNS can make websites fail until restart clears it.
Flushing DNS is faster than rebooting.
Can VPN cause this?
Yes. VPN routes and kill switches can block traffic until reboot.
Disconnect VPN and clear routes before restarting.
Does sleep mode cause it?
Often. Sleep can leave the adapter in a bad power state.
Disable Ethernet power saving and update drivers.
Should I replace the Ethernet cable?
Try it if the link drops, but restart-only fixes usually point to software state.
Cable problems usually do not wait for reboot to improve.
Can the router cause restart-only fixes?
Yes, if several devices get bad DHCP or DNS from the router.
If only one PC needs restart, the PC is more likely.
When should I use network reset?
Use it after targeted IP, DNS, VPN, power and driver tests fail.
It can help, but it removes saved network configuration.
Outside references
- Microsoft Windows Support
Official Windows networking support reference.
- Intel Ethernet Support
Official Ethernet driver support reference.