lolinus wrote:What's the ping to your router/modem? If the ping to router/modem is low and stable(should be below 10 ms) then It's on their side, could be anything between the cable to your building to a random cable below the street somewere or the router your line is connected to.
start>cmd>ping *routerip* -t
Let it send about 15 before stopping it( ctrl c).
So, I'm told I'm skipping a little less than I was before, but it's possible that the internet was fine during those few moments. I was just testing what you said a second ago before I checked here and I'm a little confused. Here's my latest PingPlotter 10-minute result directly connected to the modem:
Before, I was assuming that first hop (DNSName --------------) was the modem, but I realized that the modem IP was just 192.182.100.1. Pinging that results in a 0ms response.
Code: Select all
Ping statistics for 192.168.100.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
So what is the first hop (69.181.184.1)?
My current IP is 69.181.194.205, so I assume that first hop (owned by Comcast) is the service assigning my IP address. I'm not sure how much the first hop affects the ping of the subsequent hops, so I don't want to go too far down the list for no reason.
Another tech should be coming in the next 2-3 hours and I'll have him take a look at all my results thus far. If this doesn't work, I'm just going to have to yell at someone at customer service until they bump me up to actual IT people instead of the idiots that just try to powercycle the modem every time I call.
[quote="lolinus"]What's the ping to your router/modem? If the ping to router/modem is low and stable(should be below 10 ms) then It's on their side, could be anything between the cable to your building to a random cable below the street somewere or the router your line is connected to.
start>cmd>ping *routerip* -t
Let it send about 15 before stopping it( ctrl c).[/quote]
So, I'm told I'm skipping a little less than I was before, but it's possible that the internet was fine during those few moments. I was just testing what you said a second ago before I checked here and I'm a little confused. Here's my latest PingPlotter 10-minute result directly connected to the modem:
[img]http://i.imgur.com/KRgy6Ay.png[/img]
Before, I was assuming that first hop (DNSName --------------) was the modem, but I realized that the modem IP was just 192.182.100.1. Pinging that results in a 0ms response.
[code]Ping statistics for 192.168.100.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms[/code]
So what is the first hop (69.181.184.1)?
[img]http://i.imgur.com/6bgXSP3.png[/img]
My current IP is 69.181.194.205, so I assume that first hop (owned by Comcast) is the service assigning my IP address. I'm not sure how much the first hop affects the ping of the subsequent hops, so I don't want to go too far down the list for no reason.
Another tech should be coming in the next 2-3 hours and I'll have him take a look at all my results thus far. If this doesn't work, I'm just going to have to yell at someone at customer service until they bump me up to actual IT people instead of the idiots that just try to powercycle the modem every time I call.