Connecting Windbg via Ehternet

I’ve been trying to connect Windbg to a Windows Server 2016 target but I
have been unsuccessful. I’ve tried a number of things but have not *ever*
been able to get beyond the “Debugee not connected” state.

Below is a description of the operating environment:

  • The host machine is running Windows 10 Pro, 1803
  • The target machine is running Windows Server 2016
  • The host and target are connected through a hub. I’ve also tried a switch
    and got the same results.
  • The Windbg version is 10.0.17134.12. I’ve also tried version
    10.0.16299.91 and got the same results.
  • I’ve used both dynamic IP addresses and static IP addresses and got the
    same results.
  • The target can ping the host/the host can ping the target.
  • The Firewall has been configured on the host allow network access to
    “Debugging Tools for Windows”.

The following BCDEDIT commands were used to set up the target:
bcdedit /debug on
bcdedit /dbgsettings net hostip: port: 50085 key
bcdedit /set “{dbgsettings}” busparams 1.0.0

I’m pretty sure that the target is set up correctly because the NIC is
shown “banged out” in Device Manager with the error message "This device
has been reserved for use by the windows kernel debugger …. ".

Can anyone provide any help on this issue?
Thanks in advance.

It’s some time since you posted this question - did you ever get to the bottom of it?

For the sake of others who come across this post: did you check whether your target’s NIC is listed on Supported Ethernet NICs for Network Kernel Debugging in Windows 10 ?