Traditionally, no. Exchange had several RPC-based services that used wide port ranges.
In Exchange 2013, the situation is different. All Exchange-RPC is local RPC, but that doesn’t affect the RPC that is required between servers and AD or RPC for remote management, etc. etc. Dealing with swiss-cheese firewalls was a top support challenge for escalation engineers for very little benefit. So it’s no longer supported. From: Richard Stovall [mailto:[email protected]] Sent: Thursday, May 2, 2013 9:13 PM To: MS-Exchange Admin Issues Subject: Re: Exchange 2013 Port Reference? You know, shoot me if I'm out of line here, but I couldn't help but read this thread and think: netstat -abon Wouldn't that at least help you discern from the ground what is going on? (That said, the original request for a port reference document seems extremely reasonable. The fact that one will not be made available is, well, bizarre.) --- To manage subscriptions click here: or send an email to with the body: unsubscribe exchangelist
