F5F Stay Refreshed Power Users Networks Problem with Ping connections

Problem with Ping connections

Problem with Ping connections

M
mr_azitium
Member
95
06-20-2016, 04:47 AM
#1
Recently I experience about 200-300 ping while gaming on my computer, whereas my dad's system used to have lower than 50. The screenshots indicate 50-60 ping, but during gameplay it spikes significantly (as you mentioned). Using Ethernet instead of Wi-Fi increases the ping even more. I've installed the motherboard drivers but they don't load. (screenshot below) With Ethernet vs Without Ethernet. When I run "AsusSetup" as admin and click allow after permission prompt, nothing happens, not even after restarting. My motherboard link: https://www.amazon.com/dp/B08T6H14RR?tag...th=1&psc=1 My router link: https://www.amazon.com/NETGEAR-Nighthawk...B00KWHMR6G
M
mr_azitium
06-20-2016, 04:47 AM #1

Recently I experience about 200-300 ping while gaming on my computer, whereas my dad's system used to have lower than 50. The screenshots indicate 50-60 ping, but during gameplay it spikes significantly (as you mentioned). Using Ethernet instead of Wi-Fi increases the ping even more. I've installed the motherboard drivers but they don't load. (screenshot below) With Ethernet vs Without Ethernet. When I run "AsusSetup" as admin and click allow after permission prompt, nothing happens, not even after restarting. My motherboard link: https://www.amazon.com/dp/B08T6H14RR?tag...th=1&psc=1 My router link: https://www.amazon.com/NETGEAR-Nighthawk...B00KWHMR6G

L
131
06-20-2016, 05:03 AM
#2
This could be unrelated to the driver itself. If you're playing online or connecting to servers, knowing your local network setup matters. Tracing data can clarify if the problem lies with your home environment or with your internet service provider. Tools like WinMTR or built-in tracert commands might reveal whether the issue is local or caused by your ISP. Services such as Google, Cloudflare, and Quad9 DNS servers generally point to a distant location. Try tracing to public DNS addresses like 8.8.8.8, 1.1.1.1, or 9.9.9.9. Linux Fedora maintains its hosting remotely, so checking www.fedora.com should show an international or distant view. If WinMTR runs, each line indicates a point along your connection path—often starting with your home router and ending with your ISP. Problems beyond the first line suggest contacting your ISP support. Be aware that heavy users on the same network may slow things down, typically resulting in 250-350ms to local servers. The simplest fix is disconnecting all devices (including Wi-Fi) and retesting for clearer results. It’s possible drivers are involved, but they’re less likely compared to network or ISP issues. Your findings seem close enough that I’d focus on tracing your data flow rather than jumping to driver troubleshooting. Hope this helps a bit!
L
lunathealicorn
06-20-2016, 05:03 AM #2

This could be unrelated to the driver itself. If you're playing online or connecting to servers, knowing your local network setup matters. Tracing data can clarify if the problem lies with your home environment or with your internet service provider. Tools like WinMTR or built-in tracert commands might reveal whether the issue is local or caused by your ISP. Services such as Google, Cloudflare, and Quad9 DNS servers generally point to a distant location. Try tracing to public DNS addresses like 8.8.8.8, 1.1.1.1, or 9.9.9.9. Linux Fedora maintains its hosting remotely, so checking www.fedora.com should show an international or distant view. If WinMTR runs, each line indicates a point along your connection path—often starting with your home router and ending with your ISP. Problems beyond the first line suggest contacting your ISP support. Be aware that heavy users on the same network may slow things down, typically resulting in 250-350ms to local servers. The simplest fix is disconnecting all devices (including Wi-Fi) and retesting for clearer results. It’s possible drivers are involved, but they’re less likely compared to network or ISP issues. Your findings seem close enough that I’d focus on tracing your data flow rather than jumping to driver troubleshooting. Hope this helps a bit!

M
Mac_Plays
Junior Member
8
06-21-2016, 04:55 PM
#3
I’m playing online on servers around the world. I ran some tests to see actual performance. Here are the results: 68 ms on my PC via Wi-Fi, 112 ms via Ethernet, 86 ms on my dad’s PC over Wi-Fi, and 87 ms on his PC using Ethernet. On his side, the ping is a bit lower with Ethernet, while my PC shows a noticeable difference between Wi-Fi and Ethernet. I did this when most people are working, so speeds seem better and ping lower then before.
M
Mac_Plays
06-21-2016, 04:55 PM #3

I’m playing online on servers around the world. I ran some tests to see actual performance. Here are the results: 68 ms on my PC via Wi-Fi, 112 ms via Ethernet, 86 ms on my dad’s PC over Wi-Fi, and 87 ms on his PC using Ethernet. On his side, the ping is a bit lower with Ethernet, while my PC shows a noticeable difference between Wi-Fi and Ethernet. I did this when most people are working, so speeds seem better and ping lower then before.

A
AzuzzSaphixx
Member
55
06-21-2016, 09:39 PM
#4
Suggest using <pathping> alongside <tracert> for a more precise analysis of your connection problems. The drop in ping you’re seeing with direct connectivity seems unusual, as it typically improves and might point to an issue with your cable, modem, switch, or NIC. It could also be related to timing—testing at different times and the cable check coinciding with higher network traffic. Could help clarifying if this issue persists across all your applications or is limited to this specific game? If it’s tied to that game, does it only happen when playing on an international server? Running <tracert> or <pathping> will reveal whether the latency peak appears in the initial or final hops. This might prompt your ISP to address either your connection or a nearby network node. What time do you encounter this problem, and does your ping vary noticeably throughout the day? That last point is interesting—during a summer heatwave with some underground nodes overheating between 4–6 PM daily, we saw slowdowns, jitter, and even complete outages. It’s surprising how quickly things can be resolved when the creators of Marvel movies get involved.
A
AzuzzSaphixx
06-21-2016, 09:39 PM #4

Suggest using <pathping> alongside <tracert> for a more precise analysis of your connection problems. The drop in ping you’re seeing with direct connectivity seems unusual, as it typically improves and might point to an issue with your cable, modem, switch, or NIC. It could also be related to timing—testing at different times and the cable check coinciding with higher network traffic. Could help clarifying if this issue persists across all your applications or is limited to this specific game? If it’s tied to that game, does it only happen when playing on an international server? Running <tracert> or <pathping> will reveal whether the latency peak appears in the initial or final hops. This might prompt your ISP to address either your connection or a nearby network node. What time do you encounter this problem, and does your ping vary noticeably throughout the day? That last point is interesting—during a summer heatwave with some underground nodes overheating between 4–6 PM daily, we saw slowdowns, jitter, and even complete outages. It’s surprising how quickly things can be resolved when the creators of Marvel movies get involved.