Home NewsX How to Capture Simultaneous Wireshark Traces from Client and Server for Network Troubleshooting

How to Capture Simultaneous Wireshark Traces from Client and Server for Network Troubleshooting

by info.odysseyx@gmail.com
0 comment 1 views


introduction:

I have seen clients troubleshoot issues with their IIS hosted applications on their networks. Often in network troubleshooting, you need to capture packets from both the client and the server to fully understand what is happening during the communication. Wireshark, an essential tool for network analysis, can help with this, but capturing from both sides simultaneously requires careful planning. This approach provides a complete view of the communication and helps identify the problem more effectively.

In this blog, we will walk through the process of capturing Wireshark traces simultaneously on both client and server sides, providing a clearer picture of network flows and potential issues.

Should we start with Wireshark?:

Wireshark is a free, open source network capture and network analysis tool that is widely used worldwide. It is not installed by default on any operating system, so customers must download and install it on their devices. Here’s what you need to use it for:

  1. Tools on the official website Wireshark · Download
  2. Administrator access to both clients and servers

Now we will capture the traces.

  1. Launch Wireshark. On your Windows computer, open the Start menu and type: Wireshark Right-click on Wireshark in the search box and select Run as administrator
  2. Wireshark captures traffic from all network adapters and network interface cards, but you can isolate one to capture using the capture menu that appears when Wireshark opens. A line next to the interface name indicates whether traffic is currently flowing through the interface, which can help you choose if necessary.

pradeepsharma_0-1726308867292.png

  1. Select from the toolbar menu capture -> startAlternatively, you can select the blue shark fin button to start a network capture.

pradeepsharma_1-1726308867315.png

  1. Set this on both client and server now. Reproduce the problem If you want to investigate, packet details will scroll through while the capture is running.
  2. After reproducing the problem, from the toolbar menu, select: capture -> haltAlternatively, you can stop tracking by clicking the red square button.

pradeepsharma_2-1726308867395.png

  1. Select from the toolbar menu file -> Save as. In the Save As dialog box, you can save the trace in the default Wireshark trace format, *.pcapng, or change it to: Save as type With drop down menu Microsoft Netmon 2.x Then save the trace as *.cap so that you can open it using Netmon.

pradeepsharma_3-1726308867403.png

Now you have a troubleshooting log ready for comprehensive review.





Source link

You may also like

Leave a Comment

Our Company

Welcome to OdysseyX, your one-stop destination for the latest news and opportunities across various domains.

Newsletter

Subscribe my Newsletter for new blog posts, tips & new photos. Let's stay updated!

Laest News

@2024 – All Right Reserved. Designed and Developed by OdysseyX