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 👀😩

Thanks Everybody.

I have an EEro pro from Youfibre, I usually don't understand all the Tech jargon but this router does seem to have a limited amount of settings.

In Network settings for DHCP and Nat there are only three settings Automatic, Manual IP and Bridge.

So far I can't see a setting as regards lease time.

I did switch DNS local caching on though.

What is going on if i'm correct is; your pc on boot gets an ip, which your router issues for a certain amount of time - most routers give a day. Now your router is far shorter, and you can't change. That said, so your pc has an ip and your router says ok you can have it for x minutes, you then put your pc to sleep, and when you wake the pc up its outside that lease time and that leaves you with no internet.

Theres is mulitple work arounds. One is to have a script that runs on startup to release and renew the ip or you change the Ethernet port to have a static lan ip (idealy outside of the dhcp range).

Thanks,

Just had a check of my IP from last year compared to this morning, while my IPv4 has not changed, the IPv6 is different, does that make sense?

As I do have an EEro router with only one Ethernet port I can't really do anything about that, though I do have a few old Talktalk routers lying about.

Seems it maybe is something that I can't do much about, other than not putting the PC to sleep.

We can resolve this... (it may take a day or so)

firstly what is your lan ip atm ?

Edited by Taras (Thu 12-Dec-24 09:26:52)

Thanks a lot Taras,

I take it you don't mean my main IP address, rather the local one that is assigned to my desktop by the EEro router,

A command prompt ipconfig gave this,

IPv4 Address. . . . . . . . . . . : 192.168.4.21
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 192.168.4.1

I have contacted Youfibre support and they have disabled the IPv 6 to see if that might help, and also have said that since my desktop computer is going on for fifteen years old to consider looking for a new one.

I will next year but at the moment this computer with a quad core Athlon 945 an SSD and 12 Gb of Ram does everything I ask of it.

In reply to a post by joemardo1:

Thanks a lot Taras,

I take it you don't mean my main IP address, rather the local one that is assigned to my desktop by the EEro router,

A command prompt ipconfig gave this,

IPv4 Address. . . . . . . . . . . : 192.168.4.21
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 192.168.4.1

I have contacted Youfibre support and they have disabled the IPv 6 to see if that might help, and also have said that since my desktop computer is going on for fifteen years old to consider looking for a new one.

I will next year but at the moment this computer with a quad core Athlon 945 an SSD and 12 Gb of Ram does everything I ask of it.

well YF support were not helpful with that.

I found a video guide (recent) to help set up a static lan ip address on the eero.


https://www.youtube.com/watch?v=FRNf0VzKaDI

you will need your mac address - double check in the same way as in the video shows

E0:CB:4E:C1:41:57

and your ip address for the affected pc.

192.168.4.21

give it a name JoePC1 for instance and click add ip reservation.

What this does is always gives your pc the same ip address and it should ignore the dhcp lease time..

If you find that its still doing the same thing - theres a second route of creating a static lan ip address. So do come back to say if this first attempt works or doesn't

Thanks Taras will try this.

Many thanks.

I’m not convinced that it’s a DHCP problem (renewal will usually give you the same address).

Have you tried the steps outlined in this thread https://www.reddit.com/r/Realtek/comments/wgp84u/sol... ?

Not totally convinced tis DCHP either. However statically assigning an IPv4 address (ought to be) a very quick fix/check and I think is a reasonable place to start, before moving on.

That’s true. I assign all the permanent devices in my home to pre-allocated addresses (which obviously depends upon how much control you have over the dhcp server - I use the Synology one on my NAS). DHCP addresses should renew themselves when there is half of their lifetime left, so the IP address isn’t likely to change unless they are offline for a long time. And even if it did change, I can’t see why it would cause problem.

On the other hand, components not waking properly from sleep is not uncommon.

I have had DHCP "weirdness" in the past. For example Cisco IP phones of a certain generation/build could be a real nightmare with certain DHCP servers. But these days DHCP compatibility is very much a non-event in general.

Saying that, things going too sleep (especially much older hardware like the OP has) and not waking properly / driver issues can compound a DHCP renewal situation in some cases.

In reply to a post by Pheasant:

I have had DHCP "weirdness" in the past. For example Cisco IP phones of a certain generation/build could be a real nightmare with certain DHCP servers. But these days DHCP compatibility is very much a non-event in general.

Saying that, things going too sleep (especially much older hardware like the OP has) and not waking properly / driver issues can compound a DHCP renewal situation in some cases.

its either driver, router firmware (effectively driver) or hardware. If the static ip address works then i think for the OP thats fine - for now its solved but yes wake up from sleep screams drivers - and its something i missed - so i do agree with you and TM

Agreed. It’s the most sensible first step. 👍

just re-read the OP's first post

4 Updated the Realtek driver and uninstalled it, letting Windows discover it again after PC startup.

Even though he updated the drivers they still could be out of date. Gigabyte's website is one example of "out of date drivers" for instance.

In reply to a post by Taras:

just re-read the OP's first post

4 Updated the Realtek driver and uninstalled it, letting Windows discover it again after PC startup.

