[NTLUG:Discuss] Strange iptables problem on CentOS 4.4

Jay Urish j at unixwolf.net
Mon Feb 19 11:44:41 CST 2007


I think he just advocates rm'ing telnetd..

Even cisco routers and switches are becoming ssh enabled.

Rusty Haddock wrote:
> Sally Welch wrote:
>     >It's been years since I've used telnet for a shell login, but I
>     >frequently use telnet to diagnose problems.  If I am having difficulty
>     >ssh'ing to a box, often telnetting to its port 22 will give me a clue.
>     > At least it will tell me if the server is answering that port.  I
>     >also telnet to ports 80, 443, 25, etc to diagnose other problems.
>     >Sending a test email by telnetting to port 25 is a handy email
>     >diagnostic tool which will pinpoint exactly why the MTA isn't
>     >accepting the email.
> 
> 'xactly!  I've been there, done that too.
> 
>     >At work I have been known to telnet to port 3389 to diagnose Windows
>     >terminal server problems, but I steadfastly refuse to actually login
>     >and fix Windows problems...  ;)
> 
> <Gasp!>  :-)
> 
> Good points, Sally!  Thank you!
> 
> 	-Rusty-

-- 
Jay Urish CCNA    Network Engineer
http://jay.unixwolf.net
Home)972.691.0125    Cell)972.965.6229




More information about the Discuss mailing list