Ports for Activesync?

I need to allow iphones to connect to Exchange 2013 via wifi.  Assuming i was starting with every port locked down, what kind of ports would i have to enable to make this work?  DNS, DHCP, SMTP, HTTP, HTTPS, anything else?  Thanks.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Nothing other than port 80 and 443 actually. https://technet.microsoft.com/en-us/library/bb331973(v=exchg.150).aspx

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
LB1234Author Commented:
Kim, not 587?  I'm using the exchange mail applet built into the iphone.
No, 587 is authenticated SMTP, which is meant for iPhones to send out email in a REGULAR mail client (pop/imap).
If you add a proper EXCHANGE account (which you just stated you will use), ALL DATA travels over the same protocol, including sending mails (your now really SENDING mails, you're just TELLING the server to send the mail, and you are already having a conversation at ActiveSync level, which means you don't need SMTP to send emails).
Dean CollinsCommented:
Doesn't that mean you are opening up your LAN to all kinds of https traffic?

Eg why doesn't activesync use a different port than 443?
In newer Exchange versions, all data passes port 80 and 443, whether you use Outlook locally, or Activesync on a mobile somewhere outside. Since this is a conscious design by Microsoft, I don't think you can hack your way around it, and even if you did, the client wouldn't understand it anymore.

It doesn't mean you open op your LAN to all kinds of HTTPS traffic, if you use the correct rules, (specify correct port numbers, source/target IP numbers etc).
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.