Save 10%Pay yearly on any plan. 6% half-yearly, 3% quarterly. Help centreWhatsAppTelegram TeamsOpen a ticket

How to Monitor All Network Traffic in Windows

Six ways to see every incoming and outgoing connection in Windows 10, 11 and Windows Server, from Task Manager to netstat, PowerShell and packet capture.

3 min readBy Soumya

Reviewed by the AmazingRDP technical team

Monitoring network traffic in Windows

Need a Windows server you can watch and control yourself? A Windows VPS gives you full administrator access. See Windows VPS from $8.99

Windows can show you every connection your computer or server makes, without installing anything. This guide goes from the quickest look to a full packet capture. The steps work on Windows 10, Windows 11 and Windows Server 2016 to 2022.

Which tool for which question

You want to knowUse
Which app is using the network right nowTask Manager
Which addresses and ports each program talks toResource Monitor
A list of every open connection and listening portnetstat or PowerShell
What the firewall allowed or blocked over timeWindows Defender Firewall log
The packets themselvesPacket Monitor (pktmon) or Wireshark

1. Task Manager: which app is using the network

  1. Press Ctrl + Shift + Esc.
  2. On the Processes tab, click the Network column to sort by use.
  3. On the Performance tab, choose Ethernet or Wi-Fi for a live graph of send and receive speed.

This answers "what is using my connection" in seconds. It does not show where the data goes.

2. Resource Monitor: addresses and ports per program

  1. Press Win + R, type resmon and press Enter.
  2. Open the Network tab.
  3. Tick a program under Processes with Network Activity to filter the other lists to that program.

Network Activity shows the addresses a program is exchanging data with. TCP Connections shows local and remote ports and the delay of each connection. Listening Ports shows which programs are waiting for incoming connections, and whether the firewall allows them.

3. netstat: every connection and listening port

Open Command Prompt as administrator and run:

netstat -ano

-a lists all connections and listening ports, -n shows numbers instead of names, and -o adds the ID of the process that owns each one. To see the program name as well (administrator only, and slower):

netstat -anob

To look at one port, filter the output. This shows everything on port 3389, the Remote Desktop port:

netstat -ano | findstr :3389

To turn a process ID into a program name:

tasklist /fi "PID eq 1234"

4. PowerShell: connections with program names

PowerShell gives the same information in a form you can sort and filter. This lists established connections with the name of the program behind each:

Get-NetTCPConnection -State Established |
  Select-Object LocalPort, RemoteAddress, RemotePort,
    @{n="Process";e={(Get-Process -Id $_.OwningProcess).ProcessName}} |
  Sort-Object Process

And this lists the ports your machine is listening on:

Get-NetTCPConnection -State Listen | Sort-Object LocalPort

5. Firewall log: what was allowed and what was blocked

The firewall can keep a record of connections over time, which is what you need for a security check.

  1. Press Win + R, type wf.msc and press Enter.
  2. Right-click Windows Defender Firewall with Advanced Security and choose Properties.
  3. On the tab of the profile in use (Domain, Private or Public), click Customize under Logging.
  4. Set Log dropped packets and, if you want them, Log successful connections to Yes.

The log is written to %systemroot%\System32\LogFiles\Firewall\pfirewall.log. Each line has the time, the action (ALLOW or DROP), the protocol, both addresses and both ports. Logging successful connections fills the file quickly on a busy server, so raise the size limit or switch it off when you are done.

6. Packet capture: pktmon and Wireshark

When you need the packets themselves, Windows has a capture tool built in: Packet Monitor. On Windows 10 version 2004 or later, Windows 11 and Windows Server 2022, run these as administrator:

pktmon start --capture
pktmon stop
pktmon etl2pcap PktMon.etl

The first command starts the capture, the second stops it and writes PktMon.etl to the current folder, and the third converts it to a pcapng file. Older builds use other option names; run pktmon help to see the ones your version has.

Open the pcapng file in Wireshark, a free analyser from wireshark.org, to read each packet and filter by address, port or protocol. Wireshark can also capture by itself. For a live list of connections in a window, Microsoft's free TCPView (part of Sysinternals) is a good middle step between Resource Monitor and a full capture.

Monitoring a remote server

All six methods work inside a Remote Desktop session. One thing to remember on a server: your own RDP session is a connection too, so expect to see port 3389 in every list. If you are new to connecting, see how to connect to RDP from a desktop. On a shared RDP you have no administrator rights, so only Task Manager and Resource Monitor are open to you; the other tools need an admin RDP or a Windows VPS.

Questions

How do I see all network connections in Windows?

Run netstat -ano in Command Prompt, or open Resource Monitor (resmon) and look at the Network tab.

How do I find which program is using a port?

Run netstat -ano | findstr :PORT, note the process ID in the last column, then run tasklist /fi "PID eq ID".

Does Windows have a built-in packet sniffer?

Yes. Packet Monitor (pktmon) is included in Windows 10 from version 1809, Windows 11 and Windows Server 2019 and later.

Do I need administrator rights?

For netstat -b, the firewall log and packet capture, yes. Task Manager and Resource Monitor work for any user.