Question Ethernet speed randomly and drastically drops ?

Apr 13, 2023
14
1
25
For some context I recently moved into a newly built apartment. Pre-installed in every unit is an Xfinity xFi Gateway with Cat 6 ethernet routed through the walls to various parts of the apartment. On my internet plan I selected the 800Mbps option, and over wifi speeds are pretty reliable. My issue begins when I plug my PC into the LAN port in the wall.

For the past few days my speeds have been all over the place. Today I ran 10 internet speed tests consecutively, and I've attached screenshots. It starts at around 800Mbps and immediately drops to 0.5Mbps the next test, and it has been doing this for the past few days (see Imgur album for the other trials). If I'm not mistaken, I should be getting consistent/near 800Mpbs speeds through ethernet every time, as I am the only person on the network. I've tried:

  • using a different ethernet cable,
  • using a USB wifi adapter,
  • plugging my PC directly into the router,
  • tried the different ethernet ports on the router,
  • updating my Realtek PCIe GbE Controller drivers, but my speeds are the same.
  • I tried going through Xfinity Assistant, and after restarting the router and running signal health checks, it told me my router is outputting my plan speed.

So this leads me to believe something is wrong with my PC, as not even the USB wifi adapter could fix my problems (the wifi works fine on my mobile devices and smart TV). I know my ethernet connection can supply around 800Mbps, but I'm not sure why it drastically drops to 300Mbps and sometimes even as low as 0.5Mbps as seen in the screenshots.

Here are my PC's specs if that helps:

Motherboard: MSI B350 Tomahawk
CPU: AMD Ryzen 7 1700
GPU: GTX 1070 Ti 8GB
RAM: G.Skill Flare X 16GB
PSU: Corsair RM850x
OS: Windows 10 Pro

If anyone can help me that would be greatly appreciated.
 

Ralston18

Titan
Moderator
Which Xfinity Gateway?

On your PC run "ipconfig /all" (without quotes) via the Command Prompt and post the results.

(Note: You should be able to copy and paste the results with no need to retype everything.)

That all said then this....

"My issue begins when I plug my PC into the LAN port in the wall."

Wall LAN port may not be properly punched in.

Or the Ethernet wire run to that wall port may be bad.

Or the patch panel connnection at the other end may be bad.

Report the problem to building management. The problem may not be on your end,

The key is for you to narrow down the potential culprits.

Prove/discover that everything works unless the wall LAN port in the wall is involved.
 
Apr 13, 2023
14
1
25
Which Xfinity Gateway?

On your PC run "ipconfig /all" (without quotes) via the Command Prompt and post the results.

(Note: You should be able to copy and paste the results with no need to retype everything.)

That all said then this....

"My issue begins when I plug my PC into the LAN port in the wall."

Wall LAN port may not be properly punched in.

Or the Ethernet wire run to that wall port may be bad.

Or the patch panel connnection at the other end may be bad.

Report the problem to building management. The problem may not be on your end,

The key is for you to narrow down the potential culprits.

