'warrenbuckles' is right here. For me, Wireshark or for that matter any Network Analysis tool can be a big help provided you know what you are looking for. It is similar to Internet where the information is immense but is only useful, when you know what you are looking for. Now, you have not specified what kind of connections are you trying to monitor. TCP is a very wide term. You need to be more specific like SMB is TCP 445, RDP is TCP 3389 and so on. If you are using Custom Application then it will have some specific ports as well. Now, to filter TCP session. First, we need to narrow down the traffic i.e. Wireshark will capture anything and everything which is on the wire which means a lot of garbage packet as well (Broadcasts and all). If you know that traffic is getting disrupted...let's say between two machines then begin with narrowing down the traffic between those two.
I have given some Example Commands for WireShark but like I said, it all depends on what you are trying to look for...or may be, if you can tell me what is the exact issue...I might be able to give you more pointers...
Also, note that the brackets and the Signs (&&, ||, !) play a very important role in the trace.
TC..:)
Main Topics
Browse All Topics





by: warrenbucklesPosted on 2008-02-25 at 06:43:38ID: 20975703
The manual is the place to start, but a familiarity with TCP/IP is also important.
downloads/ details.as px? FamilyI D=18b1d59d -f4d8-4213 -8d17-2f6d de7d7aac&d isplaylang =en) but I don't have as much experience with it as with wireshark - others may favor this approach. Any comments out there?
Wireshark has two modes - live capture and trace analysis.
Both modes have filter capabilities but the filter scripts are different (not great design here).
You can filter on practically anything - IP address, protocol, sub-protocol, host name, etc.
In your case you might want to build a filter that captures a specific IP combination (source and destination) and protocol (SMB? - I'm not sure what you mean by 'losing connection') and look for retransmitted packets, retransmit requests, bad packets (crc or other errors)). Wireshark has a nice coloring scheme for packets that makes it easy to scan a dataset.
If you can repeat the problem on the network you have a better chance of catching it - build a set of snapshots that cover the time period of the errors and try to pull out what they have in common.
I don't have a copy of wireshark running on this box (I'm away from home for another week) and can't give you specific examples - maybe other people on this site can help here.
Microsoft also has a network monitoring package (http://www.microsoft.com/
wb