I am using Remote Desktop to connect to my dev box and a target. The
dev box is currently debugging the target via a 1394 cable.
Of all the times for the target’s DHCP address to expire! The target
now has a new IP address and I cannot use Remote Desktop to control it.
I need to know how to dump the target’s IP address through my windbg
connection. This should be possible, right?
Unfortunately, I cannot ping the name of the target because the subnet
on which it resides does not support SMB names – dang!
You RDP into your dev box from somewhere physically remote.
On this box, you’re running an instance of WinDbg that has already
established a kd session via 1394
Correct
I have no idea of what to tell you to do, other than perhaps take a look
around the ndis kd extension, and if you get really desperate, barring
better advice, you could try greping memory for something like
[0-9]+.[0-9+.[0-9]+ and hope for the best.
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of QuasiCodo
Sent: Tuesday, October 11, 2011 8:20 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Using windbg to dump the IP address of the target
I’ve got a problem.
I am using Remote Desktop to connect to my dev box and a target. The dev
box is currently debugging the target via a 1394 cable.
Of all the times for the target’s DHCP address to expire! The target now
has a new IP address and I cannot use Remote Desktop to control it.
I need to know how to dump the target’s IP address through my windbg
connection. This should be possible, right?
Unfortunately, I cannot ping the name of the target because the subnet on
which it resides does not support SMB names – dang!
I have no idea whether this will work on your system, but the following printed the right ipv4 address on my machine:
lkd> du poi(poi(srvnet!SrvAdminIpAddressList))
fffffa800d4b34a8 "127.0.0.1" lkd\> du <repeat a few times><br>lkd> du<br>fffffa800d4b3584 “aaa.bbb.ccc.ddd”
I found this variable by doing x !ipaddress. You could try other variations (e.g. networkaddress) if the above doesn’t work.
-----Original Message----- From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of QuasiCodo Sent: Tuesday, October 11, 2011 8:20 PM To: Windows System Software Devs Interest List Subject: [ntdev] Using windbg to dump the IP address of the target
I’ve got a problem.
I am using Remote Desktop to connect to my dev box and a target. The dev box is currently debugging the target via a 1394 cable.
Of all the times for the target’s DHCP address to expire! The target now has a new IP address and I cannot use Remote Desktop to control it. I need to know how to dump the target’s IP address through my windbg connection. This should be possible, right?
Unfortunately, I cannot ping the name of the target because the subnet on which it resides does not support SMB names – dang!
I bow before the master whose computational cycles I am not worthy to
cogitate.
((&->
On 10/12/2011 12:20 AM, Pavel Lebedynskiy wrote:
I have no idea whether this will work on your system, but the following printed the right ipv4 address on my machine:
lkd> du poi(poi(srvnet!SrvAdminIpAddressList))
fffffa800d4b34a8 "127.0.0.1" lkd\> du <repeat a few times><br>> lkd> du<br>> fffffa800d4b3584 “aaa.bbb.ccc.ddd” > > I found this variable by doing x !ipaddress. You could try other variations (e.g. networkaddress) if the above doesn’t work. > > -----Original Message----- > From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of QuasiCodo > Sent: Tuesday, October 11, 2011 8:20 PM > To: Windows System Software Devs Interest List > Subject: [ntdev] Using windbg to dump the IP address of the target > > I’ve got a problem. > > I am using Remote Desktop to connect to my dev box and a target. The dev box is currently debugging the target via a 1394 cable. > > Of all the times for the target’s DHCP address to expire! The target now has a new IP address and I cannot use Remote Desktop to control it. > I need to know how to dump the target’s IP address through my windbg connection. This should be possible, right? > > Unfortunately, I cannot ping the name of the target because the subnet on which it resides does not support SMB names – dang! > > Anybody have an idea? > > thx, > > ((&-> > > — > NTDEV 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 > >