I've taken Tim's advice and borrowed somebody's laptop to serve as a WinDbg host.
Now I'm having trouble getting a debug session started.
The host runs Windows 7, and I've installed WinDbg on it.
On the target, I've set the debug parameters thus...
The hostip is what I get from ipconfig on the host.
On the host WinDbg, I go into File : Kernel Debug..., select the NET tab, and enter port number 50000. There is no place to enter the key!
I click OK, and the Command window opens, showing...
Using NET for debugging
Opened WinSock 2.0
Waiting to reconnect...
Connected to target 192.168.0.100 on port 50000.
At the bottom, it reads "Debuggee not connected", and it doesn't allow me to enter anything there.
This is the correct IP for the target, but I don't know how the host found that out.
If I put a different port in the Kernel Debug... dialog, I don't get the last "Connected..." line, so I interpret that to mean that some sort of handshake was established with the target.
So what's wrong here??? Some sort of version mismatch between target and host?
I have a wireless router. The target is ethernet connected to the router, and the target is wireless connected to the router. That's supposed to be OK, as I understand it.
The host and target can both ping themselves and each other by their IP addresses.
I enabled the firewall on the target as requested the first time I tried Kernel Debug....
I've also tried disabling the firewalls on both ends, to no effect.
I'm going to try installing a matching version of Debug Tools on the target, and see if that helps. I don't know if the code that implements the target interface is built into Windows 10 or it comes from the Debug Tools. It's worth a try.