[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: DHCP will not grab ip.

On Wed, Oct 8, 2008 at 2:20 PM, Laura Speck <girlstar gmail com> wrote:
> Hey all,
> I am having a problem with a brand new install of Fedora 9. This
> machine has two nic's, eth0 and eth1. They are both . We currently
> have eth0 plugged into a router, had eth1 plugged in earlier to try it
> as well but we have this problem on both nics.
> Basically, on install we specified that both nics were to be dhcp, and
> to come up on boot. But neither of them get an ip on boot. I know that
> it's not a problem with the cable, as we plugged it into a different
> machine and it works fine. I don't think it's a problem with the nics
> as I can't see both of them being toast on a new machine.
> ifconfig eth0 up does nothing. I've gotten someone local to the server
> to try dhclient eth0 and then tail /var/log/messages. We see
> DHCPREQUEST, a bunch of DHCPDISCOVER lines and then end with a "No
> DHCPOFFERS received" message. ifconfig never shows either interface as
> having an "inet ..." line, but they get an "inet6 ..." line. I know
> it's not a problem with the dhcp server because it's our isp's, and
> our other machines can grab an ip fine.
> I've shut off Networkmanager (service NetworkManager stop) and started
> the network (service network start).
> service network start outputs:
> Bringing up loopback interface [OK]
> Bringing up interface eth0:
> Determining IP information for eth0... failed. [FAILED]
> Bringing up interface eth0:
> Determining IP information for eth1... failed. No link available.
> Check cable. [FAILED]
> Our /etc/sysconfig/network-scripts/ifcfg-eth0 looks like...
> DEVICE=eth0
> ONBOOT=yes
> Any tips would be greatly appreciated. Thanks in advance!
> Laura
> --
> fedora-list mailing list
> fedora-list redhat com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Hi Laura Speck!

I notice quite a few e-mails about this but I did not see that the
problem was solved.  If I missed it please forgive me all.

As a temporary measure you may be able to get by with another older slower card.

If it were me I would:

1. Determine that the driver for the card is correct and working.
Time to Google the brand and model number of the card along with (at
least at first) "linux driver".  "lsmod" and similar are your friends
along with "#lspci -v -v -x".

2.  Oh, reseat the card and try one at a time.  Try the cards in a
different machine.  You are right that it is unlikely but still
possible that both are bad, another possibility is that EMF
interference which could be specific to the particular cable run and
machine as plugged into a specific source of power is causing the
problem - substitution is the best way to determine that.

Good Hunting!


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]