balinton
asked on
External OWA Access
Hi I just setup my exchange server and am able to send and recieve mail fine. I am running Exchange 2007 SP1 and Windows Server 2008 with IIS7. I am having trouble getting the external URL for owa to work. I am using a dynamic DNS service and have added the A record for the URL and entered it into the external url property in exchange but no luck. Any help with this would be greatly appreciated.
ASKER
hmm... havent done that... I dont have ISA setup so i would use my ASA Device 5505. Would you be able to explain how to do that?
So did you setup the A record on your external DNS server? The one hosting your domain? Did you forward ports 80 and 443 to your server on the pix? Did you configure your pix to allow these ports?
If you need help with the syntax, I just posted it on another question:
https://www.experts-exchange.com/questions/24014443/How-to-Publish-OWA-using-ASA-5505.html
This assumes that you have OWA working. Can you confirm that it is working internally?
If you need help with the syntax, I just posted it on another question:
https://www.experts-exchange.com/questions/24014443/How-to-Publish-OWA-using-ASA-5505.html
This assumes that you have OWA working. Can you confirm that it is working internally?
ASKER
owa internal is working i am using a dynamic dns service and it is pulling my dynamic ip address which i have assigned differnent A records to on the external dns service. It is using only one IP address for all. After adding those ASA commands i am able to access remotely although instead of going to the OWA website it redirects me to the asa ssl vpn i have setup...
The first command did fail stating that i have to use the interface command when using NAT? I didnt understand?
The first command did fail stating that i have to use the interface command when using NAT? I didnt understand?
Oh, so you have an SSL VPN on the same IP address? And it is a web interface? In this case, you will need to do PAT, or port address translation. You can redirect traffic from the outside port 444 to the internal port 443, for example. You would then access it by going to https://yourdomain.com:444/owa. Change the first 443 to 444 in that first line, then again in the second line. This assumes that 444 is not in use by anything else.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ISA or ASA etc ???