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 4:14 PM, Derek Martin <invalid at pizzashack.org> wrote:

> On Tue, Aug 07, 2012 at 07:10:44PM -0400, dan moylan wrote:
> > > Maybe add the verbose option and post the output to the list.
> >
> > ok, here 'tis:
> >   Executing: program /usr/bin/ssh host 192.168.0.103, user moylan,
> command scp -v -t -- .
> >   OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
> >   debug1: Reading configuration data /etc/ssh/ssh_config
> >   debug1: /etc/ssh/ssh_config line 19: Applying options for *
> >   debug1: Connecting to 192.168.0.103 [192.168.0.103] port 22.
> >   debug1: connect to address 192.168.0.103 port 22: Connection refused
> >   ssh: connect to host 192.168.0.103 port 22: Connection refused
> >   lost connection
>
> Seems as though there's no server running on 192.168.0.103, port 22.
> But you say ssh works?  Perhaps you should repeat this exercise with
> ssh.  Basically scp == ssh, so one would expect them both to work, or
> both to not work.
>
> Is it perhaps that when you ran ssh, it was in the opposite direction?
>
> --
> Derek D. Martin    http://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
> -=-=-=-=-
> This message is posted from an invalid address.  Replying to it will
> result in
> undeliverable mail due to spam prevention.  Sorry for the inconvenience.
>
>
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>
>
I missed the first part of the conversation, but here's a few things you
can check.  Do you have to the server?  If so, check "netstat -lpn | grep
ssh" to see if ssh is running on port 22.  Then try using "tcpdump -i any
port 22" to see if you can see any host trying to connect on port 22.  You
can check iptables to make sure that ssh isn't being blocked.  Check
/etc/hosts.deny to make sure that your IP isn't being blocked by
tcp_wrappers.  On the client, try "nmap -sT serverIP" to see if your client
can see port 22 open.



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