cox.net FYI

[Digital Wokan]

I made the same mistaken assumption about Windows use.  We aren't doing
any Unix any favors though when we compare Sun Solaris performance to
Windows performance.  Better to just accept that they took on too much
too fast because of the cluster fuck that was @Home's bankruptcy (and
general operation from what I've read).

Lisa Winkler wrote:
> 
> I have been using 2 @home ips.  They stopped working yesterday.  I couldn't reach a DHCP server, so I couldn't get a cox ip.
> 
> I finally got through to tech support (the wait is 1.5 hours) and the guy told me to plug the modem directly into the computer instead of going through the hub.  I know this is on their standard list of things to tell the user to do and explained to the guy that it wouldn't solve anything if the DHCP server was unreachable.  Finally I agreed to do it anyway.  I was connected instantly!
> 
> The t.s. guy explained that the software on their DHCP server (it's probably running windows!) is having problems when the modem reports that there are 2 different MAC addresses behind it.  Apparently when this happens it just refuses to respond to my request.  He says they are working on it, doesn't know when it will be fixed, but until it is you won't be able to have 2 computers with real-world IPs connected because if they are both up at the same time the DHCP server will refuse to assign them ips.  I guess this is my official kick in the ass to try to get NAT working (instead of a bridge as I am currently using).
> 
> Anyway, just a public service in case anyone else is dead in the water but still reading mail!
> 
> Lisa