Sorry if this has been asked an answered, but I didn't know the correct terminology to search on. Our network is setup so that ports 25 & 110 are forwarded at the firewall to the IP of theexchange server and ports 80 and 443 are forwarded to our dedicated web server. Outlook works fine both internally (Exchange connection) and externally (POP3). OWA works fine internally (using the local FQDN). Is there any way possible to have the web server access the mailboxes on the exchange server?Do I create a virtual directory (or whatever) on the web server and have it point to a share on the exchange server (I know the share for OWA on the exchange serveris something like ./BackOfficeStorage). Or will I need to install an Exchange component on the web server to make this happen. TIA!

Hiya chap, from the description that you have given it sounds as if your "Web Server" is just that - e.g. is not running the CAS server role. You have a couple of options open to you: 1. Place an ISA server in between your Firewall and Web + Exchange Client Access Server - point port 80 & 443 traffic at the ISA server and then publish your web server and client access server via the ISA server - this would beyour best option. 2.If you firewall supports multiple IP addresses on the external Interface - configure a new external IP address,point the URL in DNS for OWA at the new external address and then NAT the 443 traffic to your CAS server. Cheers A

Yes, the web server is just that....handles web traffic. Currently it has no other roles assigned to it. 1.) I haven't used ISA server before, so I'm not sure how much would go into the configuration to make it work. 2.) AFAIK the router only supports 1 IP on the external interface. You mentioned CAS. What exactly is that? We only have 1 Exchange server and it's using the default installation/configuration.

Hiya chap, one of the Roles on you Exchange 2007 server is called the CAS (Client Access Server) - this is the johnny that serves up OWA (amongst other things). Do you have the option of installing ISA? considering the description of your configration it sounds like a good option I can provide a number of links that wouldhelpyouchoose either "yes or no". Cheers A

Yes, I do have the option to install ISA. Any help you could provide is greatly appreciated.

Hiya chap; You would be looking at forwarding all 80 and 443 trafffic to the DMZ address of the ISA server (when installed) - then via publishing rules and DNS FQDN's the ISA server will decide where to route traffic via its private address- the following should help; http://technet.microsoft.com/en-us/library/aa998036(EXCHG.80).aspx- ISA with Exchange 2007 - look to the bottom for CAS configurations http://www.isaserver.org/tutorials/ISA-2006-Firewall-Web-Publishing-Rules.html- ISA web publishing rules in fact - www.isaserver.org is the place to go for great stuff with ISA There are loads of other bits and bobs that can be found via Google ISA 2006 sounds complicated but if you can play around with it in a Test Lab it can be picked up pretty quickly. Hope the above helps,A

Come to find out we were/are not hosting any HTTPS sites on the dedicated web server. So I just forwarded 443 traffic to the exchange server and the issue is now taken care of. Although the solution provided may assist someone else down the road. Thx!!!!