Moved host system to a different network switch.Once the connection has been lost, I tried this hoping it would re-establish connection. Unplugging the Ethernet cable, and then plug it back in.I've tried a hand full of different network ports (49152-65535) just in case one of them is being used for a different purpose. However, further investigation shows that vendors have a bad habit of not updating their device IDs, so I decided to rule out this possibility by buying new adapters from different vendors. According to this webpage, my network adapter should support network kernel debugging. I tried this after reading this post: WinDbg, host machine lose network if test machine is on the same switch Disabling Flow Control, and using Half Duplex mode, on the network adapter.Setting up the systems: I followed instructions from MSDN website to setup my target and host systems.ĭebugging: Below are my attempts to resolve this issue. I use "!ustr srv!SrvComputerName" to get the target computer name, and it returns the correct name. Moreover, It seems like the connection is good while in debug break, because I can gather information from the target system. I can even see debug print statements in WinDbg as I use the target system during this grace period. However, if I never break into the debugger, it looks like the connection is stable for an 'N' period of time. 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 (Debug->Go).
0 Comments
Leave a Reply. |