F5F Stay Refreshed Power Users Networks Request timing failed during a ping to www.google.com -t in the command prompt.

Request timing failed during a ping to www.google.com -t in the command prompt.

Request timing failed during a ping to www.google.com -t in the command prompt.

6
6Toribella
Junior Member
21
01-08-2016, 06:02 PM
#1
Hey there, I see you're really struggling with your gaming experience. You've already tried a lot of fixes—network reset, router changes, different cables, PC reboots, and even command prompts for flushing services—but the ping still times out every few attempts. It's frustrating when nothing seems to work. Let's figure this out together. Have you checked if your internet speed meets the minimum requirements for gaming? Also, try restarting your gaming device or switching to a wired connection if possible. If the issue persists, it might be worth checking your modem/router settings or contacting your ISP for further assistance.
6
6Toribella
01-08-2016, 06:02 PM #1

Hey there, I see you're really struggling with your gaming experience. You've already tried a lot of fixes—network reset, router changes, different cables, PC reboots, and even command prompts for flushing services—but the ping still times out every few attempts. It's frustrating when nothing seems to work. Let's figure this out together. Have you checked if your internet speed meets the minimum requirements for gaming? Also, try restarting your gaming device or switching to a wired connection if possible. If the issue persists, it might be worth checking your modem/router settings or contacting your ISP for further assistance.

S
selamo
Member
59
01-10-2016, 05:55 PM
#2
What is your network configuration? Are you linked through Wi-Fi or an Ethernet cable? Do you have powerline adapters set up? What kind of ISP connection do you use (coaxial, VDSL/ADSL, fiber, satellite, 4G/5G, dial-up)? Does the issue appear when another device is connected, such as a phone, another PC, or a laptop? Speed tests or performance checks could be useful. Initially, you might want to run a ping test to your router (ping -t 192.168.1.1 or 192.168.0.1 or similar) to confirm the problem isn’t between your device and the router. Then consider switching DNS servers—try 1.1.1.1 and 1.0.0.1 for Cloudflare, or 8.8.8.8 and 8.8.4.4 for Google DNS—and clear the cache afterward. You could also use Cloudflare Warp. The goal is to eliminate any issues caused by your ISP’s DNS servers or connection throttling.
S
selamo
01-10-2016, 05:55 PM #2

What is your network configuration? Are you linked through Wi-Fi or an Ethernet cable? Do you have powerline adapters set up? What kind of ISP connection do you use (coaxial, VDSL/ADSL, fiber, satellite, 4G/5G, dial-up)? Does the issue appear when another device is connected, such as a phone, another PC, or a laptop? Speed tests or performance checks could be useful. Initially, you might want to run a ping test to your router (ping -t 192.168.1.1 or 192.168.0.1 or similar) to confirm the problem isn’t between your device and the router. Then consider switching DNS servers—try 1.1.1.1 and 1.0.0.1 for Cloudflare, or 8.8.8.8 and 8.8.4.4 for Google DNS—and clear the cache afterward. You could also use Cloudflare Warp. The goal is to eliminate any issues caused by your ISP’s DNS servers or connection throttling.

E
ErenKartal
Member
161
01-11-2016, 02:25 AM
#3
Does it also stop when you use "ping 8.8.8.8 -t"? Or only when you send a name like www.google.com? If yes, then this isn't about DNS. Are there any interruptions when you reach your default gateway? If not, proceed with a "tracert 8.8.8.8" which will show the path through all intermediate devices. Then run ping -t each hop one by one in separate windows. Some connections may not respond at all—ignore them. Focus on those that do. Check if any timeouts occur and whether they happen together or separately. If you see drops to your default gateway, it likely points to your local network issue, not the ISP. Test from another device to confirm. Possible causes include a faulty cable, problematic switch port, Wi-Fi interference, or signal instability—though the latter seems unlikely given the concerns.
E
ErenKartal
01-11-2016, 02:25 AM #3

Does it also stop when you use "ping 8.8.8.8 -t"? Or only when you send a name like www.google.com? If yes, then this isn't about DNS. Are there any interruptions when you reach your default gateway? If not, proceed with a "tracert 8.8.8.8" which will show the path through all intermediate devices. Then run ping -t each hop one by one in separate windows. Some connections may not respond at all—ignore them. Focus on those that do. Check if any timeouts occur and whether they happen together or separately. If you see drops to your default gateway, it likely points to your local network issue, not the ISP. Test from another device to confirm. Possible causes include a faulty cable, problematic switch port, Wi-Fi interference, or signal instability—though the latter seems unlikely given the concerns.