Network debugging, took PCs off the DHCP network, WinDbg can no longer connect

It wasnt me who called someone dense Peter.

No, Mr Sykes… but Mr, Roberts has answered questions for quite literally hundreds of people here. His uniform willingness to help, coupled with his exceptional patience, are the stuff of legend. This has earned him the undisputed right to receive respect and deference from every member of this community. And this level of respect is due him regardless of whether Mr, Roberts might display a rare level of frustration in one of his numerous replies.

When you speak disrespectfully to Mr. Roberts, regardless of the provocation, it is not acceptable to me. When you couple this with a snarky reply to me… well, that earns you a bit of a rebuke.

I’m not sure why I need to explain this to you Mr. Sykes. You’ve been here for about five years. Surely you know the rules by now.

Regardless, I’ve taken ten minutes from my Saturday morning to explain this to you, as opposed to going with the faster and simpler alternative of putting you on moderation (which takes 3 mouse clicks), which was my first inclination.

Any reply to this post from you, other than perhaps “Thank you Peter, you are both wise and good looking”, would be Ill-advised. If you want to continue the vain attempt to justify your actions, or you wish to try my patience further in any other way, I ask you to please do so with a direct email. My direct email is visible in my profile.

Peter

Thank you for the information @Tim_Roberts , I forgot that KDNET maintains its own IP address stack!

@Tim_Roberts said:

The kernel debugger (meaning the part embedded in the target computer’s
kernel) is able to connect a windbg on a machine with a static IP, but
it has never supported assigning a static IP to itself. You either use
DHCP, or you get a fallback address in the 169.254.x.x range. That
range is not routable, so the two computers have to be directly connected.

Note that the IP address assigned to the network adapter by the
operating system is irrelevant. The kernel debugger has its own
independent driver stack.

I wrote a SuperUser post based on extreme slowness to boot with static network. KDNET takes ~10minutes to fall back on link-local address when DHCP server is unavailable. I discovered the DHCP:yes flag was set by default, clearing that flag (on RS5 17763.1) allowed network debug to work as intended.

https://superuser.com/questions/1404669/crossover-computer-connection-vs-network-switch-broadcast-packet-differences

Actually makes it easier, because toggling the IP address of the target machine in Windows is sufficient to block internet access (NDA project), without needing a direct network cross-over connection. WinDbg settings can remain on DHCP

I would recommend amending the Network debug articles to include the nodhcp documentation from https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/bcdedit--dbgsettings as that was definitely missed by me as well.

I would recommend amending the Network debug articles to include the nodhcp

That is an excellent idea.

Are you aware that the docs are on github… and you can do the edits yourself? Seriously. Go to that page, and you’ll see an “edit” link at the top. Go for it! The doc folks are very pleasant to deal with and appreciative of contributions.

Peter

Actually Peter I have been here since the dawn of time, been writing windows drivers since the days of NT4. (remember the old discussion forum we used before you created these ones on osr? WHat was it, google groups or some such, I forget)

But anyway, I see someone else has agreed with me, that nodhcp is not clearly documented, and nice to see you agree Peter. Now perhaps we can put whatever misunderstanding everyone suffered in this thread behind us and move on.

Actually Peter I have been here since the dawn of time

Then you should really know the rules, Mr. Sykes, know that Mr. Roberts is worthy of your respect, and act likewise.

What was it, google groups or some such, I forget

It was way before there was a Google, Mr. Sykes. Those original forums, back in the 1993 and 1994, were on CompuServe. We’ve been answering questions about how to write Windows (NT) drivers for a long, long, time here at OSR…

Oh, these were the days…

Peter
(thread closed)