how-to block ads
|
nixen
Rockin' the Boxen
Premium
join:2002-10-04
Alexandria, VA
 ·Cox HSI
| reply to geowil
Re: i agree, CS is usually horrible
said by geowil  :i dunno bout soho. but here is the list of what they do support. » support.cox.com/sdccommon/asp/co···e87bd537for the love of god, dont use the chat service. they lvl 1's on there are like lvl 0's lmao, and the lvl 2's are like lvl 1's. in short LC service sucks, best to stick with the phone. Yeah, those are the actual cable MODEMs - what plugs into the coax cable - if you don't want to get one from Cox. I was looking for a gateway device (router/firewall) to sit between the MODEM that comes with the self-install kit and the switch that the rest of my house plugs into (i.e., my XBox360, my NAS, my printers, my media center, computers). I was a little disappointed that they wouldn't/couldn't furnish me with a list like that. I mean, I can't be the only subscriber with a home network to protect.
--
The trouble with the world is that the stupid are cocksure and the intelligent are full of doubt. -- Bertrand Russell | |
geowil
join:2008-04-20
Laveen, AZ | AH, in other words a router.
any router will work.
i just installed a netgear yesterday to replace my old pos.
as long as the modem is something they support, you can use w/e router you want wireless or otherwise. | |
nixen
Rockin' the Boxen
Premium
join:2002-10-04
Alexandria, VA
·Cox HSI
| said by geowil :AH, in other words a router. any router will work. i just installed a netgear yesterday to replace my old pos. as long as the modem is something they support, you can use w/e router you want wireless or otherwise. Yeah, I just wanted someone to own up to that, somewhere.
Ultimately, what it appeared to come down to was that, having run through the "FastConnect 2.0" software with my laptop, I had confused the upstream DHCP server (guessing, here). Such that, when I put my router on the line, their DHCP server was slow to provision the link.
My routing device was "impatient" (and apparently "leaky"), such that it ended up snaking DHCP information from the interior DHCP server and applying it to the exterior interface. Fortunately, I was consoled in via it's management port and could see this. I was able to hard-down the interior NIC and re-DHCP the exterior NIC. Once it was able to wait long enough for the initial grab, subsequent reboots of the router set everything up correctly (the exterior DHCP was subsequently nearly instantaneous rather than taking the nearly three minutes for the first successful DHCP).
It was fun and their tech support people were of no help. Granted, I could have avoided it all if I'd have used something like a Linksys to begin with. However, I'd been using the firewall system for YEARS with my DSL link and didn't see any reason to just change when, supposedly, "any router would just work".
--
The trouble with the world is that the stupid are cocksure and the intelligent are full of doubt. -- Bertrand Russell | |
|
