Opening ports for Exchange 2010 in firewall
10,644
Depends how you're connecting to the Exchange.
http://technet.microsoft.com/en-us/library/bb331973%28EXCHG.140%29.aspx
Related videos on Youtube
Author by
Frederik
Experienced in Cisco routing/switching, Mikrotik routers, Windows Server 2008-2016, Debian/CentOS Linux, puppet and a whole lot more Programming experience includes PHP, C#.NET and I've been touching most other languages more or less
Updated on September 18, 2022Comments
-
Frederik over 1 year
I have setup an Exchange 2010 SP2 server, which works absolutely fine.
However, sometimes the Outlook client won't connect. Looking with TCPView, I can see that it is trying to access ports that haven't been opened. The weird thing is, that it worked fine a few weeks earlier.
So, are there any dynamic port range that Exchange uses? I noticed the ports were something like 48031, 48103.
-
EEAA over 11 yearsThose would be ports that the client is connecting from, not ports the client is connecting to.
-
Frederik over 11 years@ErikA Might be that you say so, but opening these ports in the firewall on the exchange site fixed any exchange/outlook related issues we had.
-
-
Frederik over 11 yearsI have already been all over that article, and opened more or less all of those ports. However, I cannot seem to find the ports specified in the original post: 48031,48103.
-
Vick Vega over 11 yearsBecause they're not needed, because those are dynamic ports, next time you restart your Exchange server, it will change. Please describe the way how your users are connecting to the Exchange server.
-
Frederik over 11 yearsThey start up their outlook, inserts their name, email and password, autodiscover figures the rest of the settings, and they got email.
-
Vick Vega over 11 yearsIf this is the case, the only port you need is 443. (HTTPS) I would suggest validating all the settings are properly configured for Autodiscover. testexchangeconnectivity.com
-
Frederik over 11 yearsUsing testexchangeconnectivity gives me all green lights - except for the RPC/HTTP test, which tells me that it gives 404 on rpcproxy.dll
-
Frederik over 11 yearsI figured out that the RPC over HTTP Proxy was the problem, as it wasn't installed at all. Now testexchangeconnectivity gives me all green lights :-)