[NCLUG] dhcp and @home

[Prescott Oelke]

 When they installed the @Home service at my place I had win2k on my box and
it wouldn't pick up DHCP either. The guy got tired of messing with it and
set it up with the static IP. I have used Win98 and BeOS with DHCP with no
problems. I had been using SuSE 6.4 with the static IP, because I couldn't
get DHCP working. When I did a clean install of SuSE 7.1 it picked up the
DHCP and worked right off. I think that the hostname is what screws up the
Linux DHCP. @Home wants to assign the computer the IP and Hostname
automatically. Linux (and Windows 2k/NT) just want to recieve the IP while
keeping their own hostname. Anyway they have never changed my IP so I
usually use it static just to cut down the boot time.

Prescott


On Fri, 16 Mar 2001 09:39:28 -0700 (MST), nclug at nclug.org wrote:

>  
>   Any of you @home cable modem users have any issues with getting DHCP to
>  work? I got it installed yesterday and could never even get a reply from
>  my dhcp requests, although I could see plenty of broadcasts on the
network
>  from stations other than myself. I'm connecting a machine directly to the
>  modem over cat-5. Their tech support wasn't very useful as they tried
>  updating their dhcp database 3 times then gave up and said I couldn't
talk
>  to tier 2 support anymore because I only had the basic installation. :-P
>  
>   I did get it working with the static IP and hopefully I can convince
them
>  to let me keep it but they confirmed again to me that they are going to
try
>  to take them all away and make everyone use dhcp where possible.
>  
>  -- 
>     Mike Loseke    | If at first you don't succeed,
>   mike at verinet.com | increase the amperage.
>  _______________________________________________
>  NCLUG mailing list
>  NCLUG at nclug.org
>  http://www.nclug.org/mailman/listinfo/nclug





_______________________________________________________
Send a cool gift with your E-Card
http://www.bluemountain.com/giftcenter/