win7 hosts文件更改后无效，不生效问题

最新推荐文章于 2025-04-18 09:10:18 发布
最新推荐文章于 2025-04-18 09:10:18 发布
阅读量394 收藏
点赞数
CC 4.0 BY-SA版权
原文链接：http://www.cnblogs.com/su-han/p/5481096.html
本文详细阐述了在使用记事本修改hosts文件后，域名解析仍未能生效的问题，并揭示了问题根源在于文件末尾非空行的存在。通过分析，最终解决了这一困扰，确保了域名解析的正常进行。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

通过记事本修改完hosts文件后，域名解析没有生效。

注：可以正常保存修改、服务dnsclient也已经启动

最后发现是hosts文件最后一行不是空行，回车后问题解决

转载于:https://www.cnblogs.com/su-han/p/5481096.html

 win7修改hosts文件总是不生效/无效的解决方法
wangchsh123456的专栏
01-20 3120
win7添加域名可以通过修改如下文件内容： C:\windows\system32\drivers\etc\host ==========================内容示例如下============================== ==========================内容示例结束============================== 若host文件修改后未生效，原因可能是如下几种： 1、文件编码不对 根据微软的相关文档， hosts文件必须是a...
【解决】hosts 修改无效 - 方法整理
LawssssCat的博客
03-13 1382
关注点： 用win自带的 notepad 修改 hosts （保证编码正确） 清理 dns 缓存（好习惯） ipconfig /flushdns 清理浏览器缓存（方法一大堆，推荐一个chrome插件 ） 关掉 DNS 服务（正常来说，是不需要关闭的，实在不行就试下咯） 关掉 代理 （这个很重要，网上其他解决方法均没提到的这点） 成功的标志 只要 ping 到是你想...
windows7下修改hosts文件无效解决办法
weixin_30861459的博客
04-30 145
通常会为了开发方便、或者屏蔽掉一些恶意网站，我们会在hosts(c:\windows\system32\drivers\etc\hosts)文件中进行相应的域名指向，例： 在上图中，我们可以看到，将www.ywec.com指向到了127.0.0.1，在命令行下ping一下该域名，我们发现它已经被指向到了127.0.0.1，有时我们做了如上述所示操作后，发现域名仍然是指向原IP，这是怎么回事呢...
win7修改host没有起作用问题
PariyPeng
08-20 1190
今天在做测试时，发现自己重定向的地址没有得到跳转，也就是在hosts文件里添加了一些域名指向后，发现根本没起作用，发现有说是因为用户权限的问题。 具体操作如下： 1、win7修改host时是否开启权限，在组或用户名下点击编辑，添加everone用户权限 2、这时如果还不行的话，得刷新一下DNS缓存，在命令行模式下输入 ipconfig /flushdns。然后再ping 360iwx
Win7/10系统修改hosts文件后发现设置无效怎么办
gw5201984的博客
03-30 2224
　Hosts文件具体指什么呢？　　Hosts文件是用于本地dns服务的，采用ip 域名 的格式写在一个文本文件当中， Windows系统上一般存放在系统盘的system32目录下， 比如 C:\windows\system32\drivers\etc\， 本地主机一般都被定义为 127.0.0.1 locahost 。根据微软的相关文档， hosts文件必须是ascii编码方式， 如果你存为uni...
windows7下修改hosts文件无效解决办法（hbase连接失败）
wangzyg的专栏
07-23 770
1.该文件保存时未使用ansi编码进行保存，解决办法：更改文件编码为ansi进行保存2.启用了DNS Client服务（该服务为DNS解析的缓存服务）解决办法：将该服务停用；如果该服务为自动启用，请改为手动启用。
Hosts文件修改权限问题终极解决方案
mmoo_python的博客
04-18 510
对于需要频繁管理hosts配置的专业用户，SwitchHosts等工具能显著提升工作效率，值得纳入开发工具箱。在Windows系统维护过程中，Hosts文件修改权限不足是开发者常遇到的棘手问题。作为系统核心配置文件，Hosts文件承担着域名解析重定向的重要功能，但在实际操作中，不少用户会遇到"您没有权限保存此文件"的提示。本文将系统讲解Hosts文件权限问题的成因及解决方案，并提供专业工具优化建议。当系统提示"无法保存Hosts文件"时，本质是Windows安全机制在起作用。一、Hosts文件基础认知。
centos安装elasticsearch修改IP后无法启动解决方法
netsec_steven的博客
11-01 1222
之所以要记录下，因为过程中遇到很多问题，现在终于解决，结果如下图 es最新软件软件包可在官方网站下载：https://www.elastic.co/downloads/elasticsearch 下载完tar zxvf 解压缩 然后进bin目录./elasticsearch 执行，都没有问题。但是这是IP地址后竟然运行不起来，报错如下 the default discovery se...
分布式文件系统FastDFS
企业实战系列集 ●●● https://ximenjianxue.blog.youkuaiyun.com
09-08 7216
概述 FastDFS是一个开源的轻量级分布式文件系统，是我国一款开源的分布式文件系统 由阿里巴巴开发，其真题架构由跟踪服务器（tracker server）、存储服务器（storage server）和客户端（client）三个部分组成，主要解决了海量数据存储问题，特别适合以中小文件（建议范围：4KB < file_size <500MB）为载体的在线服务。 特点： 1>Fast......
VS Code SSH 远程连接时断时续 / 不稳定问题排查
u013669912的博客
12-30 3388
……
修改hosts文件不生效
qq_46433748的博客
09-05 2121
cmd窗口，比如我修改了192.168.1.1 bbb.com，那就运行ping bbb.com，看得到的ip是否是这个。windows刷新dns缓存：ipconfig /flushdns。原因①：浏览器页面有keep-alive长连接，重启浏览器即可。原因②：挂梯子（代理）了，关了。
windows修改hosts文件不生效，的有效解决方法
Web前端工程师
11-11 868
ANSI。
修改hosts 不生效? 三种方法解决
zx1323的博客
10-22 4万+
chrome无痕模式, 让修改立即生效
win7 HOSTS映射后没有生效操作方法
80后大叔爱学习
08-03 5599
1、首先测试下是不是hosts问题 打开hosts： 1、在hosts添加输入127.0.0.1 www.baidu.com 2、打开 www.taobao.com，是不是进不去了 &lt;这里说明 hosts 修改生效了&gt; 3、注释掉刚才hosts修改，# 127.0.0.1 www.baidu.com，再打开 www.baidu.com，很好，正常打开了，这说明hosts是正常的......
配置windows下域名解析及修改hosts文件不起作用的问题
博客
04-11 1万+
一、配置windows下域名解析 文件位置：c:\windows\system32\drivers\etc\hosts windows下修改的文件为： 到命令行(cmd) ping一下，看是否解析 注意：中间的空格建议从上边拷贝下来，使用tab出现ping不通的问题。 二、修改hosts文件不起作用的问题 1、关闭浏览器 2、命令行(cmd)运行:ipconfig /flush...
关于HOSTS设置不生效的解决小方法
热门推荐
上帝De助手
12-19 5万+
HOSTS对于需要设置的人应该都知道为何用，主要就是在本地建立一个域名--ip映射，而不需要再去找上层的DNS服务器去进行解析。直接就能建立链接操作，进行相关信息的发送。而某些情况下我们可能设置了HOSTS后不能生效，这里总结一下工作中遇到问题和解决的方法： 1、双系统的机器： 设置hosts后不生效的原因主要是：设置的hosts不是当前操作系统的hosts，比如当前系统装在D盘，而修改hos
windows修改hosts文件不生效！
weixin_45042272的博客
02-04 1737
hosts文件默认ASCII编码，我们编辑器打开正常是UTF-8，所以配置进去的可能某些字符会被修改，需要将编辑器改成ASCII编码格式，再去配置保存就ok！如果试了各种方法还是不生效，试试改一下编码格式。
Windows hosts修改后不生效问题
Wrox_Tang的博客
01-30 4985
在使用Windows时有些特殊原因需要修改hosts，但是修改之后发现无法生效，可依次尝试如下操作：
windows下修改host不生效的解决方法
苏卡达
06-07 4万+
修改hosts的host mapping不生效解决   在windows 环境下，修改hosts，添加新host mapping，如下： 192.168.128. 128   test 执行ping 192.168.128.128 ，可以ping通 但执行ping test，死活都不通   最后才找到方法解决，mark下。   1. 打开本地连接-》Internet protoc
sftp -vvv sftp_dy@localhost debug3: spawning "C:\\Program Files\\OpenSSH\\ssh.exe" "-oForwardX11 no" "-oPermitLocalCommand no" "-oClearAllForwardings yes" -v -v -v "-oForwardAgent no" -l sftp_dy -s -- localhost sftp as subprocess OpenSSH_for_Windows_9.8p2 Win32-OpenSSH-GitHub, LibreSSL 4.0.0 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/config error:2 debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2 debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> 'C:\\Users\\zwx1262540/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> 'C:\\Users\\zwx1262540/.ssh/known_hosts2' debug2: resolving "localhost" port 22 debug3: resolve_host: lookup localhost:22 debug3: channel_clear_timeouts: clearing debug3: ssh_connect_direct: entering debug1: Connecting to localhost [127.0.0.1] port 22. debug1: Connection established. debug1: identity file C:\\Users\\zwx1262540/.ssh/id_rsa type 0 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_rsa-cert error:2 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_rsa-cert.pub error:2 debug3: failed to open file:C:/Users/zwx1262540/.ssh/id_rsa-cert error:2 debug1: identity file C:\\Users\\zwx1262540/.ssh/id_rsa-cert type -1 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_ecdsa error:2 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_ecdsa.pub error:2 debug3: failed to open file:C:/Users/zwx1262540/.ssh/id_ecdsa error:2 debug1: identity file C:\\Users\\zwx1262540/.ssh/id_ecdsa type -1 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_ecdsa-cert error:2 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_ecdsa-cert.pub error:2 debug3: failed to open file:C:/Users/zwx1262540/.ssh/id_ecdsa-cert error:2 debug1: identity file C:\\Users\\zwx1262540/.ssh/id_ecdsa-cert type -1 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_ecdsa_sk error:2 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_ecdsa_sk.pub error:2 debug3: failed to open file:C:/Users/zwx1262540/.ssh/id_ecdsa_sk error:2 debug1: identity file C:\\Users\\zwx1262540/.ssh/id_ecdsa_sk type -1 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_ecdsa_sk-cert error:2 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_ecdsa_sk-cert.pub error:2 debug3: failed to open file:C:/Users/zwx1262540/.ssh/id_ecdsa_sk-cert error:2 debug1: identity file C:\\Users\\zwx1262540/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file C:\\Users\\zwx1262540/.ssh/id_ed25519 type 3 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_ed25519-cert error:2 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_ed25519-cert.pub error:2 debug3: failed to open file:C:/Users/zwx1262540/.ssh/id_ed25519-cert error:2 debug1: identity file C:\\Users\\zwx1262540/.ssh/id_ed25519-cert type -1 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_ed25519_sk error:2 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_ed25519_sk.pub error:2 debug3: failed to open file:C:/Users/zwx1262540/.ssh/id_ed25519_sk error:2 debug1: identity file C:\\Users\\zwx1262540/.ssh/id_ed25519_sk type -1 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_ed25519_sk-cert error:2 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_ed25519_sk-cert.pub error:2 debug3: failed to open file:C:/Users/zwx1262540/.ssh/id_ed25519_sk-cert error:2 debug1: identity file C:\\Users\\zwx1262540/.ssh/id_ed25519_sk-cert type -1 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_xmss error:2 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_xmss.pub error:2 debug3: failed to open file:C:/Users/zwx1262540/.ssh/id_xmss error:2 debug1: identity file C:\\Users\\zwx1262540/.ssh/id_xmss type -1 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_xmss-cert error:2 debug3: Failed to open file:C:/Users/zwx1262540/.ssh/id_xmss-cert.pub error:2 debug3: failed to open file:C:/Users/zwx1262540/.ssh/id_xmss-cert error:2 debug1: identity file C:\\Users\\zwx1262540/.ssh/id_xmss-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_for_Windows_9.8 Win32-OpenSSH-GitHub debug1: Remote protocol version 2.0, remote software version OpenSSH_for_Windows_9.8 Win32-OpenSSH-GitHub debug1: compat_banner: match: OpenSSH_for_Windows_9.8 Win32-OpenSSH-GitHub pat OpenSSH* compat 0x04000000 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to localhost:22 as 'sftp_dy' debug3: record_hostkey: found key type ECDSA in file C:\\Users\\zwx1262540/.ssh/known_hosts:2 debug3: load_hostkeys_file: loaded 1 keys from localhost debug3: Failed to open file:C:/Users/zwx1262540/.ssh/known_hosts2 error:2 debug1: load_hostkeys: fopen C:\\Users\\zwx1262540/.ssh/known_hosts2: No such file or directory debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts error:2 debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts: No such file or directory debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts2 error:2 debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts2: No such file or directory debug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp384 debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,kex-strict-c-v00@openssh.com debug2: host key algorithms: ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp384,ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256 debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512 debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512 debug2: compression ctos: none,zlib@openssh.com,zlib debug2: compression stoc: none,zlib@openssh.com,zlib debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug2: peer server KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-s,kex-strict-s-v00@openssh.com debug2: host key algorithms: rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp384,ssh-ed25519 debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512 debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512 debug2: compression ctos: none,zlib@openssh.com debug2: compression stoc: none,zlib@openssh.com debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug3: kex_choose_conf: will use strict KEX ordering debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ecdsa-sha2-nistp384 debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug3: send packet: type 30 debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug3: receive packet: type 31 debug1: SSH2_MSG_KEX_ECDH_REPLY received debug1: Server host key: ecdsa-sha2-nistp384 SHA256:UyANwfU8ig+Uf3gKnpza2NfNH19MfjRQxURpwC7ou0U debug3: record_hostkey: found key type ECDSA in file C:\\Users\\zwx1262540/.ssh/known_hosts:2 debug3: load_hostkeys_file: loaded 1 keys from localhost debug3: Failed to open file:C:/Users/zwx1262540/.ssh/known_hosts2 error:2 debug1: load_hostkeys: fopen C:\\Users\\zwx1262540/.ssh/known_hosts2: No such file or directory debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts error:2 debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts: No such file or directory debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts2 error:2 debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts2: No such file or directory debug1: Host 'localhost' is known and matches the ECDSA host key. debug1: Found key in C:\\Users\\zwx1262540/.ssh/known_hosts:2 debug3: send packet: type 21 debug1: ssh_packet_send2_wrapped: resetting send seqnr 3 debug2: ssh_set_newkeys: mode 1 debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: Sending SSH2_MSG_EXT_INFO debug3: send packet: type 7 debug1: expecting SSH2_MSG_NEWKEYS debug3: receive packet: type 21 debug1: ssh_packet_read_poll2: resetting read seqnr 3 debug1: SSH2_MSG_NEWKEYS received debug2: ssh_set_newkeys: mode 0 debug1: rekey in after 134217728 blocks debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,kex-strict-c-v00@openssh.com debug2: host key algorithms: ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp384,ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256 debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512 debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512 debug2: compression ctos: none,zlib@openssh.com,zlib debug2: compression stoc: none,zlib@openssh.com,zlib debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug3: send packet: type 5 debug3: receive packet: type 7 debug1: SSH2_MSG_EXT_INFO received debug3: kex_input_ext_info: extension server-sig-algs debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256> debug3: kex_input_ext_info: extension publickey-hostbound@openssh.com debug1: kex_ext_info_check_ver: publickey-hostbound@openssh.com=<0> debug3: kex_input_ext_info: extension ping@openssh.com debug1: kex_ext_info_check_ver: ping@openssh.com=<0> debug3: receive packet: type 6 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug3: send packet: type 50 debug3: receive packet: type 7 debug1: SSH2_MSG_EXT_INFO received debug3: kex_input_ext_info: extension server-sig-algs debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256> debug3: receive packet: type 51 debug1: Authentications that can continue: password debug3: start over, passed a different list password debug3: preferred publickey,keyboard-interactive,password debug3: authmethod_lookup password debug3: remaining preferred: ,keyboard-interactive,password debug3: authmethod_is_enabled password debug1: Next authentication method: password sftp_dy@localhost's password: debug3: send packet: type 50 debug2: we sent a password packet, wait for reply debug3: receive packet: type 51 debug1: Authentications that can continue: password Permission denied, please try again. sftp_dy@localhost's password: debug3: send packet: type 50 debug2: we sent a password packet, wait for reply debug3: receive packet: type 51 debug1: Authentications that can continue: password Permission denied, please try again.
最新发布
06-10
配置文件检查打开OpenSSH服务器配置文件（位于`C:\ProgramData\ssh\sshd_config`），确保以下基本配置：```Port22ListenAddress0.0.0.0PasswordAuthenticationyes```修改配置后重启服务：```powershellRestart-...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值