FW: remote connection via LAN

WINDBG
1

>

Ok, thanks Don,
Now what can i do to see KdPrint or other log files on PC1?

-- LAN

*
*
___________ *
*__________
| PC1 |
| PC 2 |
***************
**************
WinDbg Client WinDbg
Server(BSOD problem)

Osman

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Monday, March 14, 2011 4:44 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] remote connection via LAN

No that type of connection is one Windbg to another Windbg, the remote
Windbg then needs to connect to the test machine with one of the
mechanisms in my earlier post.

Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Osman TOKER
Sent: Monday, March 14, 2011 10:41 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] remote connection via LAN

I can connect by;

Local machine command(Windbg) : .server tcp:port = 9000 Remote machine
command(Windbg) : tcp:Port=9000,Server=servername (from a writing of
Herbert Zimbizi)

Result : OSMAN-TOKER\otoker (tcp 47.168.2.140:2940) connected at Mon
Mar
14 17:28:28 2011

But i couldnt see anything on the remote machine Windbg monitor while
BSOD appears on the local machine.

Osman

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Monday, March 14, 2011 4:32 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] remote connection via LAN

Your choices are serial port, 1394 or if you are lucky USB. There is
no support for a remote machine over an Ethernet connection.

Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@netas.com.tr
Sent: Monday, March 14, 2011 10:23 AM
To: Kernel Debugging Interest List
Subject: [windbg] remote connection via LAN

Hi,
i have a BSOD error and want to debug from another pc. This two
computer are on the same LAN( can ping each-other) but i couldnt use
their serial ports.
Can i connect this two computers by Windbg(can remote connection)
without serial ports and any other programmes(VM, VirtualBox)? How?

WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
OSR Seminars – OSR

To unsubscribe, visit the List Server section of OSR Online at
ListServer/Forum

WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
OSR Seminars – OSR

To unsubscribe, visit the List Server section of OSR Online at
ListServer/Forum

WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
OSR Seminars – OSR

To unsubscribe, visit the List Server section of OSR Online at
ListServer/Forum

WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
OSR Seminars – OSR

To unsubscribe, visit the List Server section of OSR Online at
ListServer/Forum

2

You are going to have to setup Windbg to effectively debug. So find a way
to get a serial connection or a 1394 link from a machine running Windbg to
the test machine that is having problems. There is no other way to really
debug.

Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Osman TOKER
Sent: Monday, March 14, 2011 11:11 AM
To: Kernel Debugging Interest List
Subject: FW: [windbg] remote connection via LAN

Ok, thanks Don,
Now what can i do to see KdPrint or other log files on PC1?

– LAN –

* *

___________ *
*__________
| PC1 | |
PC 2 |
***************
**************
WinDbg Client WinDbg
Server(BSOD problem)

Osman

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com
mailto:xxxxx ] On Behalf Of Don Burn
Sent: Monday, March 14, 2011 4:44 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] remote connection via LAN

No that type of connection is one Windbg to another Windbg, the remote
Windbg then needs to connect to the test machine with one of the mechanisms
in my earlier post.

Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com http:
Blog: http://msmvps.com/blogs/WinDrvr http:

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com
mailto:xxxxx] On Behalf Of Osman TOKER
Sent: Monday, March 14, 2011 10:41 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] remote connection via LAN

I can connect by;

Local machine command(Windbg) : .server tcp:port = 9000 Remote machine
command(Windbg) : tcp:Port=9000,Server=servername (from a writing of Herbert
Zimbizi)

Result : OSMAN-TOKER\otoker (tcp 47.168.2.140:2940) connected at Mon Mar
14 17:28:28 2011

But i couldnt see anything on the remote machine Windbg monitor while BSOD
appears on the local machine.

Osman

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com
mailto:xxxxx] On Behalf Of Don Burn
Sent: Monday, March 14, 2011 4:32 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] remote connection via LAN

