When looking for which ports Exchange 2010 uses, you probably already read the excellent Exchange 2010 Network Port Reference TechNet article located here.
However, at some point, like when discussing things with the network/firewall people or documenting your design, it might be required to visualize things. For this purpose I created the following diagram:
Note that it’s a v1 and not all things are included, e.g.
- Internal clients, e.g. Outlook, OWA;
- UM connections to PBX;
- Client Access Server connections to OCS;
- For Hub-Hub, CAS-CAS or Edge-Edge, I’ve included a 2nd Hub/CAS/Edge server only mentioning ports used for Hub-Hub, CAS-CAS and Edge-Edge communications.
Also, all ports are left at their default values and the diagram doesn’t reflect the fact that you can fix certain ports like the one for the DAG or the MAPI RPC port; that might be added in a later version.
When you got feedback, fill in a comment. Otherwise, feel free the use it; crediting or a reference would be nice.
EighTwOne (821) 
Great diagram! Would it be possible to also publish this as a PDF file?
Thanks,
Yogesh
LikeLike
Yes, but first I’ll process initial feedback and add client elements.
LikeLike
Nice work Michel.
This is a helpfull peace of work.
LikeLike
Pingback: EighTwOne (821) « JC’s Blog-O-Gibberish
Great post Michel, I appreciate the effort that has gone into this.
Will really help during design process and will be good to also see the addition of UM ports for PBX
LikeLike
UM to PBX ports will be added in an update
LikeLike
Very nice. Thanks for sharing!
LikeLike
Pingback: Exchange 2010 Network Ports « Rodrigo Rodrigues .:. www.andersonpatricio.org
Pingback: Some 2010 Statistics « EighTwOne (821)
I love it. Thanks a lot Michel.
LikeLike
Very nice! Do you have the diagram that includes Outlook clients to the CAS as well?
Thank you again.
LikeLike
Not yet, will work on full blown diagram asap.
LikeLike
Pingback: Exchange 2010 SP1 Network Ports Diagram v0.31 « EighTwOne (821)
The arrows to/from the DC and mailbox show as two way for protocol communication I’m guessing that this was just a slight oversight? Also, I’m making a tabular spreadsheet of all the protocol communication requirements for a exchange 2010 environment. I’ll use this table as the data for a script which will take all the servers in an environment and spit out firewall requests for companies with an international or highly segmented network. Would you be so kind as to review the excel sheet I come up with for additions/mistakes and your professional insight?
LikeLike
Oversight? No. There’s two-way traffic, e.g.
* Email Address Policy addresses stamping on AD objects;
* Failover Cluster updating its record in DNS.
Reviewing, sure. Nice idea btw; always nice to semi-automate those RFC requests 🙂
LikeLike
Good point! Thanks for the clarification. I’ll update my list and shoot it out to you soon.
Thanks!
LikeLike
Do you have a link to the updated diagram?
Thanks!
LikeLike
LikeLike
Port 443 from outside to CAS?
LikeLike
Directly (unlikely) or indirectly – e.g. through reverse proxy – yes.
LikeLike
Pingback: Exchange 2010 Ports | Messaging and Unified Communications
Michel, would you happen to have an update to your ports diagram for Exchange 2013?
LikeLike
No and if there will be one it will be low priority as MS advocates unfiltered traffic between Exchange 2013 nodes.
http://blogs.technet.com/b/exchange/archive/2013/02/18/exchange-firewalls-and-support-oh-my.aspx
I might do one regardless, as many network people still want to know (or chart) port usage (not to restrict traffic)
LikeLike
Diagram is good but need some improvement as remote site server port?
LikeLike
Rest is good.
LikeLike
Thanks.
LikeLike