On Tue, Jul 5, 2011 at 6:44 PM, bbb10 <[email protected]> wrote:
> However, now that you have helped me with all this technical minutiae > (thank you very much for sticking with me!), I'm still at a loss as to > how to achieve my original, more practical objective, which is to > determine whether the response time caused by Connecting is the fault > of my ISP, Time Warner. This Connecting issue is something new. When > the Time Warner service was originally installed, it was absolutely > first class and I never saw a Connecting problem. However, as I said > at the outset, the service is now not as good as it was (meaning > significantly slower when surfing, although not as bad when just > downloading one large file), and I'm trying to figure out why. My > guess is that when you are downloading one large file, you only have > to connect once, whereas when you serve, you have to connect many > times, but that doesn't tell me who is causing the Connect problem. > Do you have any suggestions on that issue? I also have TimeWarner as my ISP, and don't see that. One thing to remember is that when you have a cable modem, you are on a network segment, sharing a pipe with everyone else on that segment. Cable modem users commonly experience bandwidth degradation when everyone in the neighborhood comes home from work and hops on the Internet at once. See whether the same problem persists during "off hours" (like 2AM.) TWC tries to build out with each building in the metropolitan area being a segment. For reasons not relevant here, I'm the only user in my building, so I don't see those issues. :) You may be in an area where TWC has added customers to your segment. You may have a problem with your cable modem. (I had that, as the old original modem I got when I first got the service finally started to fail. A new one solved the problems.) And you may need TWC to rebuild your configuration on their end. I've had to do that, too, and Customer Support was able to determine I wasn't getting proper bandwidth and recreate my connection to fix it.) In any case, Firebug is not the tool I would use for the job. You need to determine things like ping times to systems you are trying to reach. You also need to insure you don't have a configuration problem on your end, such as a misconfiguration on your router or a problem with your Windows configuration. The first thing I'd do is go tp http://www.dslreports.com, and run their speed tests. I'd also read their FAQs, and spend a bit of time in the Roadrunner forums. I'm not offhand sure what your underlying problem is, but I doubt Firebug is the way to identify it. ______ Dennis -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
