Нет соединения по SHH через Putty?

Question

[i_want_to_know_everything]

При соединении через Putty вот такая картина

через WinSCP под теме же данными на тот же порт все ок
встроенный в WinSCP терминал, тоже работает

В чем может быть причина?

Comments

[Сергей Зеленский]

пытаетесь под рутом зайти?

[i_want_to_know_everything]

и под рутом и не под рутом

Answer 1

[automatik]

KeepAlive в Putty включите и тайм-аут в настройках увеличьте. У самого такое же было, пока не включил.

superuser.com/questions/826485/putty-server-unexpe...

Answer 2

[Ivan]

Покажите пожалуйста PuTTY Event Log + sshd_config.

Comments

[i_want_to_know_everything]

Ivan@:
sshd_config - дефолтный

# This is the ssh client system-wide configuration file.  See
# ssh_config(5) for more information.  This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.

# Configuration data is parsed as follows:
#  1. command line options
#  2. user-specific file
#  3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.

# Site-wide defaults for some commonly used options.  For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.

Host *
#   ForwardAgent no
#   ForwardX11 no
#   ForwardX11Trusted yes
#   RhostsRSAAuthentication no
#   RSAAuthentication yes
#   PasswordAuthentication yes
#   HostbasedAuthentication no
#   GSSAPIAuthentication no
#   GSSAPIDelegateCredentials no
#   GSSAPIKeyExchange no
#   GSSAPITrustDNS no
#   BatchMode no
#   CheckHostIP yes
#   AddressFamily any
#   ConnectTimeout 0
#   StrictHostKeyChecking ask
#   IdentityFile ~/.ssh/identity
#   IdentityFile ~/.ssh/id_rsa
#   IdentityFile ~/.ssh/id_dsa
#   Port 22
#   Protocol 2,1
#   Cipher 3des
#   Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
#   MACs hmac-md5,hmac-sha1,[e-mail],hmac-ripemd160
#   EscapeChar ~
#   Tunnel no
#   TunnelDevice any:any
#   PermitLocalCommand no
#   VisualHostKey no
#   ProxyCommand ssh -q -W %h:%p gateway.example.com
#   RekeyLimit 1G 1h
    SendEnv LANG LC_*
    HashKnownHosts yes
    GSSAPIAuthentication yes
    GSSAPIDelegateCredentials no
<code>

А лог для данного соединения даже не создается

[Ivan]

i_want_to_know_everything: egrep -v '^(#|$)' /etc/ssh/sshd_config,

Event Log: "right mouse-click on the PuTTY window title, which will display PuTTY menu. Select ‘Event Log’".

Попробуйте убрать GSSAPI если не нужен "Category -> Connection -> SSH -> Auth -> GSSAPI -> Attempt GSSAPI authentication"

[i_want_to_know_everything]

Ivan: ну такой рецепт для лога у меня не работает,
веду логи так

и для текущего соединения не создается
с конфигом протупил вот

# Package generated configuration file
# See the sshd_config(5) manpage for details

# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes

# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 1024

# Logging
SyslogFacility AUTH
LogLevel INFO

# Authentication:
LoginGraceTime 120
PermitRootLogin yes
StrictModes yes

RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile	%h/.ssh/authorized_keys

# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes

# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no

# Change to no to disable tunnelled clear text passwords
#PasswordAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no

#MaxStartups 10:30:60
#Banner /etc/issue.net

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

Subsystem sftp /usr/lib/openssh/sftp-server

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes

[Ivan]

i_want_to_know_everything: Понятно, попробуйте тогда так: "C:\Program Files (x86)\PuTTY> plink.exe -v user@host" и покажите логи.

[i_want_to_know_everything]

Ivan: Спасибо за участие. Не хочет оно так делать.
Свободно залез туда через тимвювер с американского компа с чистого Putty, хостер godaddy, сервер там же. Вероятно ip мой попадает под какой то там диапазон в блэклисте.

Answer 3

[CityCat4]

Возможно путти предлагает хосту набор шифров, который хостом не поддерживается. Это нечастая ситуация, тут должен быть либо очень старый ssh сервер, либо очень старый putty, но такое возможно. Есть у меня сервак под FreeBSD 9.2-STABLE, который не обновляется и уже никогда не будет обновляться - с заходом на него уже есть некоторые проблемы:

> ssh -l user not-a-server.ru
Unable to negotiate with XXX.XXX.XXX.XXX port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1