Your choices are serial port, 1394 or if you are lucky USB. There is no
support for a remote machine over an Ethernet connection.

Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com http:
Blog: http://msmvps.com/blogs/WinDrvr http:

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com
mailto:xxxxx] On Behalf Of
xxxxx@netas.com.tr
Sent: Monday, March 14, 2011 10:23 AM
To: Kernel Debugging Interest List
Subject: [windbg] remote connection via LAN

Hi,
i have a BSOD error and want to debug from another pc. This two computer are
on the same LAN( can ping each-other) but i couldnt use their serial ports.

Can i connect this two computers by Windbg(can remote connection) without
serial ports and any other programmes(VM, VirtualBox)? How?

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars http:

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
http:

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars http:

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
http:

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars http:

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
http:

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars http:

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
http:

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer</http:></http:></http:></http:></http:></http:></http:></http:></mailto:xxxxx></http:></http:></mailto:xxxxx></mailto:xxxxx></http:></http:></mailto:xxxxx>

3

What type of driver is this? If it is not a PNP driver that controls hardware, you may very easily be able to run the driver in a VM (virtual machine) and use WinDbg in that manner via a Pipe which is well documented in WinDbg. You’ve wasted a hell of a lot of time coming here to ask questions that you could have more beneficently used fixing your problem by simply using WinDbg to step into and examine your own code.

I suspect your !analyze -v output came from the use of OSR dump facility. That’s really great, but NOTHING can benefit your debug capability MORE than having WinDbg available via either a VM or Host/target setup.

Gary G. Little

----- Original Message -----
From: “Osman TOKER”
To: “Kernel Debugging Interest List”
Sent: Monday, March 14, 2011 10:10:48 AM
Subject: FW: [windbg] remote connection via LAN

FW: [windbg] remote connection via LAN

Ok , thanks Don ,
Now what can i do to see KdPrint or other log files on PC1?

----------------------------
– LAN –
----------------------------
* *
_* *
| PC1 | | PC 2 |
*****************************
WinDbg Client WinDbg Server(BSOD problem)

Osman

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Monday, March 14, 2011 4:44 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] remote connection via LAN

No that type of connection is one Windbg to another Windbg, the remote Windbg then needs to connect to the test machine with one of the mechanisms in my earlier post.

Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Osman TOKER
Sent: Monday, March 14, 2011 10:41 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] remote connection via LAN

I can connect by;

Local machine command(Windbg) : .server tcp:port = 9000 Remote machine command(Windbg) : tcp:Port=9000,Server=servername (from a writing of Herbert Zimbizi)

Result : OSMAN-TOKER\otoker (tcp 47.168.2.140:2940) connected at Mon Mar
14 17:28:28 2011

But i couldnt see anything on the remote machine Windbg monitor while BSOD appears on the local machine.

Osman

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Monday, March 14, 2011 4:32 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] remote connection via LAN

Your choices are serial port, 1394 or if you are lucky USB. There is no support for a remote machine over an Ethernet connection.

Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@netas.com.tr
Sent: Monday, March 14, 2011 10:23 AM
To: Kernel Debugging Interest List
Subject: [windbg] remote connection via LAN

Hi,
i have a BSOD error and want to debug from another pc. This two computer are on the same LAN( can ping each-other) but i couldnt use their serial ports.

Can i connect this two computers by Windbg(can remote connection) without serial ports and any other programmes(VM, VirtualBox)? How?

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

4

Osman TOKER wrote:

I can connect by;

Local machine command(Windbg) : .server tcp:port = 9000
Remote machine command(Windbg) : tcp:Port=9000,Server=servername (from a
writing of Herbert Zimbizi)

Result : OSMAN-TOKER\otoker (tcp 47.168.2.140:2940) connected at Mon Mar
14 17:28:28 2011

But i couldnt see anything on the remote machine Windbg monitor while
BSOD appears on the local machine.

You can do application debugging that way, but you cannot do kernel
debugging over Ethernet. To do kernel debugging, you must use either a
serial port, 1394, or USB, as Don said.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.