Only a windbg session could not be established. To confirm bad firewall setting was not the problem, I did confirm that a TCP connection can be made from my guest to the same port of that physical machine. in my guest win10, w.x.y.z below is set to the IP address of that physical machine), no windbg session was established. VM set to use bridged adapter just like above, the guest was assigned its own IP address by the DHCP server of my network, and was able to access the internet, windbg was running in another physical machine with another ip address, guest win10 debug session pointed to the IP address of that separate machine (i.e. debug connection was successfully establishedģ VM set to use bridged adapter, the guest was assigned its own IP address by the DHCP server of my network, but windbg was running in the host, debug connection was successfully establishedĤ. Marked as answer by Brian Catlin Friday, J3:45 AM. It finally works Now the same NIC can be used to do both kernel debug and normal NIC functionality. devcon.exe install \windows\inf root\kdnic. we have to go to 'cmd' and just type 'cmd'. Finally I tried the devcon.exe from latest windows WDK using the following command line (run cmd as admin). VM set to use host-only networking while windbg was running in the host. In this Video we are going to see how to disable Microsoft Kernel Debug Network Adapter. VM set to use NAT and no session established to windbgĢ. Some further testing, I found these results:ġ. Run as administrator (elevated): msconfig -> Boot ->Advanced options.
0 kommentar(er)
