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>
