How to run WireShark
A brief tutorial on how to run WireShark.
Last updated
A brief tutorial on how to run WireShark.
Last updated
WireShark is a helpful tool for capturing network traffic in real-time. It helps us identify and diagnose issues more clearly, such as which ports are causing problems or analyzing data packets, including their source, destination, protocol, and content. We have put together an easy tutorial on how to use WireShark, let's begin!
In the majority of cases, you will only need to use this tool when having issues connecting to your server through RDP.
Go to the WireShark website and click "Download" on the top navigation bar.
Locate the "Stable Releases: 4.4.2" list and select Windows x64 Installer.
Open the .exe file.
A prompt will appear asking if you would like WireShark to make changes to your device, simply click "Yes".
The installer .exe will open, click "Next", read through their TOS and select "Noted", then continue to click "Next" until you are presented with "Install", click it then wait for the program to install.
Click "Next" then "Finish"
You have now installed WireShark, now how do you use it?
Open the program
A prompt will open for admin-mode, always click "Yes".
You will be presented with the following:
In the filter textbox, write: host [your server IPv4 address]
Proceed to double-click the network connection you are using [typically Wifi if you are not using an ethernet cable].
A new window will open for the recorder that is capturing the network traffic.
After this step with the recorder open, attempt the task that is causing problems.
If it is connecting to your server, attempt to connect through RDP.
After you have attempted the task that is causing problems, like attempting to connect to your server through RDP, allow about 5 seconds, and then click the red square "Stop" button on the top left corner.
Click "File" and "Save as", name the file and click "Save".
Send us the saved .pcapng file in your Discord ticket.
You can now open the file and view the network traffic, protocols that were run, and their sources and destinations.
Problems will be identified and highlighted in red for when a protocol fails, this is what we are looking for to resolve!
