So since a bad wind storm in March, and having to have the cable running to the house replaced, I’ve been having issues. I’ve had the cable people out and they claimed to find no signal problems, but replaced the splitter on the house. That didn’t help, as I guessed it wouldn’t.
Now I’m wondering if somebody can help me understand this WinMTR a bit better, so I know what I need to actually say if I call the cable company again. For the record, this is actually the first time I’ve seen any packet loss at the router itself.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 1 | 655 | 654 | 0 | 0 | 15 | 0 |
| 10.114.64.1 - 7 | 516 | 480 | 3 | 9 | 36 | 12 |
| 192.168.12.93 - 8 | 512 | 475 | 6 | 11 | 75 | 8 |
| 10.224.252.217 - 8 | 509 | 471 | 13 | 18 | 41 | 16 |
| lag-133.ear1.Dallas1.Level3. net - 17 | 360 | 302 | 12 | 510 | 3904 | 3900 |
| No response from host - 100 | 132 | 0 | 0 | 0 | 0 | 0 |
| BLIZZARD-EN.ear3.Dallas1.Level3. net - 7 | 516 | 480 | 13 | 19 | 51 | 19 |
| ae1-br01-eqda6.as57976. net - 8 | 512 | 475 | 36 | 41 | 158 | 37 |
| et-0-0-4-br01-eqch2.as57976. net - 9 | 496 | 455 | 38 | 47 | 866 | 38 |
| be1-pe01-eqch2.as57976. net - 8 | 512 | 475 | 34 | 38 | 54 | 39 |
| chi-eqch2-ia-bons-02.as57976. net - 7 | 532 | 500 | 35 | 39 | 59 | 39 |
| 24.105.62.129 - 9 | 493 | 451 | 37 | 39 | 62 | 38 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
It doesn’t appear to be your problem to resolve. There is a line problem between your device interface and the ISP. Granted they might have replaced the cable, but something else is wrong. In fact, the cable replacement eliminates other possible culprits of your situation. The ISP needs to check their internals from your house to the data center.
I will say though, it’s a little odd to see data loss at the local interface level. RECV should be the same as SENT, not 1 less as yours is showing. Also concerning is the WRST result for your localhost of 15. A machine pinging itself should be nowhere near 15. It typically should be <1ms, or 0 (zero). That’s on a healthy system.
problem is between your router and the first hop outside your house. i feel like its more often caused by a modem/router issue than it is the wiring and/or their first hop, but it could be any of that.
do you connect wired or wirelessly?
can you wire directly to the modem and run another winmtr?
Sorry, I should have clarified this is a wired connection.
Hi Liserschel
Describe the home network connection starting at the computer. You mentioned it is Ethernet cable - then describe all devices it connects to and splitters until it leaves the house.
Let’s run a Tracert here see if we can catch the packet loss we are seeing on WinMTR.
eh, WinMTR in the first post IS a traceroute…
They aren’t the same and ISP support folk generally have no idea what a WinMTR is. If we can catch the packet loss on a standard Tracert that will provide proof for the ISP.
The key is to catch it. Tracerts are a moment in time thing.
Hopefully this is all correct, but let me know if not.
Computer - Modem/Router(combination one) - Splitter in room(splits the cable for both modem & cable tv box in one room) - Cable runs out to the outdoor splitter that connects to the main line from the pole.
I know having my modem & TV on a splitter isn’t ideal, but I’ve never had an issue this bad before with that. I do plan on trying to test the modem on its own on a newer line in another room tomorrow if I can.
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 37 ms 9 ms 14 ms 10.114.64.1
3 8 ms 8 ms * 192.168.12.93
4 17 ms 19 ms 16 ms 10.224.252.217
5 * * * Request timed out.
6 18 ms 18 ms 16 ms ae-8-0.ear3.Dallas1.Level3. net [4.69.210.145]
7 17 ms 18 ms 17 ms BLIZZARD-EN.ear3.Dallas1.Level3. net [4.15.45.54]
8 38 ms 38 ms 38 ms ae1-br01-eqda6.as57976. net [137.221.74.33]
9 40 ms 39 ms 39 ms et-0-0-4-br01-eqch2.as57976. net [137.221.65.38]
10 37 ms 37 ms * be1-pe01-eqch2.as57976. net [137.221.69.67]
11 39 ms 48 ms 38 ms chi-eqch2-ia-bons-02.as57976. net [137.221.66.11]
12 39 ms 38 ms 39 ms 24.105.62.129
Trace complete.
We see packet loss on the Tracert on hop 3. That seems to be a private IP number of some sort. On or close to the home network. The * indicates packet loss. Something to show the ISP. I would be interested in your test tomorrow.
Another thing you might try is checking the connection at the splitter. Small wrench or pliers should work. Test with the TV cable disconnected.
3 8 ms 8 ms * 192.168.12.93
Line 3 indicates a problem with your localhost (machine). 192.168.12.93 is a private local address. That would be inside the house. The * represents a timeout. You have a couple of problems 1) your computer is having issues communicating to the gateway (your router). This is most likely at the splitter you mentioned. If possible, connect your router directly to the computer and run the trace again to see if the problem persists. 2) If the problem goes away, replace your splitter if you must use one, but if you can avoid splitting, that’s all the better.
I think you have a problem further up the line as well, as there’s another timeout after a data center or two handled your pathing. That may be a temporary issue and most likely will not be something you see regularly.
My gut instinct tells me something is wrong with your splitter. Good luck. I’ll follow along, but I’ll leave the conversation so as not to confuse you or anyone else any further.
Happy Gaming
So I’m confused, what is even going on with those first 4 hops? It looks like its going through two sets of modems and routers.
It could be. Some ISP’s use combo routers and modems that then are hooked to your router, and they look like that, with 2 sets of private IP ranges. It could also happen inside an apartment or dormitory, or any community that supplies the internet to residences, and then some residents have their
own routers.
That being said, it looks like this is an ISP type of issue, maybe a result of the splitter or the node at the wire.
So I removed the splitter and connected the modem directly, BUT I’m having to use a wireless adapter now thanks to the distance in the room just being a bit too much for my ethernet. I can’t tell how much of this issue is the result of the wireless adapter now though.
I do plan on still trying it with a different cable in another area of the house, but I will have to attach that cable to the splitter outside and unfortunately we have storms today, so this won’t be possible until tomorrow.
I’ll go ahead and leave the most recent tracert done with the splitter & cable tv removed from the mix.
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 2 ms 2 ms 1 ms 192.168.0.1
2 10 ms 9 ms 10 ms 10.114.64.1
3 10 ms 10 ms 10 ms 192.168.12.93
4 * 18 ms 18 ms 10.224.252.217
5 * 2228 ms 2398 ms lag-133.ear1.Dallas1.Level3. net [4.31.141.81]
6 * * * Request timed out.
7 20 ms 20 ms 19 ms BLIZZARD-EN.ear3.Dallas1.Level3. net [4.15.45.54]
8 39 ms 46 ms * ae1-br01-eqda6.as57976. net [137.221.74.33]
9 41 ms 42 ms 40 ms et-0-0-4-br01-eqch2.as57976. net [137.221.65.38]
10 39 ms 39 ms 40 ms be1-pe01-eqch2.as57976. net [137.221.69.67]
11 39 ms 40 ms 41 ms chi-eqch2-ia-bons-02.as57976. net [137.221.66.11]
12 41 ms 42 ms 40 ms 24.105.62.129
Trace complete.
I have wondered about the same thing Yindar asked about in regards to the 4 hops. It’s always looked like that.
I live in a house so no community setup like that, and I also have my own modem/router. It’s a combination modem/router, but it’s not hooked up to another router.
Hi Liserschel
Let’s reset the Router/Modem device to factory defaults. Should be a small button you would press with a pen tip or pin. Press down and hold that button for 30 seconds.
Run another WinMTR afterwards
Just to be sure, doing a factory reset won’t cause me to have to contact the ISP to get the modem reconnected again right?
Heya Liserschel,
Typically the ISP will use a device ID when they allow a device to connect to their network. This data is not reset when conducting a factory reset, so in theory you should not have to contact the ISP after this process. Though if they use some strange alternative method for verifying devices it’s up to them.
It’s typically fairly safe to do these factory resets though. If that doesn’t work I might also suggest contacting the ISP for assistance updating firmware or similar.
Overall it does look like there is a packet loss issue in the winMTR test that starts right at hop 1, the device the computer connects to for the internet (router or modem depending on your setup).