Now I cannot ping out at 4.2.2.2 but I can ping out at the ip address. I have checked my eth0 and my eth0:1 ip range and there are no typos or misprints. I need to get this server up very soon...has anyone experienced this before?

I am not sure I understand the problem. You can't ping 4.2.2.2, or in other words, are unable to reach external hosts? What can you ping then?

Hi, sorry for the confusion. This is the situation. I am transferring my server from one location to another. In the other location is a server that I am taking down. I am putting the ip's from the old server onto my new server. The ip's are static. I have gone into /etc/sysconfig/network-scripts/ifcfg-eth0 and made the necessary changes and also into /etc/sysconfig/network-scripts/ifcfg-eth0-range0 Once this was complete I did a services network restart and tried to ping. I am able to ping with a 0%loss when I ping the ip addresses themselves, but when I try to ping out of the server using 4.2.2.2 I get the response "destination host unreachable". This is keeping me from connecting to my network. Any help you can provide would be most appreciated. Thank you!

It sounds like the route is not valid on the new machine.

Does the output of "route" match exactly between the two machines?

I am sorry....I am a moron...the only thing I could find was the default gateway and that would not match I don't think. I did do a route -n and got some numbers and such that made no sense to me. I truly am a newbie though and most of this is just numbers and letters to me right now. The route -n gave me four rows of four colums. The top two rows started off with my ip address and below that was my gateway followed by two rows of zeros. The second column started off with two rows of zeros followed by my ip address and my gateway. I am not sure if this is helpful or not but I can go and write it all down and put it on here if that is necessary. Thanks so much for your help. I am on aim under TacetQui if you would like to get in touch with me. Thank you again for your help!

Not sure where you are pinging that device from or if you are going through a router, but it could be the arp cache on the machine you are pinging from or the router you are going through has not updated it's cache to reflect the new machine..

arp -d 4.2.2.2 to delete the arp entry from a linux box you are pinging from..

C:\>netsh interface ip delete arpcache or if the client is a windows machine

clear arp-cache for your cisco router..


Just a thought