Product Support
Product Activation FAQs
Downloads
Maintenance Programs
White Papers
WildPackets Forums
Technical Compendium
Additional Resources
Tip of the Month
Wireless Tips
Plugin Tips
Product Versions
Networking Books
Networking Glossary
Networking Links
Tech Support Requests
Home > Support > Additional Resources > Tip of the Month

Tip of the Month

Network Analysis Tip of the Month – July 2005

Getting the Expert Back on Track

Author – Fred Phillips

Usually the Expert is very good at figuring out which node is the client and which node is the server, but there are some situations when it can become confused, and can lead to messages from the Expert reporting false alarms such as "Slow Server Response Time". This usually occurs when a capture is started when a conversation is already in progress on the wire, and non-standard port numbers are in use.

There is a simple fix for this that can get the Expert back on track:

  • From the Expert screen, select the nodes that are being confused and right click on them.
  • Choose "Insert into name table" and use the pull down menu to force one node to Workstation and the other to Server.
  • Remember, the Expert only recalculates if the buffer is changed, so to force a recalculation: Right click on the conversation, choose "Select Related Packets/By Flow (or conversation). Then choose "Hide Unselected Packets".
  • The Expert will now reverse the nodes and all calculations about server response times will be correct.

 

Download a demo of OmniPeek
Custom Integration & Engineering
WildPackets understands that one size does not fit all. Moreover, we all face new challenges every day. WildPackets Custom Engineering performs software development and systems integration, complementing WildPackets products and enhancing the capabilities of Network Operations Centers.
Learn more...

Network Analysis & Consulting
WildPackets offers a full spectrum of professional services, available remote and on-site. Our network engineers provide expertise for your network troubleshooting, capacity planning, or baseline performance analysis needs.
Learn more...

Tip of the Month
Don’t Lose The Tags
WildPackets’ Technical Support Team regularly receives questions about capturing VLAN (Virtual LAN) tags in packets. Some customers report that they cannot see VLAN tags when capturing packets from their switches. The tags are usually missing because the capture configuration or the location of OmniPeek (or Omni Engine) is incorrect. So, this tip is aimed at understanding VLAN tags and how they can be captured using OmniPeek Product Family.