WinDbg会话无法连接：内核模式驱动调试实验室问题求助

按照微软官方《Debug Windows drivers step-by-step lab (echo kernel mode)》实验步骤操作，执行到第8步重启目标机后，目标机无法与主机建立WinDbg连接。主机IP地址192.168.0.183确认正确，已关闭Windows防火墙，调试密钥也核对无误，但问题仍未解决。

目标机执行bcdedit /enum all的输出如下：

Firmware Boot Manager
---------------------
identifier              {fwbootmgr}
displayorder            {bootmgr}
                        {3b372d9e-b8b8-11ed-9af1-806e6f6e6963}
                        {8b84a908-a37d-11ed-9aed-806e6f6e6963}
timeout                 1

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {7e7d0076-9117-11ed-a6ff-a7cd5c734c1b}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Firmware Application (101fffff)
-------------------------------
identifier              {3b372d9e-b8b8-11ed-9af1-806e6f6e6963}
description             UEFI: PXE IPv4 Intel(R) Ethernet Controller (3) I225-LM

Firmware Application (101fffff)
-------------------------------
identifier              {8b84a908-a37d-11ed-9aed-806e6f6e6963}
description             UEFI: PXE IPv6 Intel(R) Ethernet Controller (3) I225-LM

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 11
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {7e7d0078-9117-11ed-a6ff-a7cd5c734c1b}
displaymessageoverride  Recovery
recoveryenabled         Yes
testsigning             Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {7e7d0076-9117-11ed-a6ff-a7cd5c734c1b}
nx                      OptIn
bootmenupolicy          Standard
debug                   Yes

Windows Boot Loader
-------------------
identifier              {7e7d0078-9117-11ed-a6ff-a7cd5c734c1b}
device                  ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{7e7d0079-9117-11ed-a6ff-a7cd5c734c1b}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-us
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{7e7d0079-9117-11ed-a6ff-a7cd5c734c1b}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Resume from Hibernate
---------------------
identifier              {7e7d0076-9117-11ed-a6ff-a7cd5c734c1b}
device                  partition=C:
path                    \Windows\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
recoverysequence        {7e7d0078-9117-11ed-a6ff-a7cd5c734c1b}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
custom:21000026         partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      Yes

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\memtest.efi
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes

EMS Settings
------------
identifier              {emssettings}
bootems                 No

Debugger Settings
-----------------
identifier              {dbgsettings}
key                     2steg4fzbj2sz.23418vzkd4ko3.1g34ou07z4pev.1sp3yo9yz874p
debugtype               NET
hostip                  192.168.0.183
port                    50000
dhcp                    Yes

RAM Defects
-----------
identifier              {badmemory}

Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}

Device options
--------------
identifier              {7e7d0079-9117-11ed-a6ff-a7cd5c734c1b}
description             Windows Recovery
ramdisksdidevice        partition=\Device\HarddiskVolume4
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

排查建议 #

• 确认目标机与主机处于同一局域网，双向网络连通：在目标机执行ping 192.168.0.183，主机执行ping 目标机IP，确保无丢包
• 核对WinDbg监听配置：主机端WinDbg选择File > Kernel Debug > Net，输入端口50000和调试密钥，确保与目标机bcd设置完全一致
• 尝试禁用DHCP，手动指定目标机IP：执行bcdedit /set {dbgsettings} dhcp No，再设置bcdedit /set {dbgsettings} targetip 目标机静态IP，重启后测试
• 关闭Hypervisor调试：当前bcd中hypervisorsettings配置为串口调试，若目标机开启Hyper-V可能干扰网络调试，执行bcdedit /set {hypervisorsettings} hypervisordebugtype None后重启
• 确认引导项正确性：重启目标机时手动选择Windows 11引导项，避免进入恢复或休眠唤醒模式
• 更新目标机网卡驱动：部分网卡在调试模式下存在兼容性问题，更新驱动后重试
• 关闭第三方安全软件：除Windows防火墙外，第三方杀毒、安全工具可能拦截调试流量，暂时关闭测试

内容的提问来源于stack exchange，提问作者peregrinus