Very Computer

The problem is that we have a mixed network of Linux and Windows boxes
and my main Linux machine's internal facing NIC is showing
RX packets:86272246 errors:3084 dropped:821 overruns:3084 frame:0
TX packets:80610778 errors:0 dropped:0 overruns:4 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4145544363 (3953.4 Mb)  TX bytes:3168716203 (3021.9 Mb)

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

Geoff Lane

Quote:> I think ipconfig is the closest windows command line utility.

winipcfg on older windows.

ipconfig /ALL

in combination with

route PRINT

Most of the stuff is gui based.  Not that they all of them are accessible
from the menu by default.  Control Panel -> System -> Device Manager ->
Network Interface -> Properties -> TCP/IP -> and friends. I'm kind of
surprised that I remember that. I haven't run windows or worked in windows
for several years.  Half a decade even.  The real trick is regedit.exe
tricks to change your MTU size and stuff.  Which varies between versions.

Why do they keep calling it java when it's really C#+-XYZ?  As I look at my
java game book, and see that almost every I/O call on it has been
deprecated.

Quote:

> 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.

> The problem is that we have a mixed network of Linux and Windows boxes
> and my main Linux machine's internal facing NIC is showing
> RX packets:86272246 errors:3084 dropped:821 overruns:3084 frame:0
> TX packets:80610778 errors:0 dropped:0 overruns:4 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:4145544363 (3953.4 Mb)  TX bytes:3168716203 (3021.9 Mb)

> 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?

Under NT4, W2K, XP and probably Vista:

'ipconfig' will get you ip address, subnet mask and default gateway.
'ipconfig /all' will get you more details (DNS, DHCP, etc...)

Also, if the machine is configured to use DHCP:
'ipconfig /release' will release the IP to DHCP
'ipconfig /renew' will request an address from the DHCP

--
There is an art, it says, or rather, a knack to flying.
The knack lies in learning how to throw yourself at the ground and miss.
Douglas Adams

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

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.

Quote:> 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