>From: Paul Howarth <paul@xxxxxxxxxxxx>
>Reply-To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
>To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
>Subject: Re: Network card failing (FC3)
>Date: Thu, 11 Aug 2005 08:51:58 +0100
>
>On Thu, 2005-08-11 at 00:33 -0700, Daniel Vogel wrote:
> >
> >
> > >From: Paul Howarth <paul@xxxxxxxxxxxx>
> > >Reply-To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
> > >To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
> > >Subject: Re: Network card failing (FC3)
> > >Date: Thu, 11 Aug 2005 07:34:39 +0100
> > >
> > >On Wed, 2005-08-10 at 22:16 -0700, Daniel Vogel wrote:
> > > >
2.6.11-1.35_FC3smp
> > > >
> > > > After a long installation, we set up a server on wich we installed
> > a
> > > > sw; one of the netword card starts getting disabled by it self.
> > > >
> > > > We think that it may be because the dhcpd.conf may be causing
> > that,
> > > > but even turning service off it still doesn't work.
> > > >
> > > > We tryed the card outside and it works, so isn't a hardware
> > failure,
> > > > and each time we set up the configuration for it, it only survive
> > a
> > > > few seconds and keeps failing.
> > > >
> > > > eth1 Link encap:Ethernet HWaddr 00:0D:88:2D:DB:47
> > > > UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
>
> > > RX packets:21293 errors:0 dropped:0 overruns:0 frame:0
> > > > TX packets:1373 errors:0 dropped:0 overruns:0 carrier:0
> > > > collisions:0 txqueuelen:1000
> > > > RX bytes:1750818 (1.6 MiB) TX bytes:196495 (191.8 KiB)
> > > > Interrupt:169 Base address:0x2400
> > > >
> > > >
> > > > ...no ip assigned, even after we did it....
> > > >
> > > > Aug 11 01:16:27 dhcp-mpt dhcpd: receive_packet failed on eth0:
> > Network
> > > > is down
> > > > Aug 11 01:16:27 dhcp-mpt NetworkManager: SWITCH: old device no
> > > > longer good, but no better device was available
> > >
> > >Why are you running NetworkManager on a server? First thing I'd try
> > is
> >
>getting rid of that since it's aimed at laptops, where the network
> > >environment changes from time to time. It may be NetworkManager that
> > is
> > >actually causing problems.
> > >
> > >Paul.
> > >
> > >--
> > >Paul Howarth paul@xxxxxxxxxxxx
> >
> > The machine is supposed to work as an dhcp, with the program that is
> > loaded on it, it doesn't matters the networkmanager then? or it's used
> > by the dhcp? i still have to get ride of it?
>
>dhclient can handle getting an IP address for you.
>
>You don't *have* to get rid of Networkmanager but I suspect it may be
>the cause of the problem you're having; trying to get things working
>without it would seem to be a good way of testing that theory.
>
>Paul.
>
Well, shuting down Networkmanager makes the configuration to get reset, (so be careful to be close to the machine if that's your case), then it got configured using the dhcpd.conf information.
After re-setting the conf on both cards they work properly, so now the system is working fine.
Thanks Paul.
