Comments on: Another Miserable Day Using the C&W Internet http://www.chiriquichatter.net/blog/2007/07/31/another-miserable-day-using-the-cw-internet/ "Dream as if you'll live forever, live as if you'll die today." - James Dean Wed, 19 Nov 2008 13:56:13 +0000 http://wordpress.org/?v=2.6.3 By: Don Ray http://www.chiriquichatter.net/blog/2007/07/31/another-miserable-day-using-the-cw-internet/#comment-24767 Don Ray Fri, 03 Aug 2007 14:32:35 +0000 http://www.chiriquichatter.net/blog/2007/07/31/another-miserable-day-using-the-cw-internet/#comment-24767 <p>Hi Henry. My response time has returned. I appreciate the new info though. It may help in the future.</p> By the way Henry, I found the "traceroute" function under my system network tools. Hi Henry. My response time has returned. I appreciate the new info though. It may help in the future.

By the way Henry, I found the “traceroute” function under my system network tools.

]]> By: Henry Smith http://www.chiriquichatter.net/blog/2007/07/31/another-miserable-day-using-the-cw-internet/#comment-24765 Henry Smith Fri, 03 Aug 2007 14:24:30 +0000 http://www.chiriquichatter.net/blog/2007/07/31/another-miserable-day-using-the-cw-internet/#comment-24765 I doubt the problems are caused by missing copper, Don Ray. When they take your copper you lose the internet and telephone. Traceroute and ping are handy tools for finding the bottlenecks in the pipe. Traceroute does not install by default on Ubuntu, so enter "apt-get install traceroute" from the command line. Type "traceroute " and watch the replies. On my system there is a long lag between my router and Cable and Witless' first link. Use ping to test the addresses which take a long time to reply. If you get a good short ping reply with no losses, chances are good that C&W's network is the culprit. If you're experiencing long load times and timeouts, use ping first with the URL and then with the IP address. Ex: "ping yahoo.com" and "ping 66.94.234.13", Response times should be nearly identical. If the first response takes a long time with "ping yahoo.com", but not with the IP address, C&W's DNS server is probably the cause. Of course, knowing where the problem is probably won't help, because C&W's tech staff is mostly folks who couldn't qualify for a job at MacDonalds, but at least it gives you something to rant about. :) Added: Since I wrote the above, I've discovered that some of the bottlenecks can be eliminated by allowing access through the firewall. I allowed the first three IPs, all in Panama, and the delay disappeared on C&Ws first two (10.255.5.5 and 201.227.35.254) but remains on so1-0-0-2488M.ar4.PHX1.gblx.net (67.17.68.26), so that's where MY bottleneck is. Yahoo groups remain a coin-flip for access, but the problem appears to be at Yahoo. Henry I doubt the problems are caused by missing copper, Don Ray. When they take your copper you lose the internet and telephone.

Traceroute and ping are handy tools for finding the bottlenecks in the pipe. Traceroute does not install by default on Ubuntu, so enter “apt-get install traceroute” from the command line. Type “traceroute ” and watch the replies. On my system there is a long lag between my router and Cable and Witless’ first link. Use ping to test the addresses which take a long time to reply. If you get a good short ping reply with no losses, chances are good that C&W’s network is the culprit.

If you’re experiencing long load times and timeouts, use ping first with the URL and then with the IP address. Ex: “ping yahoo.com” and “ping 66.94.234.13″, Response times should be nearly identical. If the first response takes a long time with “ping yahoo.com”, but not with the IP address, C&W’s DNS server is probably the cause. Of course, knowing where the problem is probably won’t help, because C&W’s tech staff is mostly folks who couldn’t qualify for a job at MacDonalds, but at least it gives you something to rant about. :)

Added: Since I wrote the above, I’ve discovered that some of the bottlenecks can be eliminated by allowing access through the firewall. I allowed the first three IPs, all in Panama, and the delay disappeared on C&Ws first two (10.255.5.5 and 201.227.35.254) but remains on so1-0-0-2488M.ar4.PHX1.gblx.net (67.17.68.26), so that’s where MY bottleneck is. Yahoo groups remain a coin-flip for access, but the problem appears to be at Yahoo.

Henry

]]>