Ethernet dropping pings and reconnecting on headless PC

[Chaarliie]

Hello,

I have started having an issue with a headless PC that I use for a windows server and remote desktop in about a week ago the ethernet kept dropping for a couple of seconds then coming back and repeating every 30 seconds to a couple of minutes and it is only happening on that PC constantly and I am losing my mind trying to troubleshoot and if anyone would know of any that I can try.

Pinging PC from my main pc I am getting
Reply from 192.168.0.113: bytes=32 time<1ms TTL=128
Reply from 192.168.0.113: bytes=32 time<1ms TTL=128
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.113: bytes=32 time<1ms TTL=128
Reply from 192.168.0.113: bytes=32 time<1ms TTL=128

Pinging googles 8.8.8.8 adress:
Reply from 8.8.8.8: bytes=32 time=18ms TTL=116
Reply from 8.8.8.8: bytes=32 time=18ms TTL=116
Reply from 8.8.8.8: bytes=32 time=18ms TTL=116
Reply from 8.8.8.8: bytes=32 time=16ms TTL=116
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Reply from 8.8.8.8: bytes=32 time=19ms TTL=116

Router logs:
Jan 17 11:14:10 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 8) Link Up at 1000 mbps full duplex
Jan 17 11:14:57 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 8) Link DOWN.
Jan 17 11:15:00 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 8) Link Up at 1000 mbps full duplex
Jan 17 11:17:49 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 8) Link DOWN.
Jan 17 11:17:52 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 8) Link Up at 1000 mbps full duplex

Specs:
CPU: Ryzen 3 1300
Motherboard: gigabyte x370 gaming k5
16GB ram
32TB of storage
700w Corsair RM PSU

What I have done so far:

1. Swapped over to a brand new cat 5e ethernet cable
2. cleaned the ports on the integrated motherboard nic
3. updated my motherboard drivers chipset, lan, etc (uses Intel i211) 23.5.2
4. Disabled ethernet power-saving mods in device manager
5. flushed DNS cache, done an ip renewal, Winsock stack, set a static IP and DNS servers to Cloudflare
6. went out a bought a separate NIC that has a Realtek chip
7. set my virgin router into modem mode and now got an asus AX 82U (it is happening either when the virgin router was in regular router/modem mode)
8. set a static IP on the router for the headless server to use
9. in the event viewer I am seeing these errors "warning Intel I211 gigabit network connection link disconnected" and error " DNS Client service failed to start due to the following error: The system cannot find the file specified. "

Is there anything else I can try cause I am losing my mind?

Thanks.

 

[ColinTaylor]

Log into your VM hub and check it's network log for "partial service" messages.

 

[Chaarliie]

Log into your VM hub and check it's network log for "partial service" messages.

Hello I checked through my network log and see this

Time	Priority	Description
19/01/2022 14:12:4​	notice​	LAN login Success;CM-MAC=40:0d:10:5a:f7:c3;CMTS-MAC=28:52:61:fa:05:d0;CM-QOS=1.1;CM-VER=3.0;​
19/01/2022 14:11:56​	Warning!​	LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=40:0d:10:5a:f7:c3;CMTS-MAC=28:52:61:fa:05:d0;CM-QOS=1.1;CM-VER=3.0;​
17/01/2022 23:59:46​	notice​	LAN login Success;CM-MAC=40:0d:10:5a:f7:c3;CMTS-MAC=28:52:61:fa:05:d0;CM-QOS=1.1;CM-VER=3.0;​
17/01/2022 23:59:41​	Warning!​	LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=40:0d:10:5a:f7:c3;CMTS-MAC=28:52:61:fa:05:d0;CM-QOS=1.1;CM-VER=3.0;​
17/01/2022 03:23:30​	critical​	No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:5a:f7:c3;CMTS-MAC=28:52:61:fa:05:d0;CM-QOS=1.1;CM-VER=3.0;​
16/01/2022 20:54:23​	Warning!​	RCS Partial Service;CM-MAC=40:0d:10:5a:f7:c3;CMTS-MAC=28:52:61:fa:05:d0;CM-QOS=1.1;CM-VER=3.0;​
16/01/2022 11:11:18​	critical​	No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:5a:f7:c3;CMTS-MAC=28:52:61:fa:05:d0;CM-QOS=1.1;CM-VER=3.0;​
15/01/2022 10:34:51​	notice​	LAN login Success;CM-MAC=40:0d:10:5a:f7:c3;CMTS-MAC=28:52:61:fa:05:d0;CM-QOS=1.1;CM-VER=3.0;​
14/01/2022 03:07:24​	critical​	No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:5a:f7:c3;CMTS-MAC=28:52:61:fa:05:d0;CM-QOS=1.1;CM-VER=3.0;​
13/01/2022 16:45:41​	notice​	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=40:0d:10:5a:f7:c3;CMTS-MAC=28:52:61:fa:05:d0;CM-QOS=1.1;CM-VER=3.0;​
13/01/2022 16:45:41​	Error​	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=40:0d:10:5a:f7:c3;CMTS-MAC=28:52:61:fa:05:d0;CM-QOS=1.1;CM-VER=3.0;​
12/01/2022 18:35:31​	critical​	No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:5a:f7:c3;CMTS-MAC=28:52:61:fa:05:d0;CM-QOS=1.1;CM-VER=3.0;​
11/01/2022 19:15:23​	notice​	LAN login Success;CM-MAC=40:0d:10:5a:f7:c3;CMTS-MAC=28:52:61:fa:05:d0;CM-QOS=1.1;CM-VER=3.0;​
11/01/2022 15:35:4​	critical​	No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:5a:f7:c3;CMTS-MAC=28:52:61:fa:05:d0;CM-QOS=1.1;CM-VER=3.0;​

 

[ColinTaylor]

That looks OK. There was only one outage on the 16th. It doesn't coincide with the LINK DOWN messages in the router log, so I'm assuming that's just you unplugging the modem. That was a bit of a long shot anyway given that it's not effecting any of your other devices.

This problem was happening even before you had the Asus router? So I think we can eliminate the router as the problem. The only things left would be some sort of software running on the PC or a hardware issue (e.g. PSU). Perhaps you could try booting the PC from a Live Linux image and seeing if the problem goes away.

 

[Chaarliie]

That looks OK. There was only one outage on the 16th. It doesn't coincide with the LINK DOWN messages in the router log, so I'm assuming that's just you unplugging the modem. That was a bit of a long shot anyway given that it's not effecting any of your other devices.

This problem was happening even before you had the Asus router? So I think we can eliminate the router as the problem. The only things left would be some sort of software running on the PC or a hardware issue (e.g. PSU). Perhaps you could try booting the PC from a Live Linux image and seeing if the problem goes away.

So went with the Linux bootable USB route and running ubuntu on it right now and have done so far 2500 pings to googles DNS server and has not dropped as of yet