COMMAND

    netstat.exe

SYSTEMS AFFECTED

    WinNT

PROBLEM

    Alex Libenson found a memory leak in NETSTAT.EXE - it didn't  free
    memory used for connection table. You  can see it if you will  run
    it in a loop - NETSTAT <interval>.  Best way to reproduce it:

        NETSTAT.EXE -n 1

    run it and check netstat's memory usage in Task Manager...  If you
    have much connections it will grow very fast - up to some  10-20MB
    in ten minutes.  MS acknowledged some SNMP agents have leak memory
    when multiple  SNMP requests  are sent  rapidly in  a loop  to the
    server.  This is  why NETSTAT 1 grabs  memory - netstat uses  SNMP
    to get TCP connections table.

SOLUTION

    Nothing yet.  MS should fix this.  Check MS Q Article Q160035.