Comments on: 9 Tips to diagnose remote GNU/Linux server network connectivity issues

By: Server Support

Server Support — Thu, 18 Jun 2009 04:01:49 +0000

I am agree with Chris Dos that Don’t forget that tcptraceroute can also help diagnose if there is a transparent proxy between your and your server.

Ya it helps to diagnose your server error. MTR also play a important role in finding network..

Thanks for such a nice stuff.

By: arti ajans

arti ajans — Fri, 04 Apr 2008 19:23:04 +0000

thanks you much.

By: Andy

Andy — Wed, 16 Jan 2008 03:55:21 +0000

Yeah, this was a nice article to refer to.

By: Vince

Vince — Wed, 12 Sep 2007 17:39:23 +0000

Great article. Can you suggest any other resources? I have a server I’ve setup with Fedora7 and it keeps going offline seemingly randomly. None of the items you mentioned appear to be the issue.

Here are suspicious logs, but I’m not sure what this means:
Sep 12 08:26:40 localhost kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 12 08:26:40 localhost kernel: sky2 eth0: tx timeout
Sep 12 08:26:40 localhost kernel: sky2 eth0: disabling interface
Sep 12 08:26:40 localhost kernel: sky2 eth0: enabling interface
Sep 12 08:26:40 localhost kernel: sky2 eth0: ram buffer 0K
Sep 12 08:26:43 localhost kernel: sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both

By: vikram

vikram — Mon, 03 Sep 2007 11:13:42 +0000

please send me linux networking command

By: Tim Archer

Tim Archer — Tue, 10 Apr 2007 00:11:33 +0000

In case you want some details on how to change the default port for SSH on your server, making it a little more secure, check out the writeup at: http://timarcher.com/?q=node/46

By: Dicas para diagnosticar as configurações de rede em servidores GNU/Linux at Ricardo Martins

Tue, 20 Mar 2007 06:38:10 +0000

[...] apresenta informações e ferramentas para diagnosticar as configurações de rede… [ link ] Powered by Gregarious [...]

By: raj

raj — Tue, 27 Feb 2007 06:03:09 +0000

99% time the cause of network connection problems are environmental and IDC staff, stemming from someone inadvertantly pulling out a network cable.

By: Chris Dos

Chris Dos — Tue, 27 Feb 2007 00:12:33 +0000

Don’t forget that tcptraceroute can also help diagnose if there is a transparent proxy between your and your server. mii-tool doesn’t work with all network cards, ethtool seems to work with everything at this point.

By: Sven Hoexter

Sven Hoexter — Thu, 22 Feb 2007 15:36:47 +0000

When you’re at #5 you might have a serial console to access (ok that’s lokal network debugging then) the system and ask mii-tool for informations. Sometimes that’s a fast option to check if someone pluged off the network cable or the port on the patch panel is dead etc. pp.

By: Joe

Joe — Thu, 22 Feb 2007 10:18:43 +0000

http://www.bitwizard.nl/mtr/

By: mangoo

mangoo — Wed, 21 Feb 2007 23:00:48 +0000

“arping” command is sometimes useful, too (mainly for local problems).

By: gregf

gregf — Tue, 20 Feb 2007 15:13:36 +0000

Great article. Sure this will help a bunch of people. Keep up the great work on the site. Have it in liferea.

By: Sean

Sean — Tue, 20 Feb 2007 13:42:32 +0000

Also check the arp table… Good for finding out if the problem is fw related, layer2, or layer 3.

Sean