In comp.sys.raspberry-pi, Jack Fearnley   wrote:
> On Thu, 14 Dec 2017 19:34:07 +0000, Eli the Bearded wrote:
>> I have two suggestions:
>>
>>   1) Use ssh with -v or -v -v -v to get an idea of what ssh thinks is
>>      going on.
> Here is the, rather long, result of 'ssh -v pi@192.168.0.104'
...
> pi@192.168.0.104's password:
> debug1: Authentication succeeded (password).
> Authenticated to 192.168.0.104 ([192.168.0.104]:22).
> debug1: channel 0: new [client-session]
> debug1: Requesting no-more-sessions@openssh.com
> debug1: Entering interactive session.
> debug1: pledge: network
> debug1: Sending environment.
> debug1: Sending env LANG = en_CA.UTF-8
>
> Note that seven lines before the end it accepts and authenticates the
> password. After the last line it freezes and I have to X the terminal
> window.

That tells me the issue is not ssh. The connection is working, and ssh
has started some command (typically your login shell). You can probably
force quit ssh with  where tilde () is the default
escape key, unless reset with -e on command line or EscapeChar in an
ssh conf file. (I regularly reset the EscapeChar to asterisk myself.)

Time to look at number two:

>>   2) The ssh is working, but you have configured something on startup
>>      (eg in .login or .profile) that prevents a shell from ever
>>      answering. Something like 'startx' in your .login, for example.

What's the shell? What's in the home directory, in particular dot files
that your shell will execute? (Also might need to look at the /etc/
versions of those files, like /etc/profile.)

The bit cross-thread about IP addresses in /etc/hosts is worth fixing,
too.

Elijah
------
 is also the escape char for other programs...

--- SoupGate-Win32 v1.05