LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   "Error, some other host already uses address XXX.XXX.XXX.XXX" (https://www.linuxquestions.org/questions/linux-networking-3/error-some-other-host-already-uses-address-xxx-xxx-xxx-xxx-187162/)

mwbb_support 05-28-2004 10:23 PM

"Error, some other host already uses address XXX.XXX.XXX.XXX"
 
Hello,

I am building a RedHat 9 box. I have configured the IP information however, on boot I receive the error message "Error, some other host already uses address 192.168.1.2" (Note: Not real address but should do for troubleshooting purposes)

If I log in and do the following commands, the network works fine:

ifconfig eth0 192.168.1.2 netmask 255.255.255.0 up
route add default gw 192.168.1.1

I have checked my dns servers and cannot find the address being used. If I ping the address, I do not get a reply.

Any ideas? Also, what other information would be helpful for troubleshooting purposes?

mwbb_support

mwbb_support 05-29-2004 05:08 PM

Ok, I found the problem.

It seems that our firewall system "grabs" the entire subnet so that rogue machines cannot be either placed on the subnet without authorization or spoof themselves as one of ours.

Apparently, the firewall system detects the new machine then checks its list of authorized machines. Since my machine was not on the list, it essentially gets a DoS attack from the firewall system.

Pretty clever.

Anyway, I tried the machine on another subnet that the firewall system does not guard and it works great.

As to what type of firewall system we are using, I cannot say for security purposes however; I will say that it is open source.

mwbb_support

sfo_sc 04-11-2007 08:24 PM

Quote:

Originally Posted by mwbb_support
Ok, I found the problem.

It seems that our firewall system "grabs" the entire subnet so that rogue machines cannot be either placed on the subnet without authorization or spoof themselves as one of ours.

Apparently, the firewall system detects the new machine then checks its list of authorized machines. Since my machine was not on the list, it essentially gets a DoS attack from the firewall system.

Pretty clever.

Anyway, I tried the machine on another subnet that the firewall system does not guard and it works great.

As to what type of firewall system we are using, I cannot say for security purposes however; I will say that it is open source.

mwbb_support

I am having the exact same problem. Can you please give me some help? I am using 192.168.1.1 as my subnet. Should I change to 10.1.1.1 or something? Thanks. When I use DHCP, I dont have the problem. But I do need a static IP so I can forward the port out. I am just using a linksys wireless router by the way. This problem never happen on Windows.

skprakash1 04-30-2009 07:09 AM

Error, some other host already uses address
 
I am also facing this same problem. But there is no firewall in our network. I checked in the network, none of the devices are using the IP. I changed the IP address and it started working.Previously also the same problem happened. If I log in and do the following commands, the network works fine:

ifconfig eth0 192.168.1.2 netmask 255.255.255.0 up
route add default gw 192.168.1.1

If i restart the network service then i will get the error
Error, some other host already uses address 192.168.1.2. If configure the IP using the above method it will work.
Can anyone please help me to resolve the issue.

aamirhirani 11-15-2010 12:03 AM

Resolved: "Error, some other host already uses address XXX.XXX.XXX.XXX"
 
I was receving this error on my CentOS 5 which I was running through VMWare. I resolved this error by deleting the Network Adapter from VMWare GUI and reinstalled the Network Adapter.

-- Aamir Hirani --

nickwhite 01-20-2014 08:59 AM

Fix for CentOS 6.4
 
For me on CentOS, every time I tried ifup eth0 it would say: "Error, some other host already uses address 192.168.X.X" (even though no other host had that IP address).

The quick & dirty fix was editing /etc/sysconfig/network-scripts/ifcfg-eth0 and commenting out the following lines:

#HWADDR
#UUID
#USERCTL

And setting NM_CONTROLLED=no

After that, the interface came up just fine using ifup eth0.


All times are GMT -5. The time now is 08:41 PM.