On Mon, 2007-12-10 at 16:17 +0000, Jonathan Allen wrote: > On Mon, Dec 10, 2007 at 04:50:13PM +0100, Antonio M asked: > > > > > > # service network start > > > Bringing up loopack interface: [ OK ] > > > Bringing up interface eth0: [FAILED] > > > Error, some other host already uses address 192.168.1.6 > > > > did you try to start the machine disconnected from your network??? > > No, the network was and is still attached to the network. Have you rebooted/power cycled the box? Looking at the network scripts, that message comes from an arping poke and that's pretty definitive. Try changing the IP address in /etc/sysconfig/network-scripts/ifcfg-eth0 to something fairly high (say 192.168.1.200) and see if it'll come up via "service network restart". If it does, then try pinging 192.168.1.6 and see if something really does have that address. It may be that the address was handed out by a DHCP server on your network. If that is indeed the case, find the DHCP server and see what its address pool is. You should choose a fixed IP that's outside that pool or this will happen again. You could resort to having eth0 use DHCP by deleting the "IPADDRESS=" and "NETMASK=" lines in the file above and changing the "BOOTPROTO=" line to "BOOTPROTO=dhcp". The normal network stuff handles DHCP just fine. Example /etc/sysconfig/network-scripts/ifcfg-eth0 for DHCP: DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes TYPE=Ethernet USERCTL=no PEERDNS=yes IPV6INIT=no ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens@xxxxxxxxxxxx - - CDN Systems, Internap, Inc. http://www.internap.com - - - - This message printed using recycled bandwidth - ----------------------------------------------------------------------
