Recent content by jrsavage

Anyone know where I can find a promiscuous driver for a Realtek rtl8187 chipset? Thanks

You need to look at McAfee's web site for the specific virus. If there's a Sniffer filter available there will be a link to it in there. There is no master filter posted on Sniffer.com.

Use the autodiscovery feature of the address book within Sniffer. You can either enter a range of IPs which will ping the selected range, or select any IP address on the network which will sit there and listen to traffic to correlate Netbios names with IP and MAC addresses. Savage

The utilization you see is for the port that you have sniffer connected to. Not the switch or the VLAN. JRSavage.

Also Sniffer will not capture collisions that occur during the preamble. Most collisions on a hub will occur during this time. J.R. Savage

Send me one of the traces and I'll take a look. jsavage@nai.com

Reporter is free and included with distributed Sniffer and Sniffer Investigator. I've never heard of it selling for $500. J. Savage

Mikes999, Check out the new Sniffer Investigator at www.sniffer.com. For the money it is an outstanding portable analysis tool that comes pre-configured on it's own dedicated laptop. J.R.S.

Thanks

The only desktop (PCI) NIC supported by Sniffer is the Adaptec ANA-6911A. This is the only PCI NIC that that works in conjunction with the NAI enhanced drivers that allow you to see packets damaged at layers 1 and 2 of the OSI model

There is no "real time" display when capturing with sniffer basic. Sniffer pro will give you real time expert analysis when capturing but you still have to stop the capture to view the packets. JR Savage Sniffer SE Dallas TX

Check that Sniffer is not in loopback mode. Also do a capture while generating traffic to verify that you are actually doing so. JR Savage Sniffer SE Dallas TX

WYB, I agree with your example. I've seen quite a bit of crummy programming myself. Another thing to bear in mind is that "symptoms" in themselves are relatively minor issues which may or may not indicate a larger problem. That's why you may see large numbers of a particular symptom...

Below is the actual sniffer expert explain of the error Window Frozen In a windowing protocol (such as DECnet or TCP), the window size of this station has been stuck at some number of bytes for longer than the Window Frozen Time threshold. When a window is stuck, data flow will not be as...

\program files\nai\winnt\driver\xircom\win2k