try looking at the config file of sshd not the client. possible causes
could be that you have no key file and the server is not set to accept
login tunneling which will make your session fail because it will always
expect to find the key. could also be that the keyfile themselves have
the wrong file permissions. sshd is very strict on this.
Deds Castillo
Infiniteinfo
"Reynald I. Ngo" wrote:
>
> At 05:42 PM 1/29/01 +0800, you wrote:
>
> Did that, the log file only says...
>
> Jan 29 17:49:13 chat sshd[15601]: refused connect from x.x.x.x
>
> Verbose mode on ssh client says...
>
> SSH Version OpenSSH_2.3.0p1, protocol versions 1.5/2.0.
> Compiled with SSL (0x0090600f).
> debug: Reading configuration data /etc/ssh/ssh_config
> debug: Applying options for *
> debug: Seeding random number generator
> debug: ssh_connect: getuid 500 geteuid 0 anon 1
> debug: Connecting to me.mydomain.com [x.x.x.x] port 22.
> debug: Connection established.
> ssh_exchange_identification: Connection closed by remote host
> debug: Calling cleanup 0x805cc6c(0x0)
>
> >try adding the line
> >LogLevel DEBUG
> >to your sshd config file. then try reconnecting and inspecting the log
> >file. you would probably see what's wrong there.
>
> ---
> Reynald I. Ngo
> Express Internet, Inc.
> Express Telecoms Co., Inc.
>
> _
> Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
> To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
