Target –> Win 8.1
Host Win 7
Target configured as
C:\Users\intel\Desktop>bcdedit /dbgsettings
key tom.dick.harry.trail
debugtype NET
hostip 10.7.151.73
port 59875
dhcp Yes
The operation completed successfully.
Host running WinDbg: 6.3.9600.17298
I give the port number and the key and I get the following error:
“NET parameters: key is not a valid parameter”
I have tried different port and key same error message
I can ping both ways target-host-target
I feel the bug is at the host debugger side …
thanks
I use 6.3.9600.16384(install with WDK8.1), it works.
wOULD YOU TRY A simple key, such as aaa.bbb.ccc.ddd?
Like wesly said, try some simple key first
bcdedit /dbgsettings NET HOSTIP:10.7.151.73 PORT:59875 KEY:1.2.3.4
Then set the bus parameter, I found this helpful to me, even if i got only one Ethernet card
bcdedit /set “{dbgsettings}” busparams b.d.f
b.d.f is your Ethernet device bus/device/function
Thanks to both I had tried with 1.2.3.4 and many other simple and default key nothing worked. I shall try b.d.f later. Now being the long weekend I am stuck at home eating cold Turkey :(. I have a Windows 7 at the host side and am running WinDbg: 6.3.9600.17298. Now my question is would going to a lower version i.e., 6.3.9600.16384 really matter? I can try it out but I Googled around could not find a place where I can download a older version. Anyway only Monday I can give all of this a try.
The documentation recommands to not pass the key but to let bcdedit generate a new one automatically. Without the key parameter, bcdedit will generate a new one and print it on the console. Just copy it and save it in a text file. Finally, copy the file from the target to the host machine.
The procedure is well explained here.
http://msdn.microsoft.com/en-us/library/windows/hardware/hh439346(v=vs.85).aspx
Ensure hostip is hostip not target_ip. Change port num to something high liek 65534 etc.
On Nov 27, 2014, at 4:35 PM, xxxxx@hotmail.com wrote:
The documentation recommands to not pass the key but to let bcdedit generate a new one automatically. Without the key parameter, bcdedit will generate a new one and print it on the console. Just copy it and save it in a text file. Finally, copy the file from the target to the host machine.
OK, but I hope you understand that this advice is useless. The key is just a string. As long as he hasn’t made a typo, it won’t make a single bit of difference whether he uses “tom.dick.harry” or “x” or “thisisaverylongridiculouslydifficulttotypekey0123456789”.
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
On Nov 26, 2014, at 2:27 PM, xxxxx@gmail.com wrote:
Target –> Win 8.1
Host Win 7
Target configured as
C:\Users\intel\Desktop>bcdedit /dbgsettings
key tom.dick.harry.trail
debugtype NET
hostip 10.7.151.73
port 59875
dhcp Yes
The operation completed successfully.
Host running WinDbg: 6.3.9600.17298
I give the port number and the key and I get the following error:
"NET parameters: key is not a valid parameter”
How did you give it the key? Did you put it on the command line, or from the GUI dialog? If you used a command line, please show us the EXACT command line you typed.
Have you made sure you don’t have any firewall issues?
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
>OK, but I hope you understand that this advice is useless. The key is just a string. As
long as he hasn?t made a typo, it won?t make a single bit of difference whether he
uses ?tom.dick.harry? or ?x? or ?thisisaverylongridiculouslydifficulttotypekey0123456789?.
Indeed, I understand that typing such a long key is ridiculous when you can just copy and paste it.
To the OP: the “tom.dick.harry.trail” key is valid. So you probably have a network configuration issue.
============================================================
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Using NET for debugging
Opened WinSock 2.0
Waiting to reconnect…
Connected to target 10.0.5.25 on port 50798 on local IP 10.0.5.58.
Connected to Windows 8 9600 x86 compatible target at (Fri Nov 28 15:47:12.962 2014 (UTC + 1:00)), ptr64 FALSE
Kernel Debugger connection established.
Thanks for all the advice after much wasting time my company network admin told me that they dont allow debug packets on corporate net work. Also I read that for WinDbg to work via net there should not be routers and repeaters. Is that true? Can I sitting in US attach using th NET option a system in Bangalore? Anyway my problem did solve sort of by having a local system with a built in com port, The good old method which never fails. Please treat this case as closed. Once again thanks to all helped me get a better understanding