About TDC

Hi bulent and achitwadgi Thanks for the replys. Sorry for not replying sooner but its been a long weekend. Yes, I chose Outlook-web, SSL and Web-Browsing. All traffic gets seen as SSL to port 443. I'm not using a certificate at the moment and yes the traffic gets seen going to the FQDN of the server (thanks for the info on the pulling of the CN from the cert) so I'll look at adding SSL decryption to pop open the traffic and see if that helps. I noticed that the logs generated indicated that the URL being seen is the FQDN of the server without the '/ecp' or '/owa/' so the path seems to being dropped or ignored on the request. In my custom URL filter I include the path so when I look the logs the URL is listed as 'unknown'. When I removed the path from the URL in the custom filter it gets clasified correctly as the custom URL. I'll continue to look at the SSL decryption and how that will help but if anyones got any ideas why the paths are being ignored I'd love to here them. Cheers for all the support. Alan ... View more

Correct. The one think that the firewall won't do is 'publish' OWA in the sense that ISA does (its not a reverse proxy in that sense). However, with the SSL cert the firewall can decrypt the data as it passes by to ensure there are no hidden nasties. Also with what Kelly mentioned, you can control what web sites are being hit to ensure only the ones you want to publish (again not in the ISA sense) are the only ones available - still trying to get the fine control working. I will admit, I still get a warm fuzzy feeling publishing OWA/OMA via ISA as its not exposing the Exchange server directly to the big bad web but then again its using ISA and comparing that to our PA-500 its obvious the Pa-500 is in a different league.... Cheers Alan ... View more

Hi sdurga Many thanks for taking the time to test this out. I'm contacting our Premium Support partner now. Cheers Alan ... View more