WinDbg loses connection debugging over network, and target machine freeze

Question

I\'m trying to get WinDbg debugging over the network to work, but it always loses connections after I break into the debugger (Debug->Break), and then try to start it again (Deb

Answer 1

I finally solved this problem by switching the host system. In the beginning, I thought the target system was the problem, because MSDN only put the NIC debug requirement on the target system. It appears that there might be requirements placed the host system as well.

New host system: Desktop (Identical to target system)

• OS: Windows 8.1 Enterprise Evaluation x64
• NIC: VEN_10EC&DEV_8168

Previous host system: Laptop

• OS: Windows 8.1 Pro x64
• NIC: VEN_8086&DEV_1502

NOTE: I don't really know the root cause. Both NICs are on the Supported Ethernet NICs list, I used the same WinDbg version that came with the WDK, and all systems are on the same switch.

Answer 2

I found a simpler solution that worked for me in VMware, The problem is in vmware - the NAT connection has a 30 seconds timeout. This value is configurable. Go to edit -> virtual network editor -> change settings (uac prompt) -> select NAT in the list -> NAT settings -> UDP timeout. The max value is 32767, the default (for me) was 30 seconds. It completely solved my problem.

Answer 3

The problem is with the host. If you don't want to change your host and continue debugging on it, you might want to try using a serial port. It gives better performance. Take a look at the following link for setting up debugging of a virtual machine over com port:

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/attaching-to-a-virtual-machine--kernel-mode-?redirectedfrom=MSDN

Answer 4

I had the similar problem and solved it by using USB to Ethernet adapter on the host machine instead of in built NIC card.

Answer 5

I also met this issue, and found that when I try to force shutdown VMWare OS, the windbg connection seems recover before VMWare OS is actually closed. After several tries, I found a weird solution:

When the windbg connection between host and VMWare guest lost, try to click "shutdown VMWare Guest", but DO NOT really confirm. And you may found that the windbg connection recovers! Then, cancel the shutdown.

It's very strange, seems VMWare itself blocked the network debugging connection lost. But at least it's a workaround worth trying.

Another workaround I tried, which sometimes work, is killing windbg in task manager, and re-run windbg and reconnect to VMWare guest. And may need wait seconds to minutes until it reconnects.

btw, my ethernet card is Intel Ethernet Connection I218-V.