unable to connect to internet after PC wakes from sleep.

Hi folks,

I have an older desktop computer, connected by Ethernet from EEro router. going ok, had a few upgrades such as SSD done.
I am running Windows 10 latest build and have changed ISP from EE to Youfibre.

Occasionally in the past before going From EE to Youfibre, PC would be disconnected from the internet when awoke from sleep mode or an odd time when just doing a restart, I get that little round world icon on bottom taskbar, rather than the connected monitor icon.

It does seem to have got worse since changing to Youfibre, using the EEro router, all other devices are ok.

Its a Realtek network adapter, have done the usual troubleshooting,

1 rebooting router,
2 changing the Ethernet cable.
3 Disabling the Realtek from going to sleep in Device manager.
4 Updated the Realtek driver and uninstalled it, letting Windows discover it again after PC startup.

When I right click on the disconnected icon on the desktop and run the troubleshooter, it connects me again.

When I run the troubleshooter on the Network adapter even when connected to the net and working ok I I get the following,
"Your computer appears to be correctly configured, but the device or resource (DNS server) is not responing


Here is a log, any further ideas appreciated,


Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : E0-CB-4E-C1-41-57
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a0e:1d47:da89:4000:2528:120d:ce26:6ce1(Preferred)
IPv6 Address. . . . . . . . . . . : fdd7:64e0:e2b5:1:21b7:e48d:4c22:d5ef(Preferred)
Temporary IPv6 Address. . . . . . : 2a0e:1d47:da89:4000:38bd:60ec:d065:d97d(Preferred)
Temporary IPv6 Address. . . . . . : fdd7:64e0:e2b5:1:38bd:60ec:d065:d97d(Preferred)
Link-local IPv6 Address . . . . . : fe80::571a:56e3:6d31:af2c%26(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.4.21(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Lease Obtained. . . . . . . . . . : 11 December 2024 13:23:29
Lease Expires . . . . . . . . . . : 11 December 2024 17:16:13
Default Gateway . . . . . . . . . : fe80::ead3:ebff:fe4a:c4b2%26
192.168.4.1
DHCP Server . . . . . . . . . . . : 192.168.4.1
DHCPv6 IAID . . . . . . . . . . . : 450939726
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-AD-C9-7F-E0-CB-4E-C1-41-57
DNS Servers . . . . . . . . . . . : 185.154.147.1
185.154.147.2
2a0e:1d40::185:154:147:1
2a0e:1d40::185:154:147:2
NetBIOS over Tcpip. . . . . . . . : Enabled

Edited by joemardo1 (Wed 11-Dec-24 15:35:24)

Newer network switches generally have an eco mode that will power down unused ports. Assuming your ISP change meant a new router, I'd be checking the router config for any kind of power saving options.

Edit: Also that's an incredibly short DHCP lease time for a home LAN. Maybe look at upping it to a day or more.

Edited by Noiz (Wed 11-Dec-24 15:29:45)

Thanks, I take it DHCP lease time refers to having an IP address, which is correct as I don't have a static IP with Youfibre,

Sorry if I have misunderstood this.

I have added a litter further info to the previous post such as the message I get when I run the troubleshooter.

Edited by joemardo1 (Wed 11-Dec-24 15:41:08)

Your ISP will be assigning a public IP to your router via DHCP, yes, but that doesn't relate to this.

Your router will have a built-in DHCP server that provides LAN IPs to your local devices. Large corporate networks might opt to have a short lease time for security reasons, but home routers usually default to at least a day (86400 seconds). If your laptop is waking from sleep and its lease has expired then it might struggle to renew it if the driver or hardware is being weird. Setting a longer lease time might help.

In reply to a post by joemardo1:

Thanks, I take it DHCP lease time refers to having an IP address, which is correct as I don't have a static IP with Youfibre,

Sorry if I have misunderstood this.

I have added a litter further info to the previous post such as the message I get when I run the troubleshooter.

Check the time this delay (on wakening the PC) happens against your Win 10 logs (as above) to see:
(1) if it also coincides with a new DHCP lease being granted to your PC by your router, this is the local network IP address dished out by your router to your PC.
(2) cross check against the DHCP server logs in the router - the granting / expiry times for the DHCP lease should precisely match on router and PC. If they don't then you could have a conflict going on, which could exacerbate the delay.

What router do you have?

On the Eeros it seems you can't change the dhcp lease time. So a Static(ip v4 at least) ip may be the way to go

Must remember to read the OP (properly 🙈). Missed that!!

In reply to a post by Pheasant:

Must remember to read the OP (properly 🙈). Missed that!!

*me pointing at my giant forum tshirt pile of "i didn't read the post properly"* 😂🤭🙈. A static lan ip would work best for him given the router limitations

Hopefully, though not a huge fan of statically assigned IPs (on the device), just more admin to keep a note of what's got what. Ideally the router should be doing it all, including static assignments, but I digress. Any port in a storm as they say.

In reply to a post by Pheasant:

Hopefully, though not a huge fan of statically assigned IPs (on the device), just more admin to keep a note of what's got what. Ideally the router should be doing it all, including static assignments, but I digress. Any port in a storm as they say.

yeah I mac/ip bind at the router end, easier to maintain what the fuzz is going on. Except if you swap nics around 👀😩