Prove/discover that everything works unless the wall LAN port in the wall is involved.
Windows IP Configuration Host Name . . . . . . . . . . . . : Gunnar-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : hsd1.nm.comcast.net Ethernet adapter Ethernet: Connection-specific DNS Suffix . : hsd1.nm.comcast.net Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller Physical Address. . . . . . . . . : 30-9C-23-07-3C-5E DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2601:8c0:801:e4a0::b138(Preferred) Lease Obtained. . . . . . . . . . : Thursday, March 14, 2024 6:38:20 PM Lease Expires . . . . . . . . . . : Monday, March 18, 2024 4:35:25 PM IPv6 Address. . . . . . . . . . . : 2601:8c0:801:e4a0:67dd:1e6:7cf8:5649(Preferred) IPv6 Address. . . . . . . . . . . : 2601:8c0:880:b350:4f5b:5c65:8e4e:49c7(Preferred) Temporary IPv6 Address. . . . . . : 2601:8c0:801:e4a0:e069:6771:4ecc:f457(Preferred) Temporary IPv6 Address. . . . . . : 2601:8c0:880:b350:e069:6771:4ecc:f457(Preferred) Link-local IPv6 Address . . . . . : fe80::a3ff:4a6f:df59:9c9a%21(Preferred) IPv4 Address. . . . . . . . . . . : 10.0.0.108(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Thursday, March 14, 2024 6:38:18 PM Lease Expires . . . . . . . . . . : Saturday, March 16, 2024 6:38:17 PM Default Gateway . . . . . . . . . : fe80::1e93:7cff:fec5:372f%21 fe80::aa70:5dff:fe38:2c3%21 10.0.0.1 DHCP Server . . . . . . . . . . . : 10.0.0.1 DHCPv6 IAID . . . . . . . . . . . : 36740131 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-00-05-37-30-9C-23-07-3C-5E DNS Servers . . . . . . . . . . . : 2001:558:feed::1 2001:558:feed::2 75.75.75.75 75.75.76.76 2601:8c0:880:b350:1e93:7cff:fec5:372f 2001:558:feed::1 2001:558:feed::2 NetBIOS over Tcpip. . . . . . . . : Enabled

The Gateway's model number is XB7.

My problem still persisted when I plugged my PC directly into the Gateway, so is it safe to say the in-wall lines and LAN ports are fine? Thanks for your reply.
 

Ralston18

Titan
Moderator
For the moment yes.

With the current PC directly connected into the Gateway run:

ping
pathping
tracert

Target Google at 8.8.8.8 or 8.8.4.4

Post the results.

The objective being to learn more about the path(s) being used to reach Google's website.

Especially the first few "hops".

After which neither you nor your ISP has control of anything.

Disabling IPv6 has proven helpful in some circumstances. No harm in trying that.

Hold on that until more is known,
 
Apr 13, 2023
14
1
25
For the moment yes.

With the current PC directly connected into the Gateway run:

ping
pathping
tracert

Target Google at 8.8.8.8 or 8.8.4.4

Post the results.

The objective being to learn more about the path(s) being used to reach Google's website.

Especially the first few "hops".

After which neither you nor your ISP has control of anything.

Disabling IPv6 has proven helpful in some circumstances. No harm in trying that.

Hold on that until more is known,
C:\Users\Gunnar>ping www.google.com Pinging www.google.com [2607:f8b0:400f:803::2004] with 32 bytes of data: Reply from 2607:f8b0:400f:803::2004: time=20ms Reply from 2607:f8b0:400f:803::2004: time=20ms Reply from 2607:f8b0:400f:803::2004: time=22ms Reply from 2607:f8b0:400f:803::2004: time=22ms Ping statistics for 2607:f8b0:400f:803::2004: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 20ms, Maximum = 22ms, Average = 21ms

C:\Users\Gunnar>pathping www.google.com Tracing route to www.google.com [2607:f8b0:400f:803::2004] over a maximum of 30 hops: 0 Gunnar-PC.hsd1.nm.comcast.net [2601:8c0:880:b350:e069:6771:4ecc:f457] 1 2601:8c0:880:b350:1e93:7cff:fec5:372f 2 2001:558:1024:68::3 3 po-306-406-rur202.[contained location].comcast.net [2001:558:42:200c::1] 4 po-2-rur201.[contained location].comcast.net [2001:558:40:5d::1] 5 po-200-xar01.[contained location].comcast.net [2001:558:40:21::1] 6 * * * Computing statistics for 125 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Gunnar-PC.hsd1.nm.comcast.net [2601:8c0:880:b350:e069:6771:4ecc:f457] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% 2601:8c0:880:b350:1e93:7cff:fec5:372f 0/ 100 = 0% | 2 --- 100/ 100 =100% 100/ 100 =100% 2001:558:1024:68::3 0/ 100 = 0% | 3 9ms 0/ 100 = 0% 0/ 100 = 0% po-306-406-rur202.[contained location].comcast.net [2001:558:42:200c::1] 0/ 100 = 0% | 4 10ms 0/ 100 = 0% 0/ 100 = 0% po-2-rur201.[contained location].comcast.net [2001:558:40:5d::1] 0/ 100 = 0% | 5 10ms 0/ 100 = 0% 0/ 100 = 0% po-200-xar01.[contained location].comcast.net [2001:558:40:21::1] Trace complete.

C:\Users\Gunnar>tracert www.google.com Tracing route to www.google.com [2607:f8b0:400f:804::2004] over a maximum of 30 hops: 1 <1 ms 1 ms 1 ms 2601:8c0:880:b350:1e93:7cff:fec5:372f 2 9 ms 12 ms 13 ms 2001:558:1024:68::2 3 10 ms 13 ms 12 ms po-306-405-rur201.[contained location].comcast.net [2001:558:42:83e::1] 4 11 ms 12 ms 13 ms po-200-xar01.[contained location].comcast.net [2001:558:40:21::1] 5 12 ms * * be-306-arsc1.[contained location].comcast.net [2001:558:40:26::1] 6 20 ms 22 ms 21 ms be-36821-cs02.1601milehigh.co.ibone.comcast.net [2001:558:3:305::1] 7 18 ms 22 ms 20 ms be-1213-cr13.1601milehigh.co.ibone.comcast.net [2001:558:3:1d9::2] 8 18 ms 21 ms 16 ms be-301-cr13.champa.co.ibone.comcast.net [2001:558:3:130::1] 9 21 ms 22 ms 21 ms be-1313-cs03.champa.co.ibone.comcast.net [2001:558:3:17a::1] 10 21 ms 21 ms 21 ms be-3311-pe11.910fifteenth.co.ibone.comcast.net [2001:558:3:5e::2] 11 20 ms 21 ms 21 ms as15133-5-c.nota.fl.ibone.comcast.net [2001:559::63a] 12 20 ms 21 ms 17 ms 2607:f8b0:82bb::1 13 * 29 ms 21 ms 2001:4860:0:1::5808 14 28 ms 42 ms 30 ms 2001:4860:0:1::6562 15 19 ms 21 ms 17 ms 2001:4860:0:1::7ae1 16 21 ms 21 ms 20 ms 2001:4860:0:1::5839 17 19 ms 18 ms 22 ms den16s08-in-x04.1e100.net [2607:f8b0:400f:804::2004] Trace complete.

I removed some parts of the results that contain the city I live in. Hope that doesn't effect anything.
 

kanewolf

Titan
Moderator
C:\Users\Gunnar>ping www.google.com Pinging www.google.com [2607:f8b0:400f:803::2004] with 32 bytes of data: Reply from 2607:f8b0:400f:803::2004: time=20ms Reply from 2607:f8b0:400f:803::2004: time=20ms Reply from 2607:f8b0:400f:803::2004: time=22ms Reply from 2607:f8b0:400f:803::2004: time=22ms Ping statistics for 2607:f8b0:400f:803::2004: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 20ms, Maximum = 22ms, Average = 21ms

C:\Users\Gunnar>pathping www.google.com Tracing route to www.google.com [2607:f8b0:400f:803::2004] over a maximum of 30 hops: 0 Gunnar-PC.hsd1.nm.comcast.net [2601:8c0:880:b350:e069:6771:4ecc:f457] 1 2601:8c0:880:b350:1e93:7cff:fec5:372f 2 2001:558:1024:68::3 3 po-306-406-rur202.[contained location].comcast.net [2001:558:42:200c::1] 4 po-2-rur201.[contained location].comcast.net [2001:558:40:5d::1] 5 po-200-xar01.[contained location].comcast.net [2001:558:40:21::1] 6 * * * Computing statistics for 125 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Gunnar-PC.hsd1.nm.comcast.net [2601:8c0:880:b350:e069:6771:4ecc:f457] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% 2601:8c0:880:b350:1e93:7cff:fec5:372f 0/ 100 = 0% | 2 --- 100/ 100 =100% 100/ 100 =100% 2001:558:1024:68::3 0/ 100 = 0% | 3 9ms 0/ 100 = 0% 0/ 100 = 0% po-306-406-rur202.[contained location].comcast.net [2001:558:42:200c::1] 0/ 100 = 0% | 4 10ms 0/ 100 = 0% 0/ 100 = 0% po-2-rur201.[contained location].comcast.net [2001:558:40:5d::1] 0/ 100 = 0% | 5 10ms 0/ 100 = 0% 0/ 100 = 0% po-200-xar01.[contained location].comcast.net [2001:558:40:21::1] Trace complete.

C:\Users\Gunnar>tracert www.google.com Tracing route to www.google.com [2607:f8b0:400f:804::2004] over a maximum of 30 hops: 1 <1 ms 1 ms 1 ms 2601:8c0:880:b350:1e93:7cff:fec5:372f 2 9 ms 12 ms 13 ms 2001:558:1024:68::2 3 10 ms 13 ms 12 ms po-306-405-rur201.[contained location].comcast.net [2001:558:42:83e::1] 4 11 ms 12 ms 13 ms po-200-xar01.[contained location].comcast.net [2001:558:40:21::1] 5 12 ms * * be-306-arsc1.[contained location].comcast.net [2001:558:40:26::1] 6 20 ms 22 ms 21 ms be-36821-cs02.1601milehigh.co.ibone.comcast.net [2001:558:3:305::1] 7 18 ms 22 ms 20 ms be-1213-cr13.1601milehigh.co.ibone.comcast.net [2001:558:3:1d9::2] 8 18 ms 21 ms 16 ms be-301-cr13.champa.co.ibone.comcast.net [2001:558:3:130::1] 9 21 ms 22 ms 21 ms be-1313-cs03.champa.co.ibone.comcast.net [2001:558:3:17a::1] 10 21 ms 21 ms 21 ms be-3311-pe11.910fifteenth.co.ibone.comcast.net [2001:558:3:5e::2] 11 20 ms 21 ms 21 ms as15133-5-c.nota.fl.ibone.comcast.net [2001:559::63a] 12 20 ms 21 ms 17 ms 2607:f8b0:82bb::1 13 * 29 ms 21 ms 2001:4860:0:1::5808 14 28 ms 42 ms 30 ms 2001:4860:0:1::6562 15 19 ms 21 ms 17 ms 2001:4860:0:1::7ae1 16 21 ms 21 ms 20 ms 2001:4860:0:1::5839 17 19 ms 18 ms 22 ms den16s08-in-x04.1e100.net [2607:f8b0:400f:804::2004] Trace complete.

I removed some parts of the results that contain the city I live in. Hope that doesn't effect anything.
One thing I see is that your primary path is an IPv6 path. Try disabling IPv6 in the properties of the ethernet adapter.
See if we can force you to an IPv4 path. Those are often more consistent.
 
Apr 13, 2023
14
1
25
One thing I see is that your primary path is an IPv6 path. Try disabling IPv6 in the properties of the ethernet adapter.
See if we can force you to an IPv4 path. Those are often more consistent.
Disabled IPv6 in the ethernet adapter. Here's the results of the same tests.

C:\Users\Gunnar>ping www.google.com

Pinging www.google.com [142.250.72.68] with 32 bytes of data:
Reply from 142.250.72.68: bytes=32 time=24ms TTL=53
Reply from 142.250.72.68: bytes=32 time=25ms TTL=53
Reply from 142.250.72.68: bytes=32 time=25ms TTL=53
Reply from 142.250.72.68: bytes=32 time=22ms TTL=53

Ping statistics for 142.250.72.68:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 25ms, Average = 24ms

C:\Users\Gunnar>pathping www.google.com

Tracing route to www.google.com [142.250.72.68]
over a maximum of 30 hops:
0 Gunnar-PC.hsd1.nm.comcast.net [10.0.0.108]
1 10.0.0.1
2 100.92.205.130
3 po-306-405-rur201.[location].comcast.net [96.216.21.213]
4 po-200-xar01.[location].comcast.net [68.85.65.89]
5 be-306-arsc1.[location].comcast.net [96.108.43.101]
6 be-36831-cs03.1601milehigh.co.ibone.comcast.net [96.110.44.25]
7 be-1314-cr14.1601milehigh.co.ibone.comcast.net [96.110.39.122]
8 be-301-cr14.champa.co.ibone.comcast.net [96.110.39.1]
9 be-1314-cs03.champa.co.ibone.comcast.net [96.110.37.249]
10 be-3312-pe12.910fifteenth.co.ibone.comcast.net [96.110.33.138]
11 50.248.119.226
12 216.239.56.151
13 142.251.51.155
14 den16s09-in-f4.1e100.net [142.250.72.68]

Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Gunnar-PC.hsd1.nm.comcast.net [10.0.0.108]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 100.92.205.130
0/ 100 = 0% |
3 14ms 0/ 100 = 0% 0/ 100 = 0% po-306-405-rur201.[location].comcast.net [96.216.21.213]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% po-200-xar01.[location].comcast.net [68.85.65.89]
0/ 100 = 0% |
5 15ms 0/ 100 = 0% 0/ 100 = 0% be-306-arsc1.[location].comcast.net [96.108.43.101]
0/ 100 = 0% |
6 22ms 0/ 100 = 0% 0/ 100 = 0% be-36831-cs03.1601milehigh.co.ibone.comcast.net [96.110.44.25]
0/ 100 = 0% |
7 23ms 0/ 100 = 0% 0/ 100 = 0% be-1314-cr14.1601milehigh.co.ibone.comcast.net [96.110.39.122]
0/ 100 = 0% |
8 23ms 0/ 100 = 0% 0/ 100 = 0% be-301-cr14.champa.co.ibone.comcast.net [96.110.39.1]
0/ 100 = 0% |
9 23ms 0/ 100 = 0% 0/ 100 = 0% be-1314-cs03.champa.co.ibone.comcast.net [96.110.37.249]
0/ 100 = 0% |
10 23ms 0/ 100 = 0% 0/ 100 = 0% be-3312-pe12.910fifteenth.co.ibone.comcast.net [96.110.33.138]
0/ 100 = 0% |
11 22ms 0/ 100 = 0% 0/ 100 = 0% 50.248.119.226
0/ 100 = 0% |
12 23ms 0/ 100 = 0% 0/ 100 = 0% 216.239.56.151
0/ 100 = 0% |
13 22ms 0/ 100 = 0% 0/ 100 = 0% 142.251.51.155
0/ 100 = 0% |
14 23ms 0/ 100 = 0% 0/ 100 = 0% den16s09-in-f4.1e100.net [142.250.72.68]

Trace complete.

C:\Users\Gunnar>tracert www.google.com

Tracing route to www.google.com [142.250.72.36]
over a maximum of 30 hops:

1 6 ms 6 ms 5 ms 10.0.0.1
2 19 ms 15 ms 17 ms 100.92.205.130
3 12 ms 12 ms 13 ms po-306-405-rur201.[location].comcast.net [96.216.21.213]
4 14 ms 11 ms 12 ms po-200-xar01.[location].comcast.net [68.85.65.89]
5 14 ms 11 ms 13 ms be-306-arsc1.[location].comcast.net [96.108.43.101]
6 19 ms 20 ms 22 ms be-36821-cs02.1601milehigh.co.ibone.comcast.net [96.110.44.21]
7 25 ms 25 ms 25 ms be-1413-cr13.1601milehigh.co.ibone.comcast.net [96.110.39.110]
8 27 ms 26 ms 25 ms be-303-cr13.champa.co.ibone.comcast.net [96.110.36.201]
9 24 ms 25 ms 25 ms be-1313-cs03.champa.co.ibone.comcast.net [96.110.37.233]
10 25 ms 24 ms 27 ms be-2311-pe11.champa.co.ibone.comcast.net [96.110.40.170]
11 24 ms 25 ms 25 ms 75-149-231-178-static.hfc.comcastbusiness.net [75.149.231.178]
12 25 ms 22 ms 21 ms 216.239.54.63
13 23 ms 20 ms 22 ms 172.253.75.177
14 24 ms 25 ms 25 ms den16s08-in-f4.1e100.net [142.250.72.36]

Trace complete.

Something else I've experienced during speed tests -- sometimes the download speed starts high, around 800Mbps, and over the duration of the test descends. Not sure if that has anything to do with it.

I also ran a test on packetlosstest.com and this was the result. Does my issue relate to the results of the packet loss test?
 

Ralston18

Titan
Moderator
Noted:

"Something else I've experienced during speed tests -- sometimes the download speed starts high, around 800Mbps, and over the duration of the test descends. Not sure if that has anything to do with it."

Open either Task Manager or Resource Monitor and observe system performance. (You can also use Process Explorer - Microsoft, free.)

https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer

Use all three tools but only one tool at a time.

Open the tool window, do nothing and simply watch for a few minutes.

Leave the tool window open and visible. Run the speed test as you have been doing.

Watch for what, if anything, changes in the tool window.

The process may take a couple of tries to work out . The end objective simply to discover, if possible, what happens (or even stops happening) when the download speed drops.
 
Apr 13, 2023
14
1
25
That packet loss rate is way too high, probably bad patch or in-wall cable.

Download Realtek Diagnostics utility and test.

View: https://www.youtube.com/watch?v=nAPEMCKWCRg
Here are the results from the diagnostics test.

Also this morning I tried another packet loss test and it was 4.1% loss. I tried another one right after that and it was 71%.

Noted:

"Something else I've experienced during speed tests -- sometimes the download speed starts high, around 800Mbps, and over the duration of the test descends. Not sure if that has anything to do with it."

Open either Task Manager or Resource Monitor and observe system performance. (You can also use Process Explorer - Microsoft, free.)

https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer

Use all three tools but only one tool at a time.

Open the tool window, do nothing and simply watch for a few minutes.

Leave the tool window open and visible. Run the speed test as you have been doing.

Watch for what, if anything, changes in the tool window.

The process may take a couple of tries to work out . The end objective simply to discover, if possible, what happens (or even stops happening) when the download speed drops.
Graphs from Task Manager and Resource Monitor.

In Task Manager my tests were consistently ~330Mbps download. The speed would taper off towards the end in some of the tests. In Resource Monitor I had one test that was 800Mbps, and then the following test was like 100Mbps.

In Process Explorer I was having consistent 800Mbps tests and could not find anything that could be causing the issue.

Could it be Xfinity throttling my connection?
 
Last edited:
Apr 13, 2023
14
1
25
Show the Cable test part
Here.

Not sure that I understand the process being used.

However if downloading via steam, close Chrome beforehand.

Or vice versa.

Does the Ethernet graph/pattern change?
Sorry, steam and discord were open in the background. I closed them and tried again.

I was running the tests through Chrome, and actually I was having pretty consistent 800Mbps results this time. I then did the packet loss test and out of 3 trials my results were 36%, 0%, and 51% respectively. I then went back to the speed tests and started getting results all the way from 10Mbps to 300 to 800. So I'm pretty confused. The graphs were pretty much the same as the last tests. No weird spikes or out of place usage.
 

Ralston18

Titan
Moderator
Not familar with that Realtek Diagnostic test.....

What is the physical topology of your network?

For example:

ISP === (coax, DSL, fiber) ===> Modem ---->[WAN Port] Router [LAN Port] ----> [LAN Port] Office Wifi Access Point ~~~~> Wireless network devices

With other Router LAN ports -----> Wired network devices.


Edit and correct as necessary.

= = = =

Varying and inconsistent results suggest (to me anyway) a loose or problem connection somewhere.

Bad cable, bad connector, problem port, and so forth....
 

lantis3

Distinguished
Nov 5, 2015
856
146
19,070
See if set the speed of Realtek NIC at 1Gbps fixed the issue. Don't use Auto Negotiation.

YB0xRrY.png
 
Apr 13, 2023
14
1
25
Not familar with that Realtek Diagnostic test.....

What is the physical topology of your network?

For example:

ISP === (coax, DSL, fiber) ===> Modem ---->[WAN Port] Router [LAN Port] ----> [LAN Port] Office Wifi Access Point ~~~~> Wireless network devices

With other Router LAN ports -----> Wired network devices.


Edit and correct as necessary.

= = = =

Varying and inconsistent results suggest (to me anyway) a loose or problem connection somewhere.

Bad cable, bad connector, problem port, and so forth....
ISP - (coax) - > Gateway XB7 - > Wireless devices
Gateway LAN ports - > Office, living room, bedroom LAN ports - > Wired devices

See if set the speed of Realtek NIC at 1Gbps fixed the issue. Don't use Auto Negotiation.

YB0xRrY.png
I already tried this, didn't seem to fix my problem.

Based off the Realtek Diagnostic results, is there anything wrong with my network card?
 

Ralston18

Titan
Moderator
Check and trace your coax cables. Inside and outside. (Do so safely - no climbing on roofs, poles, etc..)

What you are looking for are any signs of damage, corrosion, rodent chews, pinched cables, kinked cables and the presence of any splitters.

A splitter being a very small devicve 2" x 3" with one coax cable going in and 2, 3, or 4 coax cables coming out. Sometimes many more.....

Splitters are very cheaply made and can (and do) go bad. What originally worked degrades over time and at some point problems begin.

Another thing to look for are unterminated coax cables. That is a cable just hanging out somewhere with nothing connected. There might be a dust cap on it but that is not sufficient

There should be terminantor caps unused coax connections.

FYI:

https://blog.solidsignal.com/tutori...dust cap is just,proper endpoint for a signal.

If Xfinity sends a tech then watch what they do. And make sure that the problem is resolved before they leave. Check everything.