Even though he updated the drivers they still could be out of date. Gigabyte's website is one example of "out of date drivers" for instance.

In reply to a post by joemardo1:

I have contacted Youfibre support and they have disabled the IPv 6 to see if that might help, and also have said that since my desktop computer is going on for fifteen years old to consider looking for a new one.

I will next year but at the moment this computer with a quad core Athlon 945 an SSD and 12 Gb of Ram does everything I ask of it.

The machine is getting on, to be fair...probably struggle to get up to date drivers for the NIC.

Edited by Pheasant (Fri 13-Dec-24 00:38:23)

Waking up from sleep, if you have STP on your network, it has to go through STP negotiation, also Windows firewall will temporarily block traffic when you are connected to a unidentified network.

However these things shouldnt prevent recovery at all, just delay it.

The recommendation is to get the drivers from Realtek.

Then make the appropriate changes to the power-saving settings for the device.

Edited by TinyMongomery (Fri 13-Dec-24 06:39:16)

The latest drivers from Realtek for their Gbe devices are dated 6/12/2024.

Sounds good 👍. Hopefully the OP can load them and set the powersave options see if it resolves their issue.

In reply to a post by TinyMongomery:

The recommendation is to get the drivers from Realtek.

Then make the appropriate changes to the power-saving settings for the device.

You do sometimes have to search for latest realtek drivers, if he had got the drivers from his mobo's or manufacture's website they may not be latest. For my 2.5gb realtek nic, gigabyte has last year's version as the latest.


anyways the link is https://www.realtek.com/Download/List?cate_id=584 from realtek.

In reply to a post by Pheasant:

In reply to a post by joemardo1:

I have contacted Youfibre support and they have disabled the IPv 6 to see if that might help, and also have said that since my desktop computer is going on for fifteen years old to consider looking for a new one.

I will next year but at the moment this computer with a quad core Athlon 945 an SSD and 12 Gb of Ram does everything I ask of it.

The machine is getting on, to be fair...probably struggle to get up to date drivers for the NIC.

I somehow missed the 15 year old bit 🙈 .Realtek is very good with updates which is good in this case. The realtek link is now in this thread and so is very usable for somebody else. Plus theres multiple solutions for people. Even though update driver is normally the cure all for issues (normally mind).

There's no such thing as "normally" when computers are involved.

In reply to a post by TinyMongomery:

There's no such thing as "normally" when computers are involved.

shuuuuuuuuuuuushhhhhhhhhh 🤭🤭🤭😂. We know this, the world doesn't ok ........

ie. order 100 computers at the same spec, at least one will behave in ways you never expected or can resolve...............🙈😩👀

American or UK date format?

Does it matter? If it’s June or December this year that’s recent enough 😄

December would be more recent than June.

Being British you can assume that I always use British format (and make any necessary conversion). But for 15-year old hardware it really is irrelevant.

You're 4 minutes late with your reply as Pheasant has already replied.

I'm so sorry. I didn't realise that only one person was allowed to reply to a post. Still, at least it was 4 minutes rather than 5 months.

In reply to a post by TinyMongomery:

I'm so sorry. I didn't realise that only one person was allowed to reply to a post. Still, at least it was 4 minutes rather than 5 months.

WOW https://i.pinimg.com/originals/3a/b1/b9/3ab1b96242f0...

Alternatively you can disable sleep hibernation and only make your computer go to standby monitor, which is what I do.
That way your computer will be running but only your monitor will go to sleep.
In truth, you're not going to be saving much energy bills having your PC go to sleep unless you are leaving your PC on the whole night.

There's also another setting, I know you mentioned in your topic that you've already tried this.

But in Control Panel--->Device Manager--->Network adapters--->Right click and go to Properties---> Power Management Tab. Uncheck the tick box "Allow the computer to turn off this device to save power"
Second option "Allow this device to wake up the computer"

Find other devices and do the same.

What this will mean is that the computer will go to sleep but will simply not be putting your network adapter to sleep.
This suggestion has often helped solve problems with keyboard and mice issues where the mouse or keyboard wasn't performing well or was causing it to be unresponsive for milliseconds.

Otherwise, the best solution is to disable the computer from going to sleep and only allow the monitor to go to standby then you won't have this problem.

Second suggestion is to buy a new NIC network adapter from Amazon and if you have an additional PCIe slot available in your motherboard then you can plug the new adapter there and see if the problem is resolved. If you don't have the slot available then really your best bet is to buy a new PC.

A new PC is also likely to give you better speeds as your old processor can be a bottleneck.

In reply to a post by Pheasant:

Does it matter? If it’s June or December this year that’s recent enough 😄

Unless the December one fixed a bug in the June one .

😂 You’d hope and pray, that the drivers would be relatively stable by now, given the original device is nigh on 15 years old and is running on an OS that will be unsupported in a few months….😉

Not to mention the fact that we are only talking about one update.

Which may or may not fix the issue.

Also it may be bios related .......

Of course.

Thanks for your useful suggestions as to how the OP might solve their problem.

You are more than welcome. Don't forget, some of the posts that you provide do not help anyone to do anything.