NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Retired_Member
Jan 27, 2019R7000 Does not Detect Ethernet Cable from Sleeping PC
When my windows 10 PC is sleeping, the light on port #1 (where it is connected) typically is lit up an amber color. Within the last week, when the connected PC goes to sleep, port #1 will not light ...
- Jan 28, 2019
Are you sure about that one? What site is that at?
I found drivers for the at the REALTEK SITE, I'd use those.
What exactly is your network adapter and what chipset does it use? Is it the "Realtek PCIe GBE Family Controller"? If it is, check my screenshot. I'm on Win10 Home, V1809, and my NIC is actually older and works (it is NOT in use now) fine as of about 5 weeks ago, and had worked fine wih the R7000 I had connected about 10 months ago.
If you open up SYSTEM INFORMATION (can search for it by entering system on the search line for Siri) and then select NETWORK, then ADAPTER you'll see a list of them depending on how many you have. My NIC has this info:
Name [00000001] Realtek PCIe GbE Family Controller
Adapter Type Not Available
Product Type Realtek PCIe GbE Family Controller
Installed Yes
PNP Device ID PCI\VEN_10EC&DEV_8168&SUBSYS_05B71028&REV_0C\010000000000000000
Last Reset 1/27/2019 5:43 AM
Index 1
Service Name rt640x64
IP Address Not Available
IP Subnet Not Available
Default IP Gateway Not Available
DHCP Enabled Yes
DHCP Server Not Available
DHCP Lease Expires Not Available
DHCP Lease Obtained Not Available
MAC Address Not Available
Driver c:\windows\system32\drivers\rt640x64.sys (10.28.615.2018, 1.09 MB (1,139,424 bytes), 7/29/2018 10:32 AM)Suspect yours would be the same as this.
When I look at the date of the driver's timestamp on the last line, it is 7/29/2018. It could very well be the same one on the RealTek site as it would be included in that package because the RealTek site has the SAME date? Of course the real Driver is that last line. Possible MS installed it along with V1809 even? Just need the .SYS file possibly?
Check what you have before trying to update, but if you do, get it off the RealTek site, much safer. Quite possible if you do try to install it it could even tell you you are up-to-date even?
Did you check all the properties for Power Management as well as the Power Plan?
Retired_Member
Jan 28, 2019Here is the picture in my post above.
It is hard to tell what driver is needed. Maybe they are universal?? I was looking for a model number or something to match up...
It is hard to tell what driver is needed. Maybe they are universal?? I was looking for a model number or something to match up...
IrvSp
Jan 28, 2019Master
Are you sure about that one? What site is that at?
I found drivers for the at the REALTEK SITE, I'd use those.
What exactly is your network adapter and what chipset does it use? Is it the "Realtek PCIe GBE Family Controller"? If it is, check my screenshot. I'm on Win10 Home, V1809, and my NIC is actually older and works (it is NOT in use now) fine as of about 5 weeks ago, and had worked fine wih the R7000 I had connected about 10 months ago.
If you open up SYSTEM INFORMATION (can search for it by entering system on the search line for Siri) and then select NETWORK, then ADAPTER you'll see a list of them depending on how many you have. My NIC has this info:
Name [00000001] Realtek PCIe GbE Family Controller
Adapter Type Not Available
Product Type Realtek PCIe GbE Family Controller
Installed Yes
PNP Device ID PCI\VEN_10EC&DEV_8168&SUBSYS_05B71028&REV_0C\010000000000000000
Last Reset 1/27/2019 5:43 AM
Index 1
Service Name rt640x64
IP Address Not Available
IP Subnet Not Available
Default IP Gateway Not Available
DHCP Enabled Yes
DHCP Server Not Available
DHCP Lease Expires Not Available
DHCP Lease Obtained Not Available
MAC Address Not Available
Driver c:\windows\system32\drivers\rt640x64.sys (10.28.615.2018, 1.09 MB (1,139,424 bytes), 7/29/2018 10:32 AM)
Suspect yours would be the same as this.
When I look at the date of the driver's timestamp on the last line, it is 7/29/2018. It could very well be the same one on the RealTek site as it would be included in that package because the RealTek site has the SAME date? Of course the real Driver is that last line. Possible MS installed it along with V1809 even? Just need the .SYS file possibly?
Check what you have before trying to update, but if you do, get it off the RealTek site, much safer. Quite possible if you do try to install it it could even tell you you are up-to-date even?
Did you check all the properties for Power Management as well as the Power Plan?
- Retired_MemberFeb 01, 2019
My posts are not saving for some reason. I have been trying for 2 days.
- antinodeFeb 01, 2019Guru
> [...] my windows 10 PC [...]
Not a very detailed description of anything.
> [...] When the PC is sleeping, the lights on the network port on the
> back of the PC are all off. I am not sure that this was always the
> case. [...]To me, that sounds like a clue.
Typically, an Ethernet interface gets power when the system is in
standby ("power off") mode, to enable features like wake-on-LAN:
https://en.wikipedia.org/wiki/Wake-on-LAN On a system which provides
standby power (almost all, these days), you can usually find a few LEDs
(on the main board and/or the Ethernet card/port) glowing whenever the
power cord is connected. The (so-called) power switch controls only the
primary part of the power supply; the (small) standby part is(typically) always on.
If the standby output of the power supply fails, then the system
(including its Ethernet interface) would be dead unless the power supply
is in its full-on state. I'd expect that even "power off", which should
be more dead than "asleep", would leave standby power on, unless there's
some contrary BIOS option.> Windows: Version 10.0.17763 Build 17763
Source? WINVER output: "Version 1809 (OS Build 17763.292)"?
> Like many of you, I had a windows 10 update installed recently,
> could that have caused the issue? [...]I'd expect not. I don't use such features, so I know nothing, but I
can imagine a BIOS option which might disable WakeOnLAN and/or the
standby output of the power supply. But I wouldn't expect any such
setting to change spontaneously. Even considering Netgear's typical
firmware quality, basic failure to detect an active Ethernet interface
seems pretty unlikely, too.
If no one has fiddled with the BIOS settings or the Windows settings,
then I'd suspect the power supply hardware. Especially if you formerly
saw LED indicators when the system was asleep or "powered off", and now
don't. I'd expect such a power supply failure to be pretty rare, but
not impossible, and it would seem to be consistent with your symptoms.Everything recovers nicely when the system is powered up?
If another computer connected to that router port works as expected,
then that should rule out the router as the cause, no?- Retired_MemberFeb 03, 2019
WINVER output: "Version 1809 (OS Build 17763.253)"
Everything recovers fine when the PC is powered up.
I connected a laptop to the router in the same port. When the laptop was put ot sleep mode the LED turned off, as it now has been doing on the PC.
I read the manual for the router and LED colors are: "The LED color indicates the speed: white for Gigabit Ethernet connections and amber for 100 Mbps or 10 Mbps Ethernet connections." So before it was indicating a 100 Mbps connection when my PC was sleeping. Not it is off indicating according to the manual that no device is connected to the port.
- Retired_MemberFeb 03, 2019
It turned out to be an outdated driver on my NIC. I installed the one from the website you recommended and it worked! Previous driver was from 2011. New one is from 2018. Thanks!