4

One of my servers at work does not connect back to us (so I can't SSH into it). I asked the person on the site to do numerous things:

sudo /sbin/service network restart

It comes up with this: enter image description here

I had him check the conf file to make sure the IP address is correctly in there using:

cat /etc/sysconfig/network-scripts/ifcfg-eth0

And it comes up as (has correct IP):

     ip: 192.168.x.x
submask: 255.255.255.0
     dg: 192.168.x.x

Everytime he runs /sbin/ifconfig -a | less, this is what comes up:

enter image description here

Is there any kind of hardware test I can run on the machine CentOS/SL that can check for hardware failures on the NIC? If not that, what other things can I check that may help isolate where the trouble is?

8
  • 2
    If you're saying that the system is supposedly configured with a static IP, then it's not a hardware issue. The first screen shows it trying to use DHCP to acquire an address. The system is misconfigured, it's not using the static address.
    – phemmer
    Oct 9, 2014 at 22:40
  • 3
    Pasting the whole of ifcfg-eth0 would be useful, plus if you could run dmesg | grep eth, and this should confirm the assigned interfaces. Oct 9, 2014 at 23:04
  • @Patrick. Good catch! How did you conclude this. I looked at the first screen shot but could not see anything that can point towards a misconfiguration. You mind providing more details in an answer? :)
    – ryekayo
    Oct 10, 2014 at 14:44
  • 1
    @ryekayo Determining IP information for eth0... means it's trying to use DHCP. Static configuration won't show that. I think you providing an answer to your own question with exactly what was wrong would be more appropriate. No harm in answering your own question :-)
    – phemmer
    Oct 10, 2014 at 14:58
  • Please post code blocks with terminal output instead of images of terminal output. The result is more readable, more compatible with browsers, and less bandwidth-heavy.
    – HalosGhost
    Oct 10, 2014 at 17:24

1 Answer 1

1

The first picture provided Determining IP information for eth0. This generally means it is misconfigured to static. I concurred this when I had the on-site provide a screenshot of the output of cat /etc/sysconfig/network-scripts/ifcfg-eth0 which shows BOOTPROTO is in fact configured to dhcp. Right now, I am having the on-site change the field to static and restart the machine so that the IP address can be correctly set. Thanks for the help.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .