Exchange Server Forums

Static Mapi Port Mappings

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Secure Messaging >> Static Mapi Port Mappings

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Static Mapi Port Mappings - 22.Jan.2008 12:40:40 AM

jd@itsmail.ca

Posts: 1
Joined: 22.Jan.2008
Status: offline

I have a client that wants to lock down their Exchange envioronment, its a fairly simple environment, just one multirole server. They have a Cisco VPN solution, they want to create an ACL on the VPN limiting access to only the internal IP of the Exchange server when using that profile, then lock down the ports a user can communicate to the server with.

There is a microsoft article and typically you would lock RPC135 and 2 other ports on the firewall and hard code the server to talk mapi on them. Internally to the environment it would make no differnence to client access as its fully open.

http://support.microsoft.com/kb/270836

They had this setup with their Exchange 2003 server and it worked fine. The article above, if you scroll down the list you will see an exchange 2007 section but its a bit vague, from what it states you follow the same procedure. Im a bit leery of just doing this, has anyone tried this scenario in e2k7?

Any help/ideas?

_____________________________

JD-