One thing you might try is to use 'telnet' to hit port 22 and look for the SSH herald. <br><br>This is why I keep 'telnet' around. The client is handy for that stuff. Port 22, port 80, port 25. Sheesh ... how many plain text protocols can we test with it? I honestly love plain text protocols. Wish we had more of them, then cover with SSL when needed. <br>
<br clear="all">-- R; <><<br><br><br><br><br><br><div class="gmail_quote">On Tue, Mar 8, 2011 at 16:48, Steve VanSlyck <span dir="ltr"><<a href="mailto:s.vanslyck@spamcop.net">s.vanslyck@spamcop.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Anyone here willing to spend a few minutes on the phone with me to go over<br>
some of the Kindergarten level parts of setting up SSH?<br>
<br>
I've got the keys generated, the service runing on the server with password<br>
authorization allowed, and port forwarding set up on the router, but<br>
can't yet connect to the server from outside. I have to confirm that my<br>
dynamic Road Runner-assigned IP address hasn't changed, but assuming it<br>
hasn't there must be a step or two that I'm missing.<br>
<br>
The OS on the server is CentOS 5.5. If someone's willing please shoot me an<br>
email backchannel.<br>
<br>
Thanks a million! ;)<br>
_______________________________________________<br>
colug-432 mailing list<br>
<a href="mailto:colug-432@colug.net">colug-432@colug.net</a><br>
<a href="http://lists.colug.net/mailman/listinfo/colug-432" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
</blockquote></div><br>