tshinder
Posts: 47490
Joined: 10.Jan.2001
From: Texas
Status: offline
|
quote:
ORIGINAL: yba Dear Tom, Once again, thank you for your support and thank you for your prompt reply. It works. I have not implemented SSL but it works, internally and externally. Amazingly, to me of course, the only thing that I had to change was the port on the listener and the bridging (no HOSTS modification on ISA box.) It refused to work on port 80 (the same return as in my previous message.) But, when I used port 81 instead, it worked perfectly. Now, step two (I pray that there are no sniffers installed on any part of my network) is to enforce security. If I clearly understood your article, I have two reservations: 1 - We need to modify the HOSTS file on the client machine, which might be a PC in a hotel's business center, and 2 - We must install the same certificate on the client machine (this is why I believe we published the enrolment site), which, again, might be a PC in a hotel's business center. If that's right, then the only practical way of using secure OWA is from one's own laptop, which will be no hassel making these two preparation steps. The reason for this debate is to ask you for a short-cut so to enforce security for road warriors with minimal hassel on third party PC's. Besides, does FBA provide any sort of encryption or I may have to abandon external OWA till security is enforced? And before I forget, thank you once more. Regards Yba P. S. I have a trial version on Exchange 2k3 SP1. Do you know why only the first three users to use OWA are internally (I have not tried it externally) allowed access? Everyone else is denied access. Hi YBA, No, none of this is true. You do not need to manipulate the HOSTS file on the client. Read the article again, you'll see that we use a HOSTS file only because in the lab envirnonment, we have not yet deployed the public DNS entries. You'll see that I state that you need to implement your public DNS entries before the clients can connect. Also, you do not install a server certificate on the clients. You need to install the CA certificate on the clients, which is standard practice for any PKI deployment. If you don't want to do this, you can install a commercial Web site certificate on the ISA firewall instead of creating your own, however, its pretty simple to allow users to get the CA certificate. You can use autoenrollment too, on your managed machines. HTH, Tom
_____________________________
Thomas W Shinder, M.D. Sr. Consultant/Technical Writer Prowess Consulting http://www.prowessconsulting.com/ Blog: http://blogs.isaserver.org/shinder/ GET THE NEW ISA 2006 Book!: http://tinyurl.com/2gpoo8
|