Random Request Timeout when pinging my router 192.168.1.1

Toggle sidebar Toggle sidebar
C

curiousbob

Prominent
Apr 10, 2017
3
0
510
Recently, I'm having random lags/delays/packet loss so I went to speedtest.net to check my speed. My speed result is good, like my normal internet speed which is around 90mbps. So the next thing I did is to ping google and that's where I found out I am getting Request Timeout even though my internet speed is fast. So I called my ISP and reported the problem, they said they will check the lines and configurations and so on. Now five days have passed and they haven't done a thing. So out of curiosity, I tried to directly ping my router 192.168.1.1 and to my surprise I'm getting random request timeout too. I also tried pinging other PC on the network but I get no request timeout. Now I wonder what could be the problem. Anyone pros out there can help me out? Thanks
 
Solution
Ralston18
The ISP can only help up to and including the last device that is theirs with respect to your network.

That device may be a modem, modem/router, or router.

And the ISP will most likely point a finger at any device you are using especially in lieu of using (renting) their device.

For reference purposes:

http://www.brainbell.com/tutorials/Networking/The_Request_Timed_Out_Message.html

What I understand to be happening is that your PC is failing to sometimes either receive or to recognize a response from the target device being pinged. That device being either the router or the google.com server.

And that failure happening only on one network PC with both wired and wireless does suggest a problem within the PC.

Run "ipconfig /all"...
Sort by date Sort by votes
Ralston18

Ralston18

Titan
Moderator
Oct 11, 2014
34,801
3,305
146,290
What do your ping results actually look like?

From my PC:

PS C:\WINDOWS\system32> ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

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

Try pinging your router from the other system(s) on your network.

Look for a pattern. However the first thing I would suggest is to check is the connection between your PC and the router.

Wired: Secure the ethernet cable plugs, swap ethernet cables, check ethernet wall ports if used.

Wireless: Move the wireless adapter if possible. Use extension cables for USB on a USB wireless adapter. Or antenna extensions for a PCIx based wireless adapter.

For both wired and wireless, verify the adapter configurations. May even need to reinstall the applicable drivers.

The idea being to narrow down the problem to a specific connection or device within your network.

Your ISP cannot (and willnot) help with problems within your network.

 
Upvote 0 Downvote
C

curiousbob

Prominent
Apr 10, 2017
3
0
510
I already tried pinging the other PCs on my network and I'm not getting any request timeout. The only time I get request timeout is when I ping google.com and my router. I also tried pinging using wireless and I'm getting Request Timeout too. So maybe the problem is on the ISP because my network is working fine?
 
Upvote 0 Downvote
Ralston18

Ralston18

Titan
Moderator
Oct 11, 2014
34,801
3,305
146,290
The ISP can only help up to and including the last device that is theirs with respect to your network.

That device may be a modem, modem/router, or router.

And the ISP will most likely point a finger at any device you are using especially in lieu of using (renting) their device.

For reference purposes:

http://www.brainbell.com/tutorials/Networking/The_Request_Timed_Out_Message.html

What I understand to be happening is that your PC is failing to sometimes either receive or to recognize a response from the target device being pinged. That device being either the router or the google.com server.

And that failure happening only on one network PC with both wired and wireless does suggest a problem within the PC.

Run "ipconfig /all" (without quotes) from the command prompt on both your PC getting Request tiimeouts and the other PC that is not getting Request timeouts.

Compare wired to wired and wireless to wireless as applicable.

Study the results of ipconfig /all and look for some configuration difference within the adapter settings. Likewise use the Network and Sharing Center window to open and compare the Network adapter settings and properties.

 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom