Posted: 10/31/2010 2:52:49 AM EDT
So, I went by pingtest.net for the first time just now, and here's my results:
What the hell gives? I'm with ComCrap, running through their modem with my router attached. I am wired to the router with some CAT5e, so I wouldn't think it's that. Is there a problem with my computer, my connection, their software, or something else entirely? |
|
Quoted: So, I went by pingtest.net for the first time just now, and here's my results: http://www.pingtest.net/result/27116131.png What the hell gives? I'm with ComCrap, running through their modem with my router attached. I am wired to the router with some CAT5e, so I wouldn't think it's that. Is there a problem with my computer, my connection, their software, or something else entirely? Considering the plethora of information you've given us about the above, I can with confidence tell you that the problem lies somewhere between the computer chair and the computer itself. |
|
Quoted:
Considering the plethora of information you've given us about the above, I can with confidence tell you that the problem lies somewhere between the computer chair and the computer itself. Thanks, smartass. 
Tell me what you need to know, and I'll give it to you. |
|
Quoted:
So, I went by pingtest.net for the first time just now, and here's my results: <a href="http://www.pingtest.net" target="_blank">http://www.pingtest.net/result/27116131.png</a> What the hell gives? I'm with ComCrap, running through their modem with my router attached. I am wired to the router with some CAT5e, so I wouldn't think it's that. Is there a problem with my computer, my connection, their software, or something else entirely? I had to switch to Comcast from Cox after moving. Since I switched, I get various routing issues at random times. I'll end up with some sites working perfectly, while others are unreachable. You might try running a tracert between you and pingtest.net to see if you routing to them dies after a few hops or something. |
|
88% packet loss is bad. The latency is not great, but not nearly as bad (performance wise) as most your packets being dropped. I would first find some other tests to run to rule out pingtest.com being the issue. If you constantly get similar results, then call up Comcast and bitch. They could be having issues they don't even know about yet. Easy test. Open a command prompt (Programs>Acceessories, I think), then type: ping www.google.com Let that run, and then take a screen shot of your results for us to see. ETA: Also pick a different test location. Try 3 or 4 and see if the results are similar. I just tried a couple, and a one test refused to even run. Another had great results. So that app could be a bit buggy. |
|
Quoted:
Easy test. Open a command prompt (Programs>Acceessories, I think), then type: ping www.google.com Let that run, and then take a screen shot of your results for us to see. ETA: Also pick a different test location. Try 3 or 4 and see if the results are similar. I just tried a couple, and a one test refused to even run. Another had great results. So that app could be a bit buggy. 0% loss pinging google.com w/ the command prompt. I tried 5-6 different servers (note the distance in the image I posted). |
|
Quoted: So that app could be a bit buggy. One of their locations gave me a 1% loss and a jitter of 8... Another gave me 0 loss, 0 jitter and a ping of 30ms... Their destination sites blow. Three of them are a couple hops off of any BGP ASN which tells me that momNpop CoLo is probably having a bad day. |
|
Quoted:
Would you happen to be running an adaptive firewall? It would explain the uber high loss rate. What does the same test look like when you plug directly into the comcast modem? Just plugged my computer directly into the router, and rebooted both for a "fresh start"... Now pingtest.net is saying that it's can't even test the packet loss on any of the seven servers I've tried. 
|
|
Quoted: Quoted: Would you happen to be running an adaptive firewall? It would explain the uber high loss rate. What does the same test look like when you plug directly into the comcast modem? Just plugged my computer directly into the router, and rebooted both for a "fresh start"... Now pingtest.net is saying that it's can't even test the packet loss on any of the seven servers I've tried. http://www.pingtest.net/result/27118200.png That's kinda odd... in that they would have needed to get at least a couple packets through for the ping time and jitter. What OS are you running? |
|
Quoted:
Quoted:
Quoted:
Would you happen to be running an adaptive firewall? It would explain the uber high loss rate. What does the same test look like when you plug directly into the comcast modem? Just plugged my computer directly into the router, and rebooted both for a "fresh start"... Now pingtest.net is saying that it's can't even test the packet loss on any of the seven servers I've tried. http://www.pingtest.net/result/27118200.png That's kinda odd... in that they would have needed to get at least a couple packets through for the ping time and jitter. What OS are you running? Vista Home Premium 64bit |
|
Quoted: When it nagged you about "making changes to your system," which button did you click?Quoted: Quoted: Quoted: Would you happen to be running an adaptive firewall? It would explain the uber high loss rate. What does the same test look like when you plug directly into the comcast modem? Just plugged my computer directly into the router, and rebooted both for a "fresh start"... Now pingtest.net is saying that it's can't even test the packet loss on any of the seven servers I've tried. http://www.pingtest.net/result/27118200.png That's kinda odd... in that they would have needed to get at least a couple packets through for the ping time and jitter. What OS are you running? Vista Home Premium 64bit |
|
Quoted:
When it nagged you about "making changes to your system," which button did you click?[/quote]
Vista Home Premium 64bit It didn't nag me at all with Firefox... Then I tried it in Chrome just now, and it nagged, and I said to unblock it, and now I get this: 
W00t, problem solved. Stupid Windows firewall. Thanks, Sub-MOA! |