<html>
I have the same problem with time warner cable. I purchased 5 dhcp ip's
and<br>
usually can only get 2 to work. The problem seems to be that after a
certain<br>
perioid of time the cable modem refuses to allow more adderss
requests<br>
to be forwarded. I've had success rebooting the modem and
immediately<br>
doing all five of my dhcp requests. Then it will allow them. But if I
need to<br>
connect my laptop from work I have to reboot the modem again or
else<br>
the laptop wont work. I've done sniffer traces on linux and windows
98<br>
and the DHCP requests are going out fine. I've even had to identical
linux<br>
boxes send out the same dhcp requests (different mac's of course)
and<br>
their DHCP server will respond to one but not the other until i reboot to
modem.<br>
Downside to rebooting is that after the cable modem reboots i have to do
a ping<br>
from each machine because if there is no network traffic after a period
of time<br>
the cable modem will ignore even the previous valid ips thus causing
the<br>
dhcp renewal to fail ~12 hours later and Im back to sqaure one.<br>
<br>
It's stupid and of course timewarner had no clue (even their level 3
people--<br>
which is probably their help desk passing the phone around). They
suggest<br>
things like if your using a hub then its a problem because a hub
doesnt<br>
forward DHCP requests fast enough (recidulous) and they tell me they
dont<br>
support hubs and point the problem at it. This of course after i
reporduce<br>
the problem for them plugging directly into the modem.<br>
<br>
People at these cable companies need to pull their heads out of
their<br>
asses and learn how to manage a network infrastructure.<br>
<br>
At 09:54 PM 1/23/01 -0600, you wrote: <br>
<blockquote type=cite cite>This question may or may not have been
answered before. I recently got a cable modem courtesy of AT&T
(mediaone). When I try to connect with my RH 7.0 box i keep getting the
error <b>timed out waiting for a valid DHCP server response. </b>I have
researched this online and have come up with the advice that dhcpcd needs
the -h option with a mysterious hostname i.e Cxxxxxx-a, which the
AT&T helpless desk knows nothing about. I would really like some
help on this before I go insane. Thank you in advance. <br>
<br>
D.J. Callais <br>
djx@mediaone.net <br>
<br>
P.S. My windoze box connects fine. Exact same NIC as the linux box.
</blockquote><br>
<BR>
</html>