I can deploy a driver to the Target machine with Visual Studio but no debug session is started. Likewise WinDbg just says Waiting to reconnect…
Before and after reboot, bcdedit reports the expected dbgsettings, where DHCP is Yes,
and Device Manager status for the NIC says it’s been reserved for use by the kernel debugger!
Windows 10 as both Host and Target.
I’m on a home router where DHCP works for everything I’m aware of… is it possible that this is a problem? How can I tell what the target is trying to do?
Are there any logs on the target to help?
(registry hkey_local_machine/system/currentcontrolset/services/kdnet does not have a kdinitresultstring entry)
What dumb thing am I (not?) doing? I just reboot the target machine and it comes up in WDKRemoteUser… is there anything more to do on the target? Are UDP packets supposed to be exchanged when WindDbg starts?
Any suggestion will be appreciated…
Is your NIC on the supported list? (check VerifiedNICList.xml in the WinDbg
installation folder)
-scott
OSR
@OSRDrivers
wrote in message news:xxxxx@windbg…
I can deploy a driver to the Target machine with Visual Studio but no debug
session is started. Likewise WinDbg just says Waiting to reconnect…
Before and after reboot, bcdedit reports the expected dbgsettings, where
DHCP is Yes,
and Device Manager status for the NIC says it’s been reserved for use by the
kernel debugger!
Windows 10 as both Host and Target.
I’m on a home router where DHCP works for everything I’m aware of… is it
possible that this is a problem? How can I tell what the target is trying to
do?
Are there any logs on the target to help?
(registry hkey_local_machine/system/currentcontrolset/services/kdnet does
not have a kdinitresultstring entry)
What dumb thing am I (not?) doing? I just reboot the target machine and it
comes up in WDKRemoteUser… is there anything more to do on the target? Are
UDP packets supposed to be exchanged when WindDbg starts?
Any suggestion will be appreciated…
Yes, it’s 8086/109A … I’m assuming the “requires further installation” in Device Manager Events Information window is due to its being reserved by the debugger (!?) … and in Resources: isn’t using any resources because it has a problem (!) Or does that mean there IS a problem? I can ping it from host ok. Wait… I can surf the Web! Does that mean the debugger does NOT have control?
Thanks so much for help… If I should post everything I can think of, e.g. bcdedit outputs, please say.
In Device Manager the real NIC will have a yellow bang and the error should
indicate that it is reserved for use by the kernel debugger. This is normal.
Do an ipconfig /all, the kernel debug network adapter should have an IP
address from your local network. Having kernel debugging enabled does not
limit the normal use of your NIC.
Have you disabled the firewall on your host? I’d also try running WireShark
and see if you see any traffic from the guest to the host.
-scott
OSR
@OSRDrivers
wrote in message news:xxxxx@windbg…
Yes, it’s 8086/109A … I’m assuming the “requires further installation”
in Device Manager Events Information window is due to its being reserved by
the debugger (!?) … and in Resources: isn’t using any resources because it
has a problem (!) Or does that mean there IS a problem? I can ping it from
host ok. Wait… I can surf the Web! Does that mean the debugger does NOT
have control?
Thanks so much for help… If I should post everything I can think of, e.g.
bcdedit outputs, please say.
Fixed!
I couldn’t get syslog working in the router so I used a new one and now debugging works. I have no idea why, though.
Thanks again -