Cannot Assign an IP address in my LAN IP range
 

I have a Dell Power edge R200 server, which has CentOS 5 running on it.
and I used 192.168.1.54 to the eth0 , and left the other network card free.
But now I cannot assign 192.168.1.0/24 ip to eth0, but I can assign 10.250.250.250 to eth0 and it works fine.
and also i have assigned 192.168.1.54 to the eth1 of the same server it works fine.

Is that a hardware failure? Or a routing issue?
How can I fix it?
Please help me..


Thanks

Amila.

Neither. Best bet, is you have a DHCP server in your network somewhere that has assigned those addresses to other interfaces.

To prove it, disconnect your eth0 interface, ifconfig it down, then try to assign the ip address you want, ifconfig it up. I suspect you will find the card will accept the address.

I should add some details also,

I checked this after few hours and the problem solved automatically,
but again after few hours the problem is back.

Mar 18 04:09:21 server1 kernel: CIFS VFS: server not responding
Mar 18 04:09:21 server1 kernel: CIFS VFS: No response for cmd 114 mid 7044
Mar 18 04:09:41 server1 kernel: CIFS VFS: Error 0xffffff90 on cifs_get_inode_info in lookup of \archive
Mar 18 04:11:08 server1 kernel: CIFS VFS: Error 0xffffff90 on cifs_get_inode_info in lookup of \archive
Mar 18 09:35:49 server1 avahi-daemon[2688]: Withdrawing address record for 192.168.1.54 on eth1.
Mar 18 09:35:49 server1 avahi-daemon[2688]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.1.54.
Mar 18 09:35:49 server1 avahi-daemon[2688]: iface.c: interface_mdns_mcast_join() called but no local address available.
Mar 18 09:35:49 server1 avahi-daemon[2688]: Interface eth1.IPv4 no longer relevant for mDNS.
Mar 18 09:35:49 server1 avahi-daemon[2688]: Withdrawing address record for fe80::221:9bff:fefa:dc9b on eth1.
Mar 18 09:35:49 server1 avahi-daemon[2688]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::221:9bff:fefa:dc9b.
Mar 18 09:35:49 server1 avahi-daemon[2688]: iface.c: interface_mdns_mcast_join() called but no local address available.
Mar 18 09:35:49 server1 avahi-daemon[2688]: Interface eth1.IPv6 no longer relevant for mDNS.
Mar 18 09:35:50 server1 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Mar 18 09:35:52 server1 kernel: tg3: eth1: Link is up at 100 Mbps, full duplex.
Mar 18 09:35:52 server1 kernel: tg3: eth1: Flow control is off for TX and off for RX.
Mar 18 09:35:52 server1 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Mar 18 09:35:53 server1 avahi-daemon[2688]: New relevant interface eth1.IPv6 for mDNS.
Mar 18 09:35:53 server1 avahi-daemon[2688]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::221:9bff:fefa:dc9b.
Mar 18 09:35:53 server1 avahi-daemon[2688]: Registering new address record for fe80::221:9bff:fefa:dc9b on eth1.
Mar 18 09:35:54 server1 avahi-daemon[2688]: New relevant interface eth1.IPv4 for mDNS.
Mar 18 09:35:54 server1 avahi-daemon[2688]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.1.54.
Mar 18 09:35:54 server1 avahi-daemon[2688]: Registering new address record for 192.168.1.54 on eth1.

You could always disable avahi to see if it is causing your issue.. it's not a necessary service.

To disable avahi, edit the file /etc/default/ avahi-daemon as root:

Change the line: AVAHI_DAEMON_START = 1
to: AVAHI_DAEMON_START = 0

Reboot your system and the service should not start.

Sorry for the delay.
I wasn't at my work place. Thank you for the help.

amilauduwerella,

192.168.1.0/24 is not a valid IP address to assign to any host. Its a network address
You normally do not assign 192.168.1.255/24 either, as most people expect that to be the broadcast address on the 192.168.1.0/24 subnet.

hrm I assumed he was assigning an ip address in that range..
I didn't look at it as though he was actually assigning the network address to the interface. interesting..

So amilauduwerella, is the issue now resolved ?

Yes its working Fine Now.
 

Thank you so much for helping.