How-To – Find how many connections Outlook makes to your Exchange infrastructure using Netstat.exe

In this quick procedure we leverage TaskList.exe command (default Windows command line utility) to get a specific process name and ID, and the Netstat.exe command (also a default Windows command line utility) to quickly find the opened connections from a specific application.


Note: you can use other tools to get these, like the Windows Task Manager for example to find the process names and IDs, and/or the excellent TCPView from sysinternals to graphically see the opened connections along with process names… or you can use any network analyzer tool (like Microsoft Message Analyzer, Network Monitor, Wireshark, …) or even the Windows Resource Monitor (Resmon.exe)  if you prefer.


When you launch an application like Outlook, it usually opens a process that has a specific ID. We are going to get the ID for the Outlook application, which associated process and then run Netstat to find out how many lines, in other words how many network connections and on which port do we have opened for Outlook.


  • Step 1: Get your Outlook PID using Tasklist


Run the below command:

Tasklist | find /I “outlook.exe”

This command is leveraging MS-DOS TaskList.exe command, and we use the “Find” command after a pipe to just output the line of the whole output that include the “outlook.exe” process.

The output will look like the below:

Fig. 1 - Outlook PID = 4028


  • Step 2 : Get the opened connections by this PID using Netstat:


Run the below command:

netstat-ano -p TCP | find /I “PID_Found_Above”

This command leverages Netstat with the -a -n -o options combined into one -ano parameter, and focussing on the TCP protocol. Then we use the “Find” command after a pipe to just output the line that include our process ID that we found on Step 1.

Fig. 2 – 2 entries, one for Mailbox connection, one for Directory connection


Here I see 2 entries:


TCP                 ESTABLISHED               4028
TCP                 ESTABLISHED               4028


One is for Mailbox connection (download e-mail body and attachments, mark e-mail as read, move and/or delete e-mails, etc...), and the other one is for Directory connection (for address book resolution in Outlook, address book searches, etc…).



When you see 2 entries like the above example that I paste below again:

TCP                 ESTABLISHED               4028
TCP                 ESTABLISHED               4028

This means I have 2 network connections that Outlook is making to my Exchange server. Note that this is the case for MAPI over HTTP, AND when you don’t have any additional mailboxes (shared mailboxes or a mailbox where you have full mailbox access and brought to your profile using auto-mapped mailboxes).

If you are using Outlook Anywhere aka RPC over HTTP (which is deprecated in Office 365’s Exchange Online), we will have an additional connection, as RPC over HTTP needs 2 connections as opposed to MAPI over HTTP: one RPC over HTTP connection for e-mail sending (RPC-OUT : uploading e-mail data from Outlook to Exchange), and one RPC over HTTP connection for e-mail receiving (RPC-IN : downloading e-mail data from Exchange to Outlook) – that way with the Exchange Directory connection, we will have at least 3 connections for an Outlook with a profile that just has one mailbox configured in Online mode).


On Outlook (in Online mode) Connection Status you will find 3 entries:

  • Exchange Directory which session type is Foreground
  • Exchange Mail which session type is Foreground as well
  • And another Exchange Directory which session type is “Background”


Fig.3 – Outlook Connection Status view


The Exchange Directory “Background” is essentially there for the cached entries, but does not account for a network connection. As long as Netstat shows only 2 entries, I guess we can tell the network guys that Outlook / Exchange in MAPI over HTTP mode, without other Public Folder and without additional groups and shared mailboxes, only needs 2 network connections opened between Outlook and Exchange…

 Note: the TCPView tool mentioned above enabled you to get the application name and its opened Network connections a bit faster, here’s an example here:

Fig. 4 - TCPView graphical user friendly interface to achieve the same as the above 2 steps, in one tool



 Remove Automapping for a shared mailbox in Office 365

Microsoft Message Analyzer:

Network Monitor v3.4 (deprecated but still functional)


Comments (2)
  1. troth says:

    Possible a more modern way with powershell

    get-process outlook* | % {Get-NetTCPConnection -OwningProcess $}

    1. SammyKrosoft says:

      Great catch, thanks troth ! I’ll update the article adding this method as well, quoting you of course!

Comments are closed.

Skip to main content