Yes, another reason dhclient (pachage dhcp-client-beta) is superior is that it doesn't immediately fork into the background. It stays in the foreground until your IP is gotten (or until a timeout expires) so you can pretty surely know that once it's been run the IP will be set. If you start dhclient in /etc/init.d/network (and update /etc/hosts) your problems with samba will disappear.
Bryan Scaringe wrote: > Just for the record, my dhcpcd is having the same problem, with one > > ethernet card. Kernel 2.2.7, dhcpcd 1.3.16. I have to use dhclient > > (another DHCP client program) to connect to the internet. > > I had this problem under Redhat, too. In fact, it is part of the > > reason I switched. Trying to get redhat to call dhclient the same way > > as it called dhcpcd showed me how poor the Redhat init scripts really > > were. > > Until you can get an answer to the dhcpcd problem, dhclient should work. > > Bryan > > > I have a question cencerning dhcp. Been running debian for about a month > > or so. I am using a cable modem to access the net. When I first installed > > dhcpcd (and now dhcpcd-sv) I only had one ethernet card installed. No > > problems. Now I am using two, and even though they seem to be detected > > correctly, and the modules being loaded, dhcpcd no longer detects my ip > > address, and I cannot access the internet. I've checked my dhcpcd.conf and > > it is set for eth0, which is the card that I have hooked to the cable modem. > > If anyone has any ideas of what I can do to possibly troubleshoot this, I > > would appreciate it. > > I do know that everything is working correctly, because my network is > > functioning fine under Windows. This is one of the last reasons that I even > > have win installed, other than some games, and I definately want to correct > > it. > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- Jens B. Jorgensen [EMAIL PROTECTED]