On Mon, 2003-07-14 at 19:30, will hill wrote: > 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.
My IP address has never changed via DHCP since the switch from @home over a year ago. Baton Rouge and New Orleans, while having different network management staff, generally operate the same way. When Cox first made the switch from @home, I think they did try to push new DHCP addresses -- ie not just make people renew, but hand out new leases to keep the pool rotating -- and found that this failed miserably. Plus it's disruptive and annoying for customers. There are a whole lot of variables that could explain why Dustin is losing his TS session. The Cox connection is one of many and IMHO not the most likely root cause. You really hate cox.... > After the Toledo FBI raids, I quit using my cable modem for anything > but browsing and email. http://yro.slashdot.org/yro/02/06/27/1329248.shtml?tid=99 What did you have to worry about? The provider wasn't cox for one. And the activity is pretty egregious and very easy for a cable provider to detect. It shows up plain as day on their CMTSs, viewable with a single "show" command or a little Perl and SNMP magic ;). Btw, I'm _not_ saying the police raids were justified. That appears to be over the top to say the least. > > 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
