To start using TCP Problem Finder, simply import a Wireshark trace ..

NetConfig
The first thing TCP Problem Finder will do is to deduce the configuration. This can tell you what devices are active on the network you are working on, the IP address of the router, or if you are on a VLAN. It can also tell you what kind of devices they are. When you are diagnosing a problem, it helps to know if the device having problems is a desktop, a phone, a printer, even a TV.

Next, TCP Problem Finder will resolve the IP addresses and geolocate them. This can tell you what sites and locations you are going to. If you find that you have a response time problem, it may be because the server is located in another country!
ResolvedAddressesSmall

ErrorsByDomain
Now, the fun really starts! TCP Problem Finder will:

  • Identify congestion or network traffic errors on subnets,
  • Identify TCP configuration errors,
  • Identify misconfigured network devices (window size, max segment size, DNS, etc),
  • Identify routes and applications with packet fragmentation,
  • Identify excessive idle or hanging connections, and many other errors!

And, it will provide them to you by domain name and location!


Of course, TCP Problem Finder will give you lots of recommendations on what is going wrong
Recommendation

DupSegs
Then, TCP Problem Finder do a detailed analysis of throughput (bytes in flight), duplicate segments, duplicate acks, hangs, resets, segmentation offload, and much more!

These are all the things that you would have to do on your own when analyzing a trace. Just think of how much time and effort can be saved by TCP Problem Finder!