IP Address Unreachable

S

ssi.inc

Verified User
Joined
Oct 9, 2005
Messages
18
Right, I can not figure this out and was hoping someone has run into this before and would offer some insight.

I have 3 IP addresses.

173.160.195.91
173.160.195.92
173.160.195.93

173.160.195.92 is the Server address that Directadmin is configured with. This IP works just fine. I can ping it, websites resolve, all is well. 91 and 93 are added using the Directadmin IP Management tool. They show up on ifconfig, I can ping them locally, but can not ping them from an external source. .91 and .93 are unreachable outside of the local machine.

This is true with the firewall off.
This is a new install. CentOS 6, and new hardware as of yesterday. I migrated all my users from the old server where .93 was the primary address. The old server is disconnected and off. I've moved everyone off the non-functioning addresses to .92 and it's working, but it sure would be nice if I knew why the other IPs were not working.

Am I missing something simple?

---additional---
After much reading this may be related to the GUI NetworkManager. This was not something I had to deal with on the previous server, so it's just a guess at the moment.
 
Last edited:
Solution:

# service/NetworkManager stop
# chkconfig NetworkManager off
(Obviously, using this method requires direct access to the server.)


Populate network interface information in /etc/sysconfig/network-scripts (NetworkManager will not populate config files like ifcfg-eth0:1, ifcfg-eth0:2)

# service network start
# chkconfig network on

NetworkManager is installed by default on CentOS 6 for those of us who live in the 21st century and use GUI interfaces. Turns out it is less than ideal for dealing with multiple IP addresses on the same NIC. The previous server setup I was using did not have this problem.
 
zEitEr said:
The IPs must be not-routed, check your rotes and ask your DC.
Click to expand...
The problem could also be an arp-cache which needs to be cleared. Either way, contacting the network manager (your datacenter?) is the best way to resolve the problem, which is hopefully resolved by now.

Jeff
 
You must log in or register to reply here.
Back
Top