Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

High ping to router


  • Please log in to reply
8 replies to this topic

#1 nickware

nickware

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:05:01 PM

Posted 10 December 2013 - 03:27 PM

Hi,

 

I have a recently started getting over a 35ms ping to my router, which has been running DD-WRT v24-sp2 (04/13/11) std for over a year.  This happens on a wired or wireless connection to the router and from multiple computers connected to it.  Here is a log from my ping of 192.168.1.1 -t

 

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=35ms TTL=64
Reply from 192.168.1.1: bytes=32 time=36ms TTL=64
Reply from 192.168.1.1: bytes=32 time=36ms TTL=64
Reply from 192.168.1.1: bytes=32 time=111ms TTL=64
Reply from 192.168.1.1: bytes=32 time=35ms TTL=64
Reply from 192.168.1.1: bytes=32 time=35ms TTL=64
Reply from 192.168.1.1: bytes=32 time=127ms TTL=64
Reply from 192.168.1.1: bytes=32 time=35ms TTL=64
Reply from 192.168.1.1: bytes=32 time=35ms TTL=64
Reply from 192.168.1.1: bytes=32 time=106ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
Reply from 192.168.1.1: bytes=32 time=36ms TTL=64
Reply from 192.168.1.1: bytes=32 time=65ms TTL=64
Reply from 192.168.1.1: bytes=32 time=35ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
Reply from 192.168.1.1: bytes=32 time=36ms TTL=64
Reply from 192.168.1.1: bytes=32 time=35ms TTL=64
Reply from 192.168.1.1: bytes=32 time=109ms TTL=64
Reply from 192.168.1.1: bytes=32 time=36ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
Reply from 192.168.1.1: bytes=32 time=36ms TTL=64
Reply from 192.168.1.1: bytes=32 time=36ms TTL=64
Reply from 192.168.1.1: bytes=32 time=210ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
 
 
and a tracert to 8.8.8.8:
 
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
 
  1     3 ms     3 ms     3 ms  DD-WRT [192.168.1.1]
  2    38 ms    34 ms    37 ms  10.102.32.1
  3    39 ms    37 ms    37 ms  68.13.10.113
  4    43 ms    35 ms    35 ms  68.13.8.253
  5    53 ms    53 ms    53 ms  68.1.5.140
  6    52 ms    50 ms    93 ms  72.14.212.233
  7    66 ms    51 ms    51 ms  209.85.244.120
  8    55 ms    56 ms    53 ms  72.14.237.219
  9    60 ms    56 ms    67 ms  209.85.243.178
 10   630 ms    57 ms    61 ms  216.239.46.63
 11     *        *        *     Request timed out.
 12    59 ms    36 ms    43 ms  google-public-dns-a.google.com [8.8.8.8]
 
Trace complete.
 
I have tried bouncing the router, cable modem, computers, etc.  Any ideas would be greatly appreciated, thanks!

Edited by nickware, 10 December 2013 - 03:28 PM.


BC AdBot (Login to Remove)

 


#2 Trakeen

Trakeen

  • Members
  • 126 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Tyler, TX
  • Local time:05:01 PM

Posted 11 December 2013 - 03:02 AM

Is it only one computer on the network having this problem or multiples?  Kind of strange that the tracert reported a much shorter time delay than your ping.

 

One simple suggestion, unplug your router for about 30 seconds and plug it back in.  I know it sounds kinda silly, but I was at a job once, where one computer could see every other computer on the network but nobody could see the computer or communicate with it.  Rebooted the router and, magic!  There went a couple of hours...



#3 nickware

nickware
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:05:01 PM

Posted 11 December 2013 - 09:58 AM

Thanks for your reply.  I thought the same thing about the tracert being a shorter time.  It's almost like the ping to 192.168.1.1 is returning the results from the second address on the tracert, 10.102.32.1.  I'm not sure what that address is.  I just have the router and then my cable modem.

 

It is all computers on my network, both wired and wireless.  The roku has been buffering lately too when playing content locally (Plex) and on the internet (Netflix).  I have tried unplugging and restarting the router many times -- no luck.

 

Any more ideas?  Thanks!



#4 Trakeen

Trakeen

  • Members
  • 126 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Tyler, TX
  • Local time:05:01 PM

Posted 16 December 2013 - 02:38 AM

What brand / model router?  I've seen some Belkins do this after about 6 months of use.  If you have a second router somewhere I would try it out and see if there's any difference.

 

Would give more ideas, but headed out the door right now.



#5 nickware

nickware
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:05:01 PM

Posted 16 December 2013 - 09:46 AM

It was an Asus RT-N10+.  I went ahead and picked up a new router and it's been running all weekend without any issues.  Thanks again for your help.


Edited by nickware, 16 December 2013 - 02:18 PM.


#6 Erin Walsh

Erin Walsh

  • Banned Spammer
  • 33 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:05:01 PM

Posted 16 December 2013 - 10:40 AM

Yeah, it sounds like a good reset is in order.  Electronics respond well to a little rest and time to reset...kind of like people do.  Good Luck!



#7 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:11:01 PM

Posted 16 December 2013 - 01:49 PM

Have you tried updating to the latest DD-WRT that is available for your router?

#8 nickware

nickware
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:05:01 PM

Posted 16 December 2013 - 02:26 PM

Actually, I did upgrade to a DD-WRT version dated 2013-04-22 and it solved my issue on all computers & devices in my house, except a old Dell D620 laptop... it was getting pings in the 400 - 600 ms with lots of packet loss (previous it and all other computers were getting 33 - 40ms pings).  I also wiped that computer and installed a fresh copy of Ubuntu and Windows 7 (to rule out malware and OS issues).  Both OSes had the high ping.

 

(I should add, I only tried wireless on the 2013-04-22 DD-WRT with the Dell Laptop)


Edited by nickware, 16 December 2013 - 02:27 PM.


#9 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:11:01 PM

Posted 16 December 2013 - 04:13 PM

Can you try the lap top via wired?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users