我已经从我的Windows 10主机端口转发到我的Ubuntu Virtual Box客户端，工作时间超过三年，然后在昨天重新启动客户端后突然PUTTY停止连接。
我还没有改变任何设置，它只是停止了工作。我已经调查并尝试了很多我在互联网上找到的建议，但它仍然没有用。以下是详细信息：
在Ubuntu guest上，我已确认sshd守护程序正在运行
$ ps aux | grep sshd
jryan 19096 0.0 0.0 61376 3036 ? Ss 14:15 0:00 /usr/sbin/sshd
在Ubuntu guest上，我可以通过端口22成功SSH到localhost
$ ssh localhost
jryan@localhost's password:
Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-108-generic x86_64)
...
在Ubuntu上，我已经确认sshd正在侦听端口22
netstat -lp --inet
tcp 0 0 localhost:ssh *:* LISTEN
tcp 0 0 10.0.0.18:ssh *:* LISTEN
再次，使用nmap
$ sudo nmap -sS -O localhost/24
PORT STATE SERVICE
22/tcp open ssh
当我从Windows 10主机（使用Putty）ssh时，它只挂起60秒然后我收到错误＆＃34;服务器意外关闭网络连接＆＃34;。然后，我打开了一个Windows BASH会话，从命令行运行ssh：
jryan@JIMSURFACEPRO4:/mnt/c/Windows/System32$ ssh -vv jryan@127.0.0.1 -p 60022
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 127.0.0.1 [127.0.0.1] port 60022.
debug1: Connection established.
debug1: identity file /mnt/c/Users/[user]/Google Drive/[user]/home/jryan/.ssh/id_rsa type -1
debug1: identity file /mnt/c/Users/[user]/Google Drive/[user]/home/jryan/.ssh/id_rsa-cert type -1
debug1: identity file /mnt/c/Users/[user]/Google Drive/[user]/home/jryan/.ssh/id_dsa type -1
debug1: identity file /mnt/c/Users/[user]/Google Drive/[user]/home/jryan/.ssh/id_dsa-cert type -1
debug1: identity file /mnt/c/Users/[user]/Google Drive/[user]/home/jryan/.ssh/id_ecdsa type -1
debug1: identity file /mnt/c/Users/[user]/Google Drive/[user]/home/jryan/.ssh/id_ecdsa-cert type -1
debug1: identity file /mnt/c/Users/[user]/Google Drive/[user]/home/jryan/.ssh/id_ed25519 type -1
debug1: identity file /mnt/c/Users/[user]/Google Drive/[user]/home/jryan/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8
ssh_exchange_identification: Connection closed by remote host
我已确认在虚拟机上正确设置了端口转发：
VBoxManage showvminfo
NIC 2: MAC: 080027775E38, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 2 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2 Rule(0): name = ssh, protocol = tcp, host ip = , host port = 60022, guest ip = , guest port = 22
我已确认端口60022已在Windows主机上打开
c:\Program Files\Oracle\VirtualBox>netstat -a
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:22 JimSurfacePro4:0 LISTENING
TCP 0.0.0.0:80 JimSurfacePro4:0 LISTENING
TCP 0.0.0.0:135 JimSurfacePro4:0 LISTENING
TCP 0.0.0.0:443 JimSurfacePro4:0 LISTENING
TCP 0.0.0.0:445 JimSurfacePro4:0 LISTENING
TCP 0.0.0.0:7680 JimSurfacePro4:0 LISTENING
TCP 0.0.0.0:23367 JimSurfacePro4:0 LISTENING
TCP 0.0.0.0:49664 JimSurfacePro4:0 LISTENING
TCP 0.0.0.0:49665 JimSurfacePro4:0 LISTENING
TCP 0.0.0.0:49666 JimSurfacePro4:0 LISTENING
TCP 0.0.0.0:49667 JimSurfacePro4:0 LISTENING
TCP 0.0.0.0:49668 JimSurfacePro4:0 LISTENING
TCP 0.0.0.0:49670 JimSurfacePro4:0 LISTENING
TCP 0.0.0.0:60022 JimSurfacePro4:0 LISTENING
TCP 10.0.0.8:139 JimSurfacePro4:0 LISTENING
我设置了Windows防火墙规则，允许端口60022上的所有TCP连接（入站和出站）
我检查了Ubuntu客户端上的日志。当我尝试连接时，没有任何内容写入/var/logs/auth.log或/var/logs/syslog。
这是来自Ubuntu主机的/etc/ssh/sshd_config：
jryan@medstro-dev-jim:~$ cat /etc/ssh/sshd_config
# 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 127.0.0.1
ListenAddress 10.0.0.18
Protocol 2,1
AllowUsers jryan
# 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:
PasswordAuthentication yes
LoginGraceTime 240
PermitRootLogin without-password
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
ClientAliveInterval 60
ClientAliveCountMax 20
#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
我没有想法。如果你能弄清楚这里发生了什么，请告诉我。
谢谢！
答案 0 :(得分：0)
关闭Windows防火墙并尝试一次。在Windows 10中，我观察到虚拟盒网络中存在一些问题。