Failed to connect Windbg to 2008R2 using named pipe

WINDBG
1

Hi All,

I wanted to connect WinDBG for debugging, two systems (Debugee and Debugger) are VMs on ESXi 6.5 server, created named PIPE in on both systems. Followed all instructions ?https://communities.vmware.com/docs/DOC-15691?
Debugger System :Windows 10 and target Debugee: Windows Server 2008 R2, but I failed to connect WinDbg properly, showing message ?waiting to connect? for infinite time. Target Debuggee is blocked/Freezed but WinDbg
not able to proceed.

I have noticed one observation that, on creating named pipe on Target system(2008R2), didn?t find any port when checked in Device Manager, expecting port COM1 or COM2 to be created.

Checked with different pipe naming conventions ?pipe2k8? also ?\.\pipe\pipe2k8?.

Any clue will be really helpful.

Thanks in advance.

~Sachin

2

I am able to connect two VMs bidirectionally using hyperTerminal

3

I’ll start by saying I have never tried this configuration…

Have you tried manually breaking with WinDbg on the debugger system
(Ctrl+Break)? Also, if you turn our debug protocol output with Ctrl+Alt+D do
you see anything?

-scott
OSR
@OSRDrivers

wrote in message news:xxxxx@windbg…

I am able to connect two VMs bidirectionally using hyperTerminal

4

Thanks Scott.

Got problem solved, CHECKed pipe and reconnect options, need to these options UNCHECK in WinDBG as per VMware esxi doc.