Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] 'nother question



On Wed, Aug 8, 2012 at 10:07 PM, Tom Metro <tmetro+blu at gmail.com> wrote:

> Matt Shields wrote:
> > On the client, try "nmap -sT serverIP" to see if your client
> > can see port 22 open.
>
> FYI, you can test SSH connectivity more simply like:
>
> % telnet ssh-server 22
> Trying 192.168.0.123...
> Connected to ssh-server.
> Escape character is '^]'.
> SSH-2.0-OpenSSH_...
>
> Then hit the escape character and type 'cl' and enter to exit.
>
> It's a nice simple sanity test that can be ran from just about any client.
>
>  -Tom
>
> --
> Tom Metro
> Venture Logic, Newton, MA, USA
> "Enterprise solutions through open source."
> Professional Profile: http://tmetro.venturelogic.com/
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>

True, there are lots of different ways to test like using netcat (nc
serverip 22).  Just trying to show options.  nmap, tcpdump, netstat are
some good tools for people to know.


Matthew Shields
www.sysadminvalley.com
www.jeeprally.com



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org