Slashdot Mirror


Need Help w/ MRTG & IP Accounting for Windows 2000?

Nasko asks: "We use a cable modem to connect our 29 PC's in the LAN to the Internet. I'm routing with Windows 2000 Professional and WinRoute. I've successfully set up a MRTG to show me the traffic for the 2 LAN interfaces in the routing machine, but couldn't find any way to get reports for the in/out traffic per local IP address. Most of the PC's are running under Windows 98 so I can't (at least i I don't think so) set up SNMP agents on them - I'll appreciate any help concerning filtering out the SNMP info from the routing machine coming from/going to a specific local interface - in fact i'm not sure if there's a way to filter that on the 'Target' line of a MRTG .CFG file. Alternatively, where I can find IP Accounting software for Windows 2000 so that I can 'feed' my MRTG, by using Perl to provide the 2 needed values?"

5 comments

  1. Answers: by Enry · · Score: 4

    Try:

    google to get info about Win2k SNMP agents

    google for info about regular windows SNMP agents.

    Agents are available for both OS's and seem to be built in (gasp!)

    1. Re:Answers: by sid+crimson · · Score: 1


      Is there some way for MRTG to distinguish internet traffic from Client/Server traffic?

      -sid

  2. MRTG is great, but have you seen opennms.org by danpbrowning · · Score: 3

    Check out opennms.org. In my opionion you would be much happpier with that than MRTG alone.

    As far as SNMP on the client boxes, check out your NIC card docs. Intel nics come with some SNMP trapping/reporting software if I recall.

    -Dan

    --
    Daniel
  3. wrong approach by Clover_Kicker · · Score: 2

    There's no need to query each box. The information you want is on your local wire, so stick something like ntop on the network and let it collect your stats.

  4. Wrong OS.. . by rsoucy · · Score: 1

    I could talk trash about Microsoft, but I won't.. If I remeber correctly you need Windows2000 Server, not Profesional, and in server there is built-in routing under Administrative Tools. That should solve your problem.. pending, of course, that your willing to pay the $800 price tag on Windows 2000 Server ;) Otherwise, I'd sugest 3rd party software.