Recent content by alail

The ANA6911 won't work because Adaptec stopped building it, there are no drivers for win2k - you should consider using the 4port EN card or the newer version of the Adaptec card. NAI can tel you which cards work with what OS. If PHY errors aren't critical, try another NIC, shouldn't matter as...

Sniffer doesn't do that, but Iris does

ANA-6911 won't be supported under 2K, the chipset is no longer manufactured.

Be sure that the NIC is in a "Gather Network Statistics" mode, AKA promiscuous. -Andy

Well Sniffer will do that - set a filter to capture all the traffic between the 2 machines and there you have it - you can limit the filter to watch a particular conversation if you'd like. http://www.sniffer.com -Andy

Michael, http://download.nai.com/products/media/sniffer/support/SND/fddi55.pdf Try that =)

Best PCMCIA NIC? EN= Xircom CBE2-100BTX Cardbus NIC TR= Madge Smart Ringnode Cardbus NIC Fibre: Sniffer Optical PoS= Snifferbook Ultra DWDM Sniffer Pro Sniffer Pro LAN Xyratex Gigabit Ethernet PCI Adapter Full Duplex Pod (you'd have to span to a monitor port on a switch) ATMBook from Sniffer...

Aside from ordering the parts from NAI, you can build the cables yourself, customize the length, etc. you can find the pinouts and specs here: http://download.nai.com/products/media/sniffer/support/SND/wannb540.pdf Starting at page 3/17. Here are the part numbers I was able to dig up on the...

OK, I got this right out of the Sniffer Knowledge Center: Error "Failed to create empty document" Error "Unable to connect to remote expert" Starting a capture using DSPro 3.0 Agent Connecting to a DSPro 3.0 Agent Problem Environment: Microsoft Windows NT Microsoft...

DSS/RMON 3.0.10 will run under Windows 2000. Having said that, I still recommend an upgrade to 4.x because unless you get a Sniffer tech who is in a particularly good mood, the 3.x under 2K configuration is not supported. The error you are getting may be a DCOM issue; there could be several...

Elca, Could you send me a trace of the conversation? I can sit down with the trace file and some of the decode guys and see what is happening. Also, please go back over your setup one more time to be sure it isn't a simple matter. I've seen NICs auto-negotiate for 10MB on a 100MB segment...

I found this in the Sniffer support website: Unknown Ethertype decode in WAN Error Message This could be caused by a proprietary Frame Relay header or one that is not supported by Sniffer Pro The "0021" & "0031" Hex values are PPP's LCP values and not Ethertype...

Elca, Yikes! Looks like there are incorrect protocol settings. What topology are you sniffing? Have you configured the sniffer to let it know what traffic type your looking at? -Andy Lail

Simply stated, most of us need to see the BW numbers and know who is using it. Graphs and charts help me explain to my boss what is happening and why, but for real in-depth analysis of what is happening on the link and tool like Sniffer is the right one. I use it to baseline my link, then...