OWA

[Pauline]

Does leaving port 135 open cause security issues? I was
told that we would need to install VPN to have system
secure with OWA, is that true? What about SSL?

 

[Ryan M. Keith [MSFT]]

Pauline,

Port 135 being open to the Internet is not a good thing. To provide
Outlook connectivity with port 135 closed, do the following. Upgrade to
Outlook 2003, and used RPC over HTTP. Setup a VPN solution for your
clients without Outlook 2003. Setup OWA with SSL for your "on the road"
users. Here are some resources on this subject.

Securing Exchange Communications:
https://www.microsoft.com/technet/treeview/default.asp?url=/technet/security
/prodtech/mailexch/opsguide/e2ksec04.asp

Exchange 2003 Security Enhancements
http://www.microsoft.com/exchange/evaluation/security_e2k3.asp

Security Resources for Exchange
http://www.microsoft.com/exchange/techinfo/security/default.asp

Exchange 2000 Security Guide Chapter Download
http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=d286
e9a7-fe36-4a02-a0f8-75d4f9eb8d2d

Webcase on securing Exchange 2000 environment
http://www.microsoft.com/seminar/shared/asp/view.asp?url=/seminar/en/2002091
8tnt1-56/manifest.xml

Help Secure E-mail Servers with ISA 2000
http://www.microsoft.com/isaserver/featurepack1/email.asp

Help Secure Outlook Web Access with ISA 2000
http://www.microsoft.com/isaserver/featurepack1/webandowa.asp

Security Design Principles
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itsolutio
ns/idc/rag/ragc05.asp

Step by Step Security How-to resources
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/
topics/hardsys/TCG/TCGCH00.asp

Best Regards,

Ryan M. Keith, BSCSE, MCSE
Microsoft Enterprise Messaging Support
Client Server Infrastructure

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
--------------------