[lug] Qwest Basic service w/ single static IP

[Collins Richey]

On 9/17/05, D. Stimits <stimits at comcast.net> wrote:
> Lee Woodworth wrote:
> > Collins Richey wrote:
> >
> >> On 9/16/05, Lee Woodworth <blug-mail at duboulder.com> wrote:
> >>
> >>
> >>> Our experience has been that qwest DSL and comcast cable service at
> >>> client
> >>> sites will routinely go out and require a power cycle on the modem.
> >>
> >>
> >>
> >> I must live in La-La land (SE Aurora). I've used Comcast (<--ATT
> >> <-- at home) for more years than I can remember, and I can count on the
> >> fingers of one hand (without using all the fingers) the number of
> >> outages requiring a modem reset in that period of time. Comcast, in my
> >> experience, is like the Everready Bunny. What's the possibility of
> >> flaky modems?
> >
> > Possible. But 4 different brands: Cisco, Actiontec, Dlink, Linksys.
> > 8+ different locations: Boulder (2), Louisville, Eldorado Springs,
> > Boulder Heights, Downtown Denver, Ken Caryl (2), Longmont. I have
> > read that the lockups might be related to line/cable quality.
> 
> When comcast bought out the AT&T lines, the lines were fairly new in
> parts of the area, but good quality...rated to 600 MHz. Comcast, in its
> wisdom, decided to use 1000 MHz instead of the 600 it originally
> operated at, and not upgrade equipment. Things like connectors suddenly
> had huge dB losses, and every time temperature or humidity changed too
> much, it got bad fast. By now there have been so many service calls that
> it runs pretty much flawlessly, so all is good again. It no longer burps
> each time weather changes or when noise sources light up.
> 

Interesting. I must be lucky, and, of course, I've still got the
original lower speed setup.


-- 
Collins Richey
      Debugging is twice as hard as writing the code ... If you write 
      the code as cleverly as possible, you are, by definition, not 
      smart enough to debug it.
             -Brian Kernighan