How JustAnswer Works:

  • Ask an Expert
    Experts are full of valuable knowledge and are ready to help with any question. Credentials confirmed by a Fortune 500 verification firm.
  • Get a Professional Answer
    Via email, text message, or notification as you wait on our site.
    Ask follow up questions if you need to.
  • 100% Satisfaction Guarantee
    Rate the answer you receive.

Ask Claws224 Your Own Question

Claws224
Claws224, IEEE Network Engineer
Category: Networking
Satisfied Customers: 1256
Experience:  IEEE, Microsoft
5195814
Type Your Networking Question Here...
Claws224 is online now
A new question is answered every 9 seconds

Bizarre issue.. Whenever I add a router to my network eventually

Customer Question

Bizarre issue.. Whenever I add a router to my network eventually the ping starts going up from 50ms to 2-3k... If I just use modem to router direct connection, no issues. I've tried everything I know. 3 different routers, new modem... I've disconnected all devices from router except one to test - same thing.. high ping.. Resetting router pushed the MS back to normal for a bit.. but eventually it rises again on all 3 routers.. 2 of them are new... The high ping and time outs is on all devices, not just one.
Submitted: 7 months ago.
Category: Networking
Customer: replied 7 months ago.
btw, I tried new cable etc etc.
Expert:  Jason Jones replied 7 months ago.
Hello,I am the person that will be helping you today.May I ask for the brand and model name of the modem?I will be standing by, looking forward to your response.Thank you,Jason
Customer: replied 7 months ago.
Yes, one sec
Customer: replied 7 months ago.
motorolla 6141 surfboard - I've tried others to though, same issue. (older models I was using when the issue started)
Expert:  Jason Jones replied 7 months ago.
Thank you for the update. May I start a secure remote assistance session with you so that I can better help you resolve this problem? When the remote session begins, a chat window will appear that we can use to communicate with each other.
Customer: replied 7 months ago.
I can do what you need on my end - just let me know.. I'm a computer tech - just never seen an issue like this..
Expert:  Jason Jones replied 7 months ago.
Thank you for the update. I have seen this problem thousands of times. In each case, the culprit can be one of many. Have you verified that the modem itself is not the problem? Being that you are experiencing the same problem with different routers, it makes the common thread the modem.
Customer: replied 7 months ago.
Yes, if you read my initial question I think I put in there that I've tried a direct connect to modem, bypassing the routers. I also have tried 3 different modems.
Customer: replied 7 months ago.
Direct connection worked on all 3
Customer: replied 7 months ago.
if I add any router though.. the ping starts creeping up... from 50ms to 1-3 k... and timed outs happen etc etc
Expert:  Jason Jones replied 7 months ago.
I read the initial question. You stated that you tried 3 different routers and that it is a new modem. So, that tells me that you tested it with ONE modem and THREE routers. I am I mistaken?
Customer: replied 7 months ago.
3 modems, 3 routers
Customer: replied 7 months ago.
And it works with every single modem.
Customer: replied 7 months ago.
directly connected that is - bypassing routers
Customer: replied 7 months ago.
Add ANY router to any three of those modems and there are problems.
Expert:  Jason Jones replied 7 months ago.
Thank you for the update. Being that you have the same problem with all combinations of modems and routers, my next question is if you have tried using different Ethernet cables?
Customer: replied 7 months ago.
Yes. So let me update again. I've tried 3 different routers, 3 different modems and different cables - cat5, cat6. AND.. when I've tried it with a router I've only had ONE device connected to the router. The same device I would then connect directly to the modem. (I've also tried multiple different devices to rule out the device) same issue... Works great if I bypass the router.. (Regardless of the device I use to test it) Add a router.. and there Is trouble..
Customer: replied 7 months ago.
This also happens wired and wireless with devices.
Customer: replied 7 months ago.
I've tried macbooks, computers, ipads etc etc - same results
Customer: replied 7 months ago.
I've also tried shutting off the wifi on the routers..
Customer: replied 7 months ago.
Only temp fix is a reboot of the router
Expert:  Jason Jones replied 7 months ago.
Okay, it all sounds like everything is setup correctly. Do you still not wish to do the remote session?
Customer: replied 7 months ago.
Yeah, don't really want to pay for that.. as I don't think it's going to solve anything... If there is something you want me to check I can.
Customer: replied 7 months ago.
98.138.253.109: bytes=32 time=46ms TTL=51
Reply from 98.138.253.109: bytes=32 time=55ms TTL=51
Reply from 98.138.253.109: bytes=32 time=49ms TTL=51
Reply from 98.138.253.109: bytes=32 time=52ms TTL=51
Reply from 98.138.253.109: bytes=32 time=76ms TTL=51
Reply from 98.138.253.109: bytes=32 time=263ms TTL=51
Reply from 98.138.253.109: bytes=32 time=49ms TTL=51
Reply from 98.138.253.109: bytes=32 time=49ms TTL=51
Reply from 98.138.253.109: bytes=32 time=754ms TTL=51
Reply from 98.138.253.109: bytes=32 time=304ms TTL=51
Expert:  Jason Jones replied 7 months ago.
Everything is covered with a 100% guarantee. If I am not able to solve anything, you are refunded.
Customer: replied 7 months ago.
That's current - soon it will hit the 1k mark
Customer: replied 7 months ago.
What would you be doing that I can't do on my end?
Expert:  Jason Jones replied 7 months ago.
I would analyze the system.
Customer: replied 7 months ago.
What system? My entire router, modem, LAN? Can you be more specific?
Customer: replied 7 months ago.
And what would you be looking for that can cause my issue?
Expert:  Jason Jones replied 7 months ago.
All systems. I will be analyzing your modem, router, etc, everything. If you wish, I can opt out of the question and allow someone else to help that may have some extra insight that I don't have. I have seen similar problems thousands of times.
Customer: replied 7 months ago.
So basically if you can't find any issue with the remote I get all my money back? This is a sporadic issue - right now the ping is not terrible, it's almost perfect - but that can change on a dime..
Expert:  Jason Jones replied 7 months ago.
Yes, that is what I stated. So, there is no problem now? Is there any rhyme and/or reason as to when this problem occurs?
Customer: replied 7 months ago.
It never happens with a direct connection to modem - I've run continuous ping for a day with that setup. But it always happens when I add back the router. And resetting always fixes it for a while.. but eventually the problem comes back..
Expert:  Jason Jones replied 7 months ago.
So, it just eventually comes back randomly?
Customer: replied 7 months ago.
When the ping starts going up high and I get timed outs - I remove router and make direct connect to modem and it fixes it instantly.
Customer: replied 7 months ago.
Yes, it will eventually return
Expert:  Jason Jones replied 7 months ago.
When it returns, it does so at random times?
Customer: replied 7 months ago.
yes
Expert:  Jason Jones replied 7 months ago.
How long does it take for the problem to begin?
Customer: replied 7 months ago.
low ping, then up to high - that's the patten, Then remove router and use modem and that will fix it permanently
Customer: replied 7 months ago.
Sometimes minutes, sometimes it will work good for a few hours
Expert:  Jason Jones replied 7 months ago.
Thank you for the update. From here, it all sounds like everything is setup correctly. Without seeing the problem in action, there is nothing else I can do.For this reason, I am opting out of the question and allowing another expert the chance to help.The next expert will see all that is on this page, so there will be no need to repeat anything.When another expert picks this up, you will be notified by email.Thank you for your patience. - Jason
Customer: replied 7 months ago.
Ok thanks man
Customer: replied 7 months ago.
Here is what It looks like when it's acting up - Reply from 98.138.253.109: bytes=32 time=981ms TTL=51
Reply from 98.138.253.109: bytes=32 time=1568ms TTL=51
Reply from 98.138.253.109: bytes=32 time=1875ms TTL=51
Reply from 98.138.253.109: bytes=32 time=2262ms TTL=51
Reply from 98.138.253.109: bytes=32 time=2333ms TTL=51
Reply from 98.138.253.109: bytes=32 time=2364ms TTL=51
Reply from 98.138.253.109: bytes=32 time=2309ms TTL=51
Request timed out.
Reply from 98.138.253.109: bytes=32 time=2407ms TTL=51
Request timed out.
Request timed out.
Reply from 98.138.253.109: bytes=32 time=3282ms TTL=51
Reply from 98.138.253.109: bytes=32 time=196ms TTL=51
Reply from 98.138.253.109: bytes=32 time=113ms TTL=51
Reply from 98.138.253.109: bytes=32 time=97ms TTL=51
Reply from 98.138.253.109: bytes=32 time=211ms TTL=51
Reply from 98.138.253.109: bytes=32 time=300ms TTL=51
Reply from 98.138.253.109: bytes=32 time=371ms TTL=51
Reply from 98.138.253.109: bytes=32 time=479ms TTL=51
Reply from 98.138.253.109: bytes=32 time=821ms TTL=51
Reply from 98.138.253.109: bytes=32 time=1236ms TTL=51
Reply from 98.138.253.109: bytes=32 time=1665ms TTL=51
Reply from 98.138.253.109: bytes=32 time=2222ms TTL=51
Reply from 98.138.253.109: bytes=32 time=2224ms TTL=51
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 98.138.253.109: bytes=32 time=3453ms TTL=51
Reply from 98.138.253.109: bytes=32 time=493ms TTL=51
Reply from 98.138.253.109: bytes=32 time=352ms TTL=51
Reply from 98.138.253.109: bytes=32 time=369ms TTL=51
Reply from 98.138.253.109: bytes=32 time=1380ms TTL=51
Reply from 98.138.253.109: bytes=32 time=1640ms TTL=51
Reply from 98.138.253.109: bytes=32 time=1800ms TTL=51
Reply from 98.138.253.109: bytes=32 time=1952ms TTL=51
Customer: replied 7 months ago.
Reply from 74.125.196.103: bytes=32 time=49ms TTL=45
Reply from 74.125.196.103: bytes=32 time=49ms TTL=45
Reply from 74.125.196.103: bytes=32 time=61ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=48ms TTL=45
Reply from 74.125.196.103: bytes=32 time=48ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=50ms TTL=45
Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=44ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=57ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=44ms TTL=45
Reply from 74.125.196.103: bytes=32 time=51ms TTL=45
Reply from 74.125.196.103: bytes=32 time=48ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=48ms TTL=45
Reply from 74.125.196.103: bytes=32 time=52ms TTL=45
Reply from 74.125.196.103: bytes=32 time=60ms TTL=45
Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=48ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=57ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=43ms TTL=45
Reply from 74.125.196.103: bytes=32 time=49ms TTL=45
Reply from 74.125.196.103: bytes=32 time=43ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=58ms TTL=45
Reply from 74.125.196.103: bytes=32 time=43ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=44ms TTL=45
Reply from 74.125.196.103: bytes=32 time=44ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=52ms TTL=45
Reply from 74.125.196.103: bytes=32 time=48ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=48ms TTL=45
Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=49ms TTL=45
Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=44ms TTL=45
Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=57ms TTL=45
Reply from 74.125.196.103: bytes=32 time=63ms TTL=45
Reply from 74.125.196.103: bytes=32 time=56ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=48ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=44ms TTL=45
Reply from 74.125.196.103: bytes=32 time=57ms TTL=45
Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=51ms TTL=45
Reply from 74.125.196.103: bytes=32 time=48ms TTL=45
Reply from 74.125.196.103: bytes=32 time=44ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=121ms TTL=45
Reply from 74.125.196.103: bytes=32 time=49ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=58ms TTL=45
Reply from 74.125.196.103: bytes=32 time=113ms TTL=45
Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=53ms TTL=45
Reply from 74.125.196.103: bytes=32 time=50ms TTL=45
Reply from 74.125.196.103: bytes=32 time=48ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=51ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.12
Customer: replied 7 months ago.
Then it starts doing this - Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=50ms TTL=45
Reply from 74.125.196.103: bytes=32 time=48ms TTL=45
Reply from 74.125.196.103: bytes=32 time=48ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=47ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=46ms TTL=45
Reply from 74.125.196.103: bytes=32 time=50ms TTL=45
Reply from 74.125.196.103: bytes=32 time=43ms TTL=45
Reply from 74.125.196.103: bytes=32 time=773ms TTL=45
Reply from 74.125.196.103: bytes=32 time=995ms TTL=45
Reply from 74.125.196.103: bytes=32 time=533ms TTL=45
Reply from 74.125.196.103: bytes=32 time=45ms TTL=45
Reply from 74.125.196.103: bytes=32 time=241ms TTL=45
Reply from 74.125.196.103: bytes=32 time=283ms TTL=45
Reply from 74.125.196.103: bytes=32 time=351ms TTL=45
Reply from 74.125.196.103: bytes=32 time=460ms TTL=45
Reply from 74.125.196.103: bytes=32 time=489ms TTL=45
Reply from 74.125.196.103: bytes=32 time=531ms TTL=45
Reply from 74.125.196.103: bytes=32 time=626ms TTL=45
Reply from 74.125.196.103: bytes=32 time=772ms TTL=45
Reply from 74.125.196.103: bytes=32 time=932ms TTL=45
Reply from 74.125.196.103: bytes=32 time=1302ms TTL=45
Reply from 74.125.196.103: bytes=32 time=1286ms TTL=45
Reply from 74.125.196.103: bytes=32 time=1285ms TTL=45
Reply from 74.125.196.103: bytes=32 time=1222ms TTL=45
Reply from 74.125.196.103: bytes=32 time=1287ms TTL=45
Reply from 74.125.196.103: bytes=32 time=872ms TTL=45
Reply from 74.125.196.103: bytes=32 time=675ms TTL=45
Reply from 74.125.196.103: bytes=32 time=193ms TTL=45
Reply from 74.125.196.103: bytes=32 time=668ms TTL=45
Reply from 74.125.196.103: bytes=32 time=1512ms TTL=45
Reply from 74.125.196.103: bytes=32 time=1924ms TTL=45
Reply from 74.125.196.103: bytes=32 time=2008ms TTL=45
Reply from 74.125.196.103: bytes=32 time=1955ms TTL=45
Reply from 74.125.196.103: bytes=32 time=1450ms TTL=45
Reply from 74.125.196.103: bytes=32 time=1522ms TTL=45
Reply from 74.125.196.103: bytes=32 time=1299ms TTL=45
Reply from 74.125.196.103: bytes=32 time=136ms TTL=45
Expert:  Kevin Wells replied 7 months ago.
Hi Danny,I would like to see if I can help with this.Do you have DHCP configured elsewhere on the network? Do you have another device providing DHCP?are you able to provide a diagram of your network?regards,Kevin
Customer: replied 7 months ago.
Hey Kevin. I can simplify this by telling you that I test this issue with 1 router with DHCP, one standard modem and one device. If a router (I've tried 3) is between the device and modem, I have issues. If I take the router out of that equation - no issue (direct connect to modem) - Yes, I do have a large network with other switches and routers in switch mode (no dhcp active) - but I'm testing with only 1 router, one modem and one device.
Customer: replied 7 months ago.
My large network looks like this - Modem to router to switchs. (only 1 dhcp is active assigning the other routers in switch mode their IP) - but again, when I test I shut it all down except the modem, 1 router and 1 device. (I've tried various devices to to make sure it wasn't just the device) wireless or wired makes no difference.
Expert:  Kevin Wells replied 7 months ago.
What device are you pinging from? A PC, switch?What is the LAN address of the router?What is the default gateway on the device you are pinging from?
Expert:  Kevin Wells replied 7 months ago.
Can I also ask what is the make and model of the router you are using?
Customer: replied 7 months ago.
Sometimes it's a pc, sometimes it's an ipad, sometimes it's a MacBook. 192.168.1.1 is the LAN IP - (I've tried 3 routers - 2 Linksys and an asus. Same issue - firmware all updated
Customer: replied 7 months ago.
I've thought about wifi interference - so disabled it.. same issue... I'm stumped.. I've tried many things..
Customer: replied 7 months ago.
Each device has a proper IP addy - I've found no ip addy conflicts ..
Customer: replied 7 months ago.
Is it possible for an ISP to set their software to detect routers and reduce the quality of service if they detect one ? I know I'm reaching here, but lol...
Expert:  Kevin Wells replied 7 months ago.
lol, I think they can if they wish, lol, but don't think that is what is happening.can you do a trace to something like 8.8.8.8 and show the output?can I check which port on the router is the modem connected to? I know you are a techy, but just want to double check
Expert:  Kevin Wells replied 7 months ago.
out of curiosity, who is your ISP?
Expert:  Kevin Wells replied 7 months ago.
Does the router have an option to clone PC MAC?
Customer: replied 7 months ago.
Running the trace now - www.tvscable.com is my ISP (local place) - I think they use ATT as their backbone. I'll check the router mac cloning option In a sec
Customer: replied 7 months ago.
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:1 16 ms 2 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 17 ms 14 ms 13 ms dynamic-68-64-127-5.tvscable.com [68.64.127.5]
4 32 ms 30 ms 31 ms 12.126.252.117
5 43 ms 44 ms 42 ms cr1.cgcil.ip.att.net [12.122.133.14]
6 * * * Request timed out.
7 263 ms 87 ms 43 ms 12.123.159.49
8 46 ms 39 ms 68 ms 12.247.252.14
9 33 ms 49 ms 35 ms 209.85.143.152
10 35 ms 32 ms 35 ms 209.85.243.173
11 44 ms 44 ms 45 ms 209.85.247.4
12 54 ms 45 ms 45 ms 72.14.234.81
13 * * * Request timed out.
14 59 ms 44 ms 46 ms google-public-dns-a.google.com [8.8.8.8]
Customer: replied 7 months ago.
Router MAC Address
Use Default Address
Use Computer MAC Address
Use This MAC Address
Customer: replied 7 months ago.
I did try using the "Use my computer mac address" last night when it was really acting up bad - didn't change anything
Customer: replied 7 months ago.
Hm.. when I choose USe Computer Mac.. doesn't look like it sticks.. reverts back to router mac
Expert:  Kevin Wells replied 7 months ago.
Hey Danny,Is there not an option to save the configuration after changing the MAC?
Expert:  Kevin Wells replied 7 months ago.
you may also need to request a new IP on the router after doing this
Expert:  Kevin Wells replied 7 months ago.
can I also check that the WAN on your router is set to use DHCP?
Customer: replied 7 months ago.
Yes, the wan is set to DHCP Internet IP Address
Get Dynamically from ISP - After changing the MAC I hit "apply"
Customer: replied 7 months ago.
This is where I am at at the moment. om 216.58.198.196: bytes=32 time=128ms TTL=49
Reply from 216.58.198.196: bytes=32 time=538ms TTL=49
Reply from 216.58.198.196: bytes=32 time=128ms TTL=49
Reply from 216.58.198.196: bytes=32 time=130ms TTL=49
Reply from 216.58.198.196: bytes=32 time=132ms TTL=49
Reply from 216.58.198.196: bytes=32 time=129ms TTL=49
Reply from 216.58.198.196: bytes=32 time=142ms TTL=49
Reply from 216.58.198.196: bytes=32 time=129ms TTL=49
Reply from 216.58.198.196: bytes=32 time=141ms TTL=49
Reply from 216.58.198.196: bytes=32 time=130ms TTL=49
Reply from 216.58.198.196: bytes=32 time=131ms TTL=49
Reply from 216.58.198.196: bytes=32 time=131ms TTL=49
Reply from 216.58.198.196: bytes=32 time=127ms TTL=49
Reply from 216.58.198.196: bytes=32 time=130ms TTL=49
Reply from 216.58.198.196: bytes=32 time=128ms TTL=49
Reply from 216.58.198.196: bytes=32 time=129ms TTL=49
Reply from 216.58.198.196: bytes=32 time=134ms TTL=49
Reply from 216.58.198.196: bytes=32 time=127ms TTL=49
Reply from 216.58.198.196: bytes=32 time=145ms TTL=49
Reply from 216.58.198.196: bytes=32 time=129ms TTL=49
Reply from 216.58.198.196: bytes=32 time=129ms TTL=49
Expert:  Kevin Wells replied 7 months ago.
that is very slow.Are you using the Linksys router at the moment?What is the model please?
Expert:  Kevin Wells replied 7 months ago.
Out of interest, if you ping 68.64.127.5 is it just as slow.Just trying to work out if it is between the modem and router that there is an issue or further down the line.
Customer: replied 7 months ago.
I don't think it's the router at all. I've tried 3 routers (2 are new). And it always works perfect with a direct modem connection. One day it just started this pattern..I've had this issue for about a year. No matter which router I use, it happens. I have the Netgear r6400 hooked up now with updated FW. Here is that IP ping - C:\Users\shado>ping 68.64.127.5 -tPinging 68.64.127.5 with 32 bytes of data:
Reply from 68.64.127.5: bytes=32 time=860ms TTL=253
Reply from 68.64.127.5: bytes=32 time=236ms TTL=253
Reply from 68.64.127.5: bytes=32 time=454ms TTL=253
Reply from 68.64.127.5: bytes=32 time=16ms TTL=253
Reply from 68.64.127.5: bytes=32 time=16ms TTL=253
Reply from 68.64.127.5: bytes=32 time=15ms TTL=253
Reply from 68.64.127.5: bytes=32 time=17ms TTL=253
Reply from 68.64.127.5: bytes=32 time=28ms TTL=253
Reply from 68.64.127.5: bytes=32 time=16ms TTL=253
Reply from 68.64.127.5: bytes=32 time=25ms TTL=253
Reply from 68.64.127.5: bytes=32 time=15ms TTL=253
Reply from 68.64.127.5: bytes=32 time=130ms TTL=253
Reply from 68.64.127.5: bytes=32 time=15ms TTL=253
Reply from 68.64.127.5: bytes=32 time=27ms TTL=253
Reply from 68.64.127.5: bytes=32 time=19ms TTL=253
Reply from 68.64.127.5: bytes=32 time=22ms TTL=253
Reply from 68.64.127.5: bytes=32 time=303ms TTL=253
Reply from 68.64.127.5: bytes=32 time=21
Customer: replied 7 months ago.
If I remove the router and ping it I bet it's perfect
Customer: replied 7 months ago.
Yup - I made a direct connection to modem from MacBook and the MS to that IP was 13 consistently - hooked router back up and MS from the mackbook was 60-100 etc etc
Customer: replied 7 months ago.
I don't think this is going to lead to a solution man - if not will I get my money back?
Expert:  Kevin Wells replied 7 months ago.
You will get a refund if you don't get a solution.You said that this has been ongoing for a year or more?
Expert:  Kevin Wells replied 7 months ago.
I am happy to continue to troubleshoot if you are?
Customer: replied 7 months ago.
Not really sure what more we can do.. What we know is that any router hooked up causes issues. Not using a router and the ms is great. I've tried 3 different modems and routers using a 1 device hook up test. It's not the modem, it's not my ISP, it's not the devices I've used to test.. (far as I can tell) so the only thing I can think of is some type of interference..
Customer: replied 7 months ago.
Yeah, about a year.
Customer: replied 7 months ago.
eply from 216.58.198.196: bytes=32 time=379ms TTL=49
Reply from 216.58.198.196: bytes=32 time=1069ms TTL=49
Reply from 216.58.198.196: bytes=32 time=2555ms TTL=49
Request timed out.
Reply from 216.58.198.196: bytes=32 time=2447ms TTL=49
Reply from 216.58.198.196: bytes=32 time=2376ms TTL=49
Reply from 216.58.198.196: bytes=32 time=2466ms TTL=49
Reply from 216.58.198.196: bytes=32 time=2429ms TTL=49
Reply from 216.58.198.196: bytes=32 time=2300ms TTL=49
Reply from 216.58.198.196: bytes=32 time=2239ms TTL=49
Reply from 216.58.198.196: bytes=32 time=2168ms TTL=49
Reply from 216.58.198.196: bytes=32 time=2066ms TTL=49
Reply from 216.58.198.196: bytes=32 time=2506ms TTL=49
Reply from 216.58.198.196: bytes=32 time=2415ms TTL=49
Reply from 216.58.198.196: bytes=32 time=2318ms TTL=49
Reply from 216.58.198.196: bytes=32 time=1854ms TTL=49
Reply from 216.58.198.196: bytes=32 time=2313ms TTL=49
Reply from 216.58.198.196: bytes=32 time=1953ms TTL=49
Customer: replied 7 months ago.
That's the current ms - it does seem to be worse at night..
Customer: replied 7 months ago.
If I remove the router, that MS will be 40
Customer: replied 7 months ago.
It's protected with security - so no one is leaching from me. I can account for each device that shows in the router that it is one of mine.
Customer: replied 7 months ago.
I thought about trying a modem/router combo device - but not sure why that should matter..
Expert:  Kevin Wells replied 7 months ago.
You said that you were testing with the Netgear r6400? The next thing that I would try is to try the copy my PC MAC address using the Linksys router, then set the router to get a new IP. This has been known to work with Lynksys routers connected to surfboard modems.
Customer: replied 7 months ago.
The Linksys I have is an old one wr54g with ddrwt on it - I might try this tomorrow - I don't have much hope it will work... and I'd have to set it all up.. I'm not even sure if it has a mac clone feature. What do you mean by "Set rouer to get a new ip"? It picks one up auto from the isp - or are you talking about changing the gateway ip?
Expert:  Kevin Wells replied 7 months ago.
this is from the DD RWT site:MAC Address Clone[edit]MAC Address Cloning EntailmentsThis is a very useful option on your router, which is located in a sub tab under Basic Setup. Many ISP's require you to register your equipment's MAC (or Media Access Controller) address to be able to use their services, as this provides a method of keeping track of billing and/or bandwidth monitoring. The addresses are coded in hexadecimal format, and in this case are limited to the values of A-F and 0-9 restrictively.To enable MAC Cloning, simply click the option under the tab itself. You will have the option of either "Get current PC MAC" or you can input one yourself. Get current PC MAC is primarily used when establishing a service with an ISP that requires it, such as Comcast.
Customer: replied 7 months ago.
I'm running the Linksys mac cloning test now - I'll let you know how it goes
Expert:  Kevin Wells replied 7 months ago.
ok, great, I will wait to hear from you
Customer: replied 7 months ago.
looks like still some spikes.. but lets see if it gets as bad as it was - 1-3kms and timed outs. - This is current eply from 172.217.3.68: bytes=32 time=34ms TTL=54
Reply from 172.217.3.68: bytes=32 time=37ms TTL=54
Reply from 172.217.3.68: bytes=32 time=35ms TTL=54
Reply from 172.217.3.68: bytes=32 time=532ms TTL=54
Reply from 172.217.3.68: bytes=32 time=285ms TTL=54
Reply from 172.217.3.68: bytes=32 time=437ms TTL=54
Reply from 172.217.3.68: bytes=32 time=231ms TTL=54
Reply from 172.217.3.68: bytes=32 time=242ms TTL=54
Reply from 172.217.3.68: bytes=32 time=213ms TTL=54
Reply from 172.217.3.68: bytes=32 time=35ms TTL=54
Reply from 172.217.3.68: bytes=32 time=54ms TTL=54
Reply from 172.217.3.68: bytes=32 time=34ms TTL=54
Customer: replied 7 months ago.
it's mainly 32ms, which is a lower base then before at 50 etc.. but my chief concern is when it hits 700-3k etc and times out. So will see - I'll get back to you later
Expert:  Kevin Wells replied 7 months ago.
ok, so maybe some progress.What are the times if you ping 68.64.127.5 ?
Customer: replied 7 months ago.
Reply from 172.217.3.68: bytes=32 time=546ms TTL=54
Reply from 172.217.3.68: bytes=32 time=290ms TTL=54
Reply from 172.217.3.68: bytes=32 time=613ms TTL=54
Reply from 172.217.3.68: bytes=32 time=662ms TTL=54
Reply from 172.217.3.68: bytes=32 time=225ms TTL=54
Reply from 172.217.3.68: bytes=32 time=736ms TTL=54
Reply from 172.217.3.68: bytes=32 time=651ms TTL=54
Reply from 172.217.3.68: bytes=32 time=572ms TTL=54
Reply from 172.217.3.68: bytes=32 time=910ms TTL=54
Reply from 172.217.3.68: bytes=32 time=848ms TTL=54
Reply from 172.217.3.68: bytes=32 time=268ms TTL=54
Reply from 172.217.3.68: bytes=32 time=847ms TTL=54
Reply from 172.217.3.68: bytes=32 time=837ms TTL=54
Reply from 172.217.3.68: bytes=32 time=317ms TTL=54
Reply from 172.217.3.68: bytes=32 time=851ms TTL=54
Reply from 172.217.3.68: bytes=32 time=853ms TTL=54
Reply from 172.217.3.68: bytes=32 time=324ms TTL=54
Reply from 172.217.3.68: bytes=32 time=33ms TTL=54
Reply from 172.217.3.68: bytes=32 time=812ms TTL=54
Reply from 172.217.3.68: bytes=32 time=853ms TTL=54
Reply from 172.217.3.68: bytes=32 time=311ms TTL=54
Reply from 172.217.3.68: bytes=32 time=49ms TTL=54
Reply from 172.217.3.68: bytes=32 time=32ms TTL=54
Reply from 172.217.3.68: bytes=32 time=826ms TTL=54
Reply from 172.217.3.68: bytes=32 time=909ms TTL=54
Reply from 172.217.3.68: bytes=32 time=484ms TTL=54
Reply from 172.217.3.68: bytes=32 time=216ms TTL=54
Reply from 172.217.3.68: bytes=32 time=857ms TTL=54
Reply from 172.217.3.68: bytes=32 time=42ms TTL=54
Reply from 172.217.3.68: bytes=32 time=94ms TTL=54
Reply from 172.217.3.68: bytes=32 time=124ms TTL=54
Reply from 172.217.3.68: bytes=32 time=840ms TTL=54
Reply from 172.217.3.68: bytes=32 time=563ms TTL=54
Reply from 172.217.3.68: bytes=32 time=35ms TTL=54
Reply from 172.217.3.68: bytes=32 time=36ms TTL=54
Customer: replied 7 months ago.
Doesn't look good..
Customer: replied 7 months ago.
Reply from 68.64.127.5: bytes=32 time=648ms TTL=253
Reply from 68.64.127.5: bytes=32 time=110ms TTL=253
Reply from 68.64.127.5: bytes=32 time=25ms TTL=253
Reply from 68.64.127.5: bytes=32 time=168ms TTL=253
Reply from 68.64.127.5: bytes=32 time=221ms TTL=253
Reply from 68.64.127.5: bytes=32 time=258ms TTL=253
Reply from 68.64.127.5: bytes=32 time=327ms TTL=253
Reply from 68.64.127.5: bytes=32 time=252ms TTL=253
Reply from 68.64.127.5: bytes=32 time=409ms TTL=253
Reply from 68.64.127.5: bytes=32 time=14ms TTL=253
Reply from 68.64.127.5: bytes=32 time=270ms TTL=253
Reply from 68.64.127.5: bytes=32 time=383ms TTL=253
Reply from 68.64.127.5: bytes=32 time=118ms TTL=253
Reply from 68.64.127.5: bytes=32 time=418ms TTL=253
Reply from 68.64.127.5: bytes=32 time=28ms TTL=253
Reply from 68.64.127.5: bytes=32 time=13ms TTL=253
Reply from 68.64.127.5: bytes=32 time=16ms TTL=253
Reply from 68.64.127.5: bytes=32 time=30ms TTL=253
Reply from 68.64.127.5: bytes=32 time=17ms TTL=253
Reply from 68.64.127.5: bytes=32 time=15ms TTL=253
Reply from 68.64.127.5: bytes=32 time=15ms TTL=253
Reply from 68.64.127.5: bytes=32 time=16ms TTL=253
Reply from 68.64.127.5: bytes=32 time=23ms TTL=253
Reply from 68.64.127.5: bytes=32 time=18ms TTL=253
Reply from 68.64.127.5: bytes=32 time=15ms TTL=253
Reply from 68.64.127.5: bytes=32 time=14ms TTL=253
Reply from 68.64.127.5: bytes=32 time=16ms TTL=253
Reply from 68.64.127.5: bytes=32 time=19ms TTL=253
Reply from 68.64.127.5: bytes=32 time=17ms TTL=253
Reply from 68.64.127.5: bytes=32 time=17ms TTL=253
Reply from 68.64.127.5: bytes=32 time=15ms TTL=253
Expert:  Kevin Wells replied 7 months ago.
so the pings are better to the ISP than they were before.Could you reboot the routerthen could you run the ping for a bit longer, and could you let me see the statistics at the end also.I feel like we have made some progress
Customer: replied 7 months ago.
I'm doing a continuous ping. I don't see a difference in the pattern - so I'm predicting it will eventually hit the 1k-2 ping as the day goes on. I did reboot the router and modem after I changed to Pc mac addy. If I just do a 4 ping it will show the ending. This is what that looks like - Pinging www.google.com [172.217.0.100] with 32 bytes of data:
Reply from 172.217.0.100: bytes=32 time=33ms TTL=54
Reply from 172.217.0.100: bytes=32 time=31ms TTL=54
Reply from 172.217.0.100: bytes=32 time=33ms TTL=54
Reply from 172.217.0.100: bytes=32 time=38ms TTL=54Ping statistics for 172.217.0.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 38ms, Average = 33msC:\Users\shado>
Customer: replied 6 months ago.
Reply from 216.58.192.228: bytes=32 time=521ms TTL=53
Reply from 216.58.192.228: bytes=32 time=356ms TTL=53
Reply from 216.58.192.228: bytes=32 time=32ms TTL=53
Reply from 216.58.192.228: bytes=32 time=324ms TTL=53
Reply from 216.58.192.228: bytes=32 time=513ms TTL=53
Reply from 216.58.192.228: bytes=32 time=51ms TTL=53
Reply from 216.58.192.228: bytes=32 time=609ms TTL=53
Reply from 216.58.192.228: bytes=32 time=88ms TTL=53
Reply from 216.58.192.228: bytes=32 time=767ms TTL=53
Reply from 216.58.192.228: bytes=32 time=363ms TTL=53
Reply from 216.58.192.228: bytes=32 time=804ms TTL=53
Reply from 216.58.192.228: bytes=32 time=651ms TTL=53
Reply from 216.58.192.228: bytes=32 time=470ms TTL=53
Reply from 216.58.192.228: bytes=32 time=731ms TTL=53
Reply from 216.58.192.228: bytes=32 time=204ms TTL=53
Reply from 216.58.192.228: bytes=32 time=761ms TTL=53
Reply from 216.58.192.228: bytes=32 time=582ms TTL=53
Reply from 216.58.192.228: bytes=32 time=523ms TTL=53
Reply from 216.58.192.228: bytes=32 time=762ms TTL=53
Reply from 216.58.192.228: bytes=32 time=48ms TTL=53
Reply from 216.58.192.228: bytes=32 time=566ms TTL=53
Reply from 216.58.192.228: bytes=32 time=77ms TTL=53
Reply from 216.58.192.228: bytes=32 time=384ms TTL=53
Reply from 216.58.192.228: bytes=32 time=720ms TTL=53
Reply from 216.58.192.228: bytes=32 time=85ms TTL=53
Reply from 216.58.192.228: bytes=32 time=139ms TTL=53
Reply from 216.58.192.228: bytes=32 time=265ms TTL=53
Reply from 216.58.192.228: bytes=32 time=310ms TTL=53
Reply from 216.58.192.228: bytes=32 time=385ms TTL=53
Reply from 216.58.192.228: bytes=32 time=345ms TTL=53
Reply from 216.58.192.228: bytes=32 time=453ms TTL=53
Reply from 216.58.192.228: bytes=32 time=412ms TTL=53
Reply from 216.58.192.228: bytes=32 time=662ms TTL=53
Reply from 216.58.192.228: bytes=32 time=705ms TTL=53
Reply from 216.58.192.228: bytes=32 time=187ms TTL=53
Reply from 216.58.192.228: bytes=32 time=278ms TTL=53
Reply from 216.58.192.228: bytes=32 time=703ms TTL=53
Reply from 216.58.192.228: bytes=32 time=96ms TTL=53
Reply from 216.58.192.228: bytes=32 time=707ms TTL=53
Reply from 216.58.192.228: bytes=32 time=30ms TTL=53
Reply from 216.58.192.228: bytes=32 time=354ms TTL=53
Reply from 216.58.192.228: bytes=32 time=537ms TTL=53
Reply from 216.58.192.228: bytes=32 time=684ms TTL=53
Reply from 216.58.192.228: bytes=32 time=630ms TTL=53
Reply from 216.58.192.228: bytes=32 time=700ms TTL=53
Reply from 216.58.192.228: bytes=32 time=695ms TTL=53
Reply from 216.58.192.228: bytes=32 time=489ms TTL=53
Reply from 216.58.192.228: bytes=32 time=319ms TTL=53
Reply from 216.58.192.228: bytes=32 time=279ms TTL=53
Reply from 216.58.192.228: bytes=32 time=260ms TTL=53
Reply from 216.58.192.228: bytes=32 time=246ms TTL=53
Reply from 216.58.192.228: bytes=32 time=293ms TTL=53
Customer: replied 6 months ago.
So there is still obviously some issues that happen on and off through the day. When it's good, it's hitting 30ms - but these spikes are still happening. I'm going to keep recording it through out the day ...and see if those spikes get even worse
Customer: replied 6 months ago.
This is what's happening now -reply from 216.58.192.228: bytes=32 time=77ms TTL=53
Reply from 216.58.192.228: bytes=32 time=160ms TTL=53
Reply from 216.58.192.228: bytes=32 time=126ms TTL=53
Reply from 216.58.192.228: bytes=32 time=103ms TTL=53
Reply from 216.58.192.228: bytes=32 time=214ms TTL=53
Reply from 216.58.192.228: bytes=32 time=149ms TTL=53
Reply from 216.58.192.228: bytes=32 time=105ms TTL=53
Reply from 216.58.192.228: bytes=32 time=256ms TTL=53
Reply from 216.58.192.228: bytes=32 time=221ms TTL=53
Reply from 216.58.192.228: bytes=32 time=307ms TTL=53
Reply from 216.58.192.228: bytes=32 time=242ms TTL=53
Reply from 216.58.192.228: bytes=32 time=122ms TTL=53
Reply from 216.58.192.228: bytes=32 time=297ms TTL=53
Reply from 216.58.192.228: bytes=32 time=330ms TTL=53
Reply from 216.58.192.228: bytes=32 time=279ms TTL=53
Reply from 216.58.192.228: bytes=32 time=266ms TTL=53
Reply from 216.58.192.228: bytes=32 time=433ms TTL=53
Reply from 216.58.192.228: bytes=32 time=37ms TTL=53
Reply from 216.58.192.228: bytes=32 time=594ms TTL=53
Reply from 216.58.192.228: bytes=32 time=136ms TTL=53
Reply from 216.58.192.228: bytes=32 time=647ms TTL=53
Reply from 216.58.192.228: bytes=32 time=74ms TTL=53
Reply from 216.58.192.228: bytes=32 time=485ms TTL=53
Reply from 216.58.192.228: bytes=32 time=620ms TTL=53
Reply from 216.58.192.228: bytes=32 time=143ms TTL=53
Reply from 216.58.192.228: bytes=32 time=422ms TTL=53
Reply from 216.58.192.228: bytes=32 time=703ms TTL=53
Reply from 216.58.192.228: bytes=32 time=400ms TTL=53
Reply from 216.58.192.228: bytes=32 time=838ms TTL=53
Reply from 216.58.192.228: bytes=32 time=633ms TTL=53
Reply from 216.58.192.228: bytes=32 time=817ms TTL=53
Reply from 216.58.192.228: bytes=32 time=759ms TTL=53
Reply from 216.58.192.228: bytes=32 time=334ms TTL=53
Reply from 216.58.192.228: bytes=32 time=652ms TTL=53
Reply from 216.58.192.228: bytes=32 time=639ms TTL=53
Reply from 216.58.192.228: bytes=32 time=1145ms TTL=53
Reply from 216.58.192.228: bytes=32 time=817ms TTL=53
Reply from 216.58.192.228: bytes=32 time=1010ms TTL=53
Reply from 216.58.192.228: bytes=32 time=1412ms TTL=53
Reply from 216.58.192.228: bytes=32 time=682ms TTL=53
Reply from 216.58.192.228: bytes=32 time=1045ms TTL=53
Reply from 216.58.192.228: bytes=32 time=1310ms TTL=53
Reply from 216.58.192.228: bytes=32 time=874ms TTL=53
Reply from 216.58.192.228: bytes=32 time=659ms TTL=53
Reply from 216.58.192.228: bytes=32 time=1316ms TTL=53
Reply from 216.58.192.228: bytes=32 time=270ms TTL=53
Reply from 216.58.192.228: bytes=32 time=38ms TTL=53
Reply from 216.58.192.228: bytes=32 time=34ms TTL=53
Reply from 216.58.192.228: bytes=32 time=174ms TTL=53
Reply from 216.58.192.228: bytes=32 time=331ms TTL=53
Reply from 216.58.192.228: bytes=32 time=36ms TTL=53
Reply from 216.58.192.228: bytes=32 time=156ms TTL=53
Reply from 216.58.192.228: bytes=32 time=200ms TTL=53
Reply from 216.58.192.228: bytes=32 time=35ms TTL=53
Reply from 216.58.192.228: bytes=32 time=38ms TTL=53
Reply from 216.58.192.228: bytes=32 time=41ms TTL=53
Reply from 216.58.192.228: bytes=32 time=192ms TTL=53
Reply from 216.58.192.228: bytes=32 time=185ms TTL=53
Reply from 216.58.192.228: bytes=32 time=160ms TTL=53
Reply from 216.58.192.228: bytes=32 time=79ms TTL=53
Reply from 216.58.192.228: bytes=32 time=95ms TTL=53
Reply from 216.58.192.228: bytes=32 time=93ms TTL=53
Reply from 216.58.192.228: bytes=32 time=147ms TTL=53
Reply from 216.58.192.228: bytes=32 time=212ms TTL=53
Reply from 216.58.192.228: bytes=32 time=461ms TTL=53
Reply from 216.58.192.228: bytes=32 time=393ms TTL=53
Customer: replied 6 months ago.
9 pm est Reply from 216.58.192.228: bytes=32 time=39ms TTL=53
Reply from 216.58.192.228: bytes=32 time=37ms TTL=53
Reply from 216.58.192.228: bytes=32 time=36ms TTL=53
Reply from 216.58.192.228: bytes=32 time=36ms TTL=53
Reply from 216.58.192.228: bytes=32 time=36ms TTL=53
Reply from 216.58.192.228: bytes=32 time=34ms TTL=53
Reply from 216.58.192.228: bytes=32 time=36ms TTL=53
Reply from 216.58.192.228: bytes=32 time=36ms TTL=53
Reply from 216.58.192.228: bytes=32 time=34ms TTL=53
Reply from 216.58.192.228: bytes=32 time=36ms TTL=53
Reply from 216.58.192.228: bytes=32 time=737ms TTL=53
Reply from 216.58.192.228: bytes=32 time=320ms TTL=53
Reply from 216.58.192.228: bytes=32 time=718ms TTL=53
Reply from 216.58.192.228: bytes=32 time=499ms TTL=53
Reply from 216.58.192.228: bytes=32 time=698ms TTL=53
Reply from 216.58.192.228: bytes=32 time=702ms TTL=53
Reply from 216.58.192.228: bytes=32 time=33ms TTL=53
Reply from 216.58.192.228: bytes=32 time=35ms TTL=53
Reply from 216.58.192.228: bytes=32 time=34ms TTL=53
Reply from 216.58.192.228: bytes=32 time=40ms TTL=53
Reply from 216.58.192.228: bytes=32 time=32ms TTL=53
Reply from 216.58.192.228: bytes=32 time=36ms TTL=53
Reply from 216.58.192.228: bytes=32 time=34ms TTL=53
Reply from 216.58.192.228: bytes=32 time=37ms TTL=53
Reply from 216.58.192.228: bytes=32 time=36ms TTL=53
Reply from 216.58.192.228: bytes=32 time=35ms TTL=53
Reply from 216.58.192.228: bytes=32 time=780ms TTL=53
Reply from 216.58.192.228: bytes=32 time=834ms TTL=53
Reply from 216.58.192.228: bytes=32 time=39ms TTL=53
Reply from 216.58.192.228: bytes=32 time=808ms TTL=53
Reply from 216.58.192.228: bytes=32 time=202ms TTL=53
Reply from 216.58.192.228: bytes=32 time=701ms TTL=53
Reply from 216.58.192.228: bytes=32 time=375ms TTL=53
Reply from 216.58.192.228: bytes=32 time=33ms TTL=53
Reply from 216.58.192.228: bytes=32 time=37ms TTL=53
Reply from 216.58.192.228: bytes=32 time=36ms TTL=53
Reply from 216.58.192.228: bytes=32 time=247ms TTL=53
Reply from 216.58.192.228: bytes=32 time=42ms TTL=53
Reply from 216.58.192.228: bytes=32 time=33ms TTL=53
Reply from 216.58.192.228: bytes=32 time=34ms TTL=53
Reply from 216.58.192.228: bytes=32 time=37ms TTL=53
Reply from 216.58.192.228: bytes=32 time=792ms TTL=53
Reply from 216.58.192.228: bytes=32 time=786ms TTL=53
Reply from 216.58.192.228: bytes=32 time=751ms TTL=53
Reply from 216.58.192.228: bytes=32 time=925ms TTL=53
Reply from 216.58.192.228: bytes=32 time=599ms TTL=53
Reply from 216.58.192.228: bytes=32 time=799ms TTL=53
Reply from 216.58.192.228: bytes=32 time=1001ms TTL=53
Reply from 216.58.192.228: bytes=32 time=965ms TTL=53
Reply from 216.58.192.228: bytes=32 time=438ms TTL=53
Reply from 216.58.192.228: bytes=32 time=852ms TTL=53
Reply from 216.58.192.228: bytes=32 time=854ms TTL=53
Reply from 216.58.192.228: bytes=32 time=181ms TTL=53
Reply from 216.58.192.228: bytes=32 time=348ms TTL=53
Reply from 216.58.192.228: bytes=32 time=293ms TTL=53
Reply from 216.58.192.228: bytes=32 time=344ms TTL=53
Reply from 216.58.192.228: bytes=32 time=652ms TTL=53
Reply from 216.58.192.228: bytes=32 time=352ms TTL=53
Reply from 216.58.192.228: bytes=32 time=352ms TTL=53
Reply from 216.58.192.228: bytes=32 time=250ms TTL=53
Reply from 216.58.192.228: bytes=32 time=35ms TTL=53
Reply from 216.58.192.228: bytes=32 time=35ms TTL=53
Reply from 216.58.192.228: bytes=32 time=716ms TTL=53
Reply from 216.58.192.228: bytes=32 time=956ms TTL=53
Reply from 216.58.192.228: bytes=32 time=136ms TTL=53
Reply from 216.58.192.228: bytes=32 time=702ms TTL=53
Reply from 216.58.192.228: bytes=32 time=342ms TTL=53
Reply from 216.58.192.228: bytes=32 time=700ms TTL=53
Reply from 216.58.192.228: bytes=32 time=513ms TTL=53
Reply from 216.58.192.228: bytes=32 time=34ms TTL=53
Reply from 216.58.192.228: bytes=32 time=37ms TTL=53
Reply from 216.58.192.228: bytes=32 time=36ms TTL=53
Reply from 216.58.192.228: bytes=32 time=35ms TTL=53
Reply from 216.58.192.228: bytes=32 time=465ms TTL=53
Reply from 216.58.192.228: bytes=32 time=521ms TTL=53
Expert:  Kevin Wells replied 6 months ago.
Hi Danny,When I ping that address i get this:64 bytes from 216.58.192.228: icmp_seq=17 ttl=53 time=113.573 ms64 bytes from 216.58.192.228: icmp_seq=18 ttl=53 time=114.184 ms64 bytes from 216.58.192.228: icmp_seq=19 ttl=53 time=116.924 ms64 bytes from 216.58.192.228: icmp_seq=20 ttl=53 time=117.688 ms64 bytes from 216.58.192.228: icmp_seq=21 ttl=53 time=119.847 ms64 bytes from 216.58.192.228: icmp_seq=22 ttl=53 time=115.377 ms64 bytes from 216.58.192.228: icmp_seq=23 ttl=53 time=116.335 ms64 bytes from 216.58.192.228: icmp_seq=24 ttl=53 time=117.000 ms64 bytes from 216.58.192.228: icmp_seq=25 ttl=53 time=116.172 ms64 bytes from 216.58.192.228: icmp_seq=26 ttl=53 time=117.361 ms64 bytes from 216.58.192.228: icmp_seq=27 ttl=53 time=116.564 msRequest timeout for icmp_seq 2864 bytes from 216.58.192.228: icmp_seq=29 ttl=53 time=116.961 ms64 bytes from 216.58.192.228: icmp_seq=30 ttl=53 time=117.089 ms64 bytes from 216.58.192.228: icmp_seq=31 ttl=53 time=131.301 ms64 bytes from 216.58.192.228: icmp_seq=32 ttl=53 time=118.687 ms64 bytes from 216.58.192.228: icmp_seq=33 ttl=53 time=117.238 ms64 bytes from 216.58.192.228: icmp_seq=34 ttl=53 time=116.690 ms64 bytes from 216.58.192.228: icmp_seq=35 ttl=53 time=116.405 ms64 bytes from 216.58.192.228: icmp_seq=36 ttl=53 time=118.824 ms64 bytes from 216.58.192.228: icmp_seq=37 ttl=53 time=117.306 ms64 bytes from 216.58.192.228: icmp_seq=38 ttl=53 time=115.655 ms64 bytes from 216.58.192.228: icmp_seq=39 ttl=53 time=116.021 ms
Expert:  Kevin Wells replied 6 months ago.
I got one drop out.Could you do the ping to an address close to your ISP?If I ping 12.247.252.14I get:64 bytes from 12.247.252.14: icmp_seq=0 ttl=58 time=115.711 ms64 bytes from 12.247.252.14: icmp_seq=1 ttl=58 time=116.164 ms64 bytes from 12.247.252.14: icmp_seq=2 ttl=58 time=117.852 ms64 bytes from 12.247.252.14: icmp_seq=3 ttl=58 time=111.671 ms64 bytes from 12.247.252.14: icmp_seq=4 ttl=58 time=116.592 ms64 bytes from 12.247.252.14: icmp_seq=5 ttl=58 time=123.297 ms64 bytes from 12.247.252.14: icmp_seq=6 ttl=58 time=142.248 ms64 bytes from 12.247.252.14: icmp_seq=7 ttl=58 time=112.171 ms64 bytes from 12.247.252.14: icmp_seq=8 ttl=58 time=111.730 ms64 bytes from 12.247.252.14: icmp_seq=9 ttl=58 time=113.792 ms64 bytes from 12.247.252.14: icmp_seq=10 ttl=58 time=122.814 msRequest timeout for icmp_seq 1164 bytes from 12.247.252.14: icmp_seq=12 ttl=58 time=114.341 ms64 bytes from 12.247.252.14: icmp_seq=13 ttl=58 time=113.263 ms64 bytes from 12.247.252.14: icmp_seq=14 ttl=58 time=114.450 ms64 bytes from 12.247.252.14: icmp_seq=15 ttl=58 time=112.562 ms64 bytes from 12.247.252.14: icmp_seq=16 ttl=58 time=110.930 ms64 bytes from 12.247.252.14: icmp_seq=17 ttl=58 time=111.005 ms64 bytes from 12.247.252.14: icmp_seq=18 ttl=58 time=110.197 ms64 bytes from 12.247.252.14: icmp_seq=19 ttl=58 time=114.734 ms64 bytes from 12.247.252.14: icmp_seq=20 ttl=58 time=110.884 ms64 bytes from 12.247.252.14: icmp_seq=21 ttl=58 time=114.293 ms64 bytes from 12.247.252.14: icmp_seq=22 ttl=58 time=115.228 ms64 bytes from 12.247.252.14: icmp_seq=23 ttl=58 time=113.673 ms64 bytes from 12.247.252.14: icmp_seq=24 ttl=58 time=114.692 ms^C--- 12.247.252.14 ping statistics ---25 packets transmitted, 24 packets received, 4.0% packet lossround-trip min/avg/max/stddev = 110.197/115.596/142.248/6.430 ms
Expert:  Kevin Wells replied 6 months ago.
Have you spoken with your ISP about this?If so, what has their feedback been?
Customer: replied 6 months ago.
Since the issue is not present with a direct modem connection - bypassing router I don't see how I could be an issue on their end. And that of course is what thy confirm to me. IF I was getting this issue wth a direct connection to the modem - then it would be more likely. I suffer no high ping or time outs with a direct connection.
Customer: replied 6 months ago.
These issues are only present wth a router included.
Expert:  Kevin Wells replied 6 months ago.
I get what you are saying.I mean have you given them the scenario? Have they come across it before?
Expert:  Kevin Wells replied 6 months ago.
which firmware is your dd-wrt? In DD-WRT, in the NAT/QoS tab, QoS, what are the default bandwidth levels?
Customer: replied 6 months ago.
Yeah, they came out - but sadly I think I know more then they do.. They are a small local company and tend to blame everything on the customer. So if they can ping their modem and it's good and a direct connection to a device yields no issues - they don't care. lol.. QoS is not turned on. I think it's some type of interference hitting my routers - but not sure what it is.. Since it doesn't matter which of the 3 I use - Linksys, Netgear (new) or Asus (New) - I don't think it's bad routers or wrongly configured routers. Something seems like it's overloading them.. and I have no clue if an ISP can detect a router and set something so that if one is attached it causes this to discurage using them for some bandwidth issues they are having because they are overloading their system... (I know that's a stretch - but I'm out of ideas)
Customer: replied 6 months ago.
I think I'm going to take all three routers to a friends house who has the same ISP 3 houses up from me and test them there - I have no doubt they will alll work just fine.. but at least I can confirm a few things doing that
Customer: replied 6 months ago.
The only other I might try after is an all in one router/modem combo and see if that makes any difference and just use switches with it.
Customer: replied 6 months ago.
But for now, My issue has not been resolved even though you clearly tried.. so I can't say I'm "satisfied" - and I have no idea how long these tickets can be left open. It will be a few days before I can test my routers at his house...
Expert:  Kevin Wells replied 6 months ago.
Yes, I think it would be a good idea to try a router/modem combolet me know how you get on.
Customer: replied 6 months ago.
Since the issue is not fixed will i be refunded?