Securing Exchange Web interface https://Ipaddress/exchange

We are currently utilizing firewall/Router option to open specific ports on our company’s public IP address for accessing Exchange web interface.

So all of the followings are working well:

https://ntserver/exchange (server name)

http://192.168.21.10/exchange  (private)

or

http://67.61.18.12/exchange/   (public)

I am just thinking about the security issues concerning having exchange server web interface on public address. I mean vbscript permission (script sources access/script and executables/ directory access) or any other security best practice in my scenario.

Currently I have everything setup as windows integrated authentication. I am looking for a good advise.

Thanks

Faruqi
sfaruqiAsked:
Who is Participating?
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.

David WilhoitSenior Consultant, ExchangeCommented:
you don't have the exchange interface on a public IP, you simply opened port 443 back to your exchange server. totally different. Set the authentication up as basic, then force the SSL for the Outlook Web Access connection.

http://support.microsoft.com/default.aspx?scid=kb;en-us;279681

D
0

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
JasonBighamCommented:
Setup a certificate and require VPN connections. This can be done for free.
0
sfaruqiAuthor Commented:
Thanks Kidego
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

David WilhoitSenior Consultant, ExchangeCommented:
you got it, check the other question as well, I think you can go a different way with it. :)


D
0
sfaruqiAuthor Commented:
>>you don't have the exchange interface on a public IP, you simply opened port 443 back to your exchange server. totally different.

If you can explain this to me. Port 443? is it for SSL  https://. Because I have open port 80 in Routing tabel (Public IP Address  translate to my NTserver Address 192.168.39.10)

Thanks
0
David WilhoitSenior Consultant, ExchangeCommented:
yes, you're on track, 443 is SSL. Open 443 if you haven't already, cause that's it's natural port. SSL from the outside won't work unless you specify the connection trhu your firewall.

d
0
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
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.