Comments on: LinkedIn Tech Support http://vanginderachter.be/2007/linkedin-tech-support/?utm_source=rss&utm_medium=rss&utm_campaign=rss van achtere naer vorene Thu, 07 Apr 2011 16:34:11 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Serge van Ginderachter http://vanginderachter.be/2007/linkedin-tech-support/comment-page-1/#comment-550 Serge van Ginderachter Sat, 15 Dec 2007 14:05:47 +0000 http://www.vanginderachter.be/2007/linkedin-tech-support/#comment-550 Point taken, Philip. Alas, the question made me think with enough reason that telnet will be available on the asker's host, whilst netcat not ;-) Point taken, Philip. Alas, the question made me think with enough reason that telnet will be available on the asker’s host, whilst netcat not ;-)

]]> By: Philip Paeps http://vanginderachter.be/2007/linkedin-tech-support/comment-page-1/#comment-549 Philip Paeps Sat, 15 Dec 2007 12:16:17 +0000 http://www.vanginderachter.be/2007/linkedin-tech-support/#comment-549 Waaah! Do Not Use telnet For Network Testing! telnet is for connecting using the TELNET protocol. For testing random TCP or UDP services, please recommend netcat. Yes, telnet will 'often' work (at least for TCP), but I have encountered daemons which get upset about cap negotiation and tear down the connection. When this happens, you'll be barking up the wrong tree for potentially a very long time. No such risk with netcat. As for blogging LinkedIn answers: it doesn't bother me in the least. Quite the contrary. Waaah! Do Not Use telnet For Network Testing!

telnet is for connecting using the TELNET protocol. For testing random TCP or UDP services, please recommend netcat. Yes, telnet will ‘often’ work (at least for TCP), but I have encountered daemons which get upset about cap negotiation and tear down the connection. When this happens, you’ll be barking up the wrong tree for potentially a very long time. No such risk with netcat.

As for blogging LinkedIn answers: it doesn’t bother me in the least. Quite the contrary.

]]>