From: Shadow_7 on
> netsh opens a shell. There is no "diag" and none of the available
> commands looks promising. What version of Windows does this work for?

Apparently Vista. I just used netsh for the first time today.

netsh interface ipv4 show subinterfaces
netsh interface ipv4 set subinterface "1" MTU=576 stored=persistent

(or something like that)
I guess that's better than hacking the windows registry to change MTU
size. But still a bit cryptic and relatively undocumented. I had to
google from linux to get that gem. Because I couldn't get anything across
the internet aside from a ping until I made the change. Which is odd
because it worked fine six months ago when I last booted windows.
From: lawnman on
On Mar 12, 2:54 pm, buck <b...(a)private.mil> wrote:
> I have been searching for hours trying to find a utility for Windows
> that will return the same information as ifconfig regarding overruns,
> frame, carrier, Etc. and I find nothing at all.
[...]
> and I need to find the Bad Boy that is causing all those overruns.
> Short of booting a live Linux distro on each Windows box, is there
> some tool available for detecting the source of the RX overruns?
> --
> buck

netstat -es
From: buck on
On Tue, 8 Apr 2008 17:11:08 -0700 (PDT), lawnman(a)gmail.com wrote:

>On Mar 12, 2:54 pm, buck <b...(a)private.mil> wrote:
>> I have been searching for hours trying to find a utility for Windows
>> that will return the same information as ifconfig regarding overruns,
>> frame, carrier, Etc. and I find nothing at all.
>[...]
>> and I need to find the Bad Boy that is causing all those overruns.
>> Short of booting a live Linux distro on each Windows box, is there
>> some tool available for detecting the source of the RX overruns?
>> --
>> buck
>
>netstat -es


YES! That works well enough. Thank you so much.
--
buck