One problem as I understand it is that M$ DHCP servers still expect the NIC to have the obsolescent interim address 0.0.0.0 assigned at initialization prior to the DHCP process commencing. Suse initializes the NIC to an address in the 192.168.x.x range prior to the DHCP process. I've had good luck by assigning the NIC the fixed address 0.0.0.0 by hand (by editing the rc.config directly --YAST won't let you do this); then running dhcpcd eth0 and ifconfig eth0 after bootup. I get a an error message on boot as the card attempts to initialize on the bogus 0.0.0.0, but otherwise DHCP seems to work first time every time. Couldn't get it to work at all before on RoadRunner's pesky NT DHCP servers. Of course, I haven't rebooted in a couple of months. If I had to boot frequently I might find the whole business excessively annoying. Regards, --Kevin On Fri, 7 Jul 2000 15:57:06 +0200, Andre Venter wrote:
Yeah sure - Make a note of the IP address you are handed when you do get it, then just force it - Use yast to assign a static IP address This is a problem I had with a Microsoft DHCP Server - The correct way to go about this is actually to speak to the syadmin and find out which addresses he has assigned to Static Ranges and get him to give you one
Kind Regards
Andre Venter Business Solutions Consultant UUNET SA
Tel: +27 11 235 6500 Fax: +27 11 235 6501
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq