if you are looking for a free Network Monitor, have a look on Ethereal. Ethereal has a decode for the Winsock Proxy messages (firewall client). Moreover, there is also a plugin available for decoding the H.323 protocol.
Ethereal is da bomb! I use it as THE main troubleshooting tool for ISA. I was able to diagnose all kinds of problems - like a request that does not answer for 3 min (resulting in ISA closing the connection)
It's free....simple...and tres cool. I even clued Microsoft into it.
Best of all, when the MS code jockeys insist on getting sniffs in Network Monitor format, you sniff with Ethereal, save it as a NetMon2 file, and send it along. Works just fine.
Ethereal takes tcpdump file generated by Unix, Linux, and even OpenVMS machines and translates them to NetMon or anything else you want.
Posts: 5
Joined: 1.May2003
From: Perth, Australia
Status: offline
the library that ethereal uses for packet capturing appears to support remote capturing...
"WinPcap 3.0 comes with Remote Capture capabilities. This is an highly experimental feature that allows to interact to a remote machine and capture packets that are being transmitted on the remote network."
taken from //winpcap.polito.it/docs/man/html/group__remote__help.html
yes! You need to take a capture in promicious mode. Of course the Ethereal host should see all the traffic. Therefore, he should be sitting on the same segment 'shared' by a hub, not a switch.
However, on ISA server itself you can use also the buildin Network Monitor tool (W2K server feature) and import the traces in Ethereal for further analyzes.
1. IF your INTERNAL NIC card is connected to a HUB, then your workstation on the same hub MIGHT be able to see it, but only if the speeds are the same (both the ISA NIC and the workstation NIC) and you are capturing in promiscuous mode.
2. Ethereal will NOT work if you are trying to go into your ISA box with Terminal Services. In thta case, you have to use tethereal (comes in the same package) and dig around a little bit to make sure you are capturing off the correct NIC card. Here's a piece of code I use: ===============================
code:
rem Ensure the following strings are set for your machine! rem Every adapter is unique!
SET Inside=\Device\Packet_{F3302A50-97CF-4EEC-AC5D-71DDDA4DD6CA} SET Outside=\Device\Packet_{A1B99062-0754-4974-B396-B5055B37E757}
@Echo Off rem Ensure you include a quoted filter expression!
1) if you are using a real hub, then the workstation should always see the traffic when capturing in promicious mode. A so called dual speed hub is not really a hub. Between the 10 and 100 Mbps internal segments there is a little switch.
2) on ISA server itself I always use the buildin Network Monitor and analyze the capture with Ethereal.
I'm using ISA at home on a Win2k server that is also DC for my small personal domain. The external connection is provided trough a dial-up PCI ADSL Card using PPPoE. I'm aware that this is not a correct configuration but it works fine and fulfill my personal needs for the moment.
However I'm experiencing some problems with my home banking application.
I'd like to know precisely how to use a network sniffer to troubleshoot these problems and at least give a useful information to the helpdesk of my bank.
I tried to Sniff the traffic with Netmon but I didn't capture even one single packet of the external traffic.
Could somenone explain me how to setup the Winpcap driver to succesfully capture this traffic on the ISA server. First or all is it safe regarding the stability of my server ?
Yes but the packet capture filters are a PAIN to setup. You have to know libpcap syntax, and I don't have to use Ethereal frequently enough to remember it! Packetyzer makes filtering SO much easier.