On Mon, 2003-07-14 at 19:33, Tim Fournet wrote: > I'm wondering if the problems may be related to the cable modems > themselves. When I experience my problems, rebooting my modem a few > times seems to help, but then so does just waiting, so I haven't been > able to tell if there's a direct correlation yet. My modem is an RCA > that they provided me. Has anyone else tried rebooting their modems, or > received a replacement modem that made their connection better/worse?
Some modems do suck. Sometimes a firmware upgrade helps. Cox has been known to push out firmware upgrades for various brand/models. AS far as known-good reliable CMs, I recommend the Motorola modems. broadbandreports.com is a good source of info/discussion place for this stuff. > > > On Mon, 2003-07-14 at 12:30, will hill wrote: > > Some Cox lines, like mine, are noisy. It comes and goes. When it got > > really bad, I called them. They sent out a repairman with a noise meter. > > He replaced the line in my backyard and that helped some. After the Toledo > > FBI raids, I quit using my cable modem for anything but browsing and email. > > > > I've been told that they push new DHCP addresses every 8 to 24 hours. That > > and port blocking are done to enforce their "no servers" policy. Who > > knows, they might have decided they don't like TS. > > > > > > On 2003.07.13 23:51 Dustin Puryear wrote: > > > I connect over Cox cable to a Win2k TS on a regular basis, as do some > > > others, and I've noticed it can be hard to keep a connection up. Is this > > > pretty standard? Anyone have problems keeping a connection going for a > > > long > > > time on Cox? The server is on Cox, while I'm on DSL. No real problems on > > > my > > > end. > > > > > > > > > > _______________________________________________ > > General mailing list > > [email protected] > > http://brlug.net/mailman/listinfo/general_brlug.net > > > _______________________________________________ > General mailing list > [email protected] > http://brlug.net/mailman/listinfo/general_brlug.net
