It has saved me a big deal of time each time I go around deploying it.
Here we go:
1- First check that your interface is enabled:
Type it merly without the -a.
Typically ifconfig will show you enabled interfaces, so that you're sure that your network adapter is enabled at the first place.
2- ping to the loop back address, to make sure there is no internal problem.
If no response restart the interface:
If the problem persists check the network settings.
3- Once you're done with pinging to the loopback address, ping to your own real IP address:
Replace X with your real IP.
4- If there is a problem, it might be physical, most of the time the cable it self is NOT connected.
If your enabled interface is eth0, the prior command is OK for you. The last line of the command will have in the output:
Link detected: yes5- If the link is not detected, please plug the network CABLE! or change it.
6- I wont forget to say, that having a small 4-port switch two network cables and a tester is pretty much handy when you need to isolate the problem, is that from the machine it self, the cables or the switch it self?
All of those techniques had saved me quite a lot of times.
7- Of course checking the gateway settings in /etc/network and /etc/sysconfig/network-scripts/ifcfg-eth0
And checking DNS settings in /etc/resolv.conf will put you in the right track for solving network problems, you can use:
And:
Alongside:
8- Check the firewall, better shut it down to test:
9- Change the network plug if the server has more than one network plug.
10- Check for possible bonding driver problems if network bonding is enabled.
Posts
