Watchguard Firebox not allwoing access to OWA, and send/recieve mail

[fenderjbass]

I have an old firebox 750e we got when we replaced a clients firewall. Its running an older v10 os. We're working more with exchange now, and I set it up for our office. Externally everything works great. I can send and receive mail though outlook, and access OWA. I can't get it to work with my droid based phone, but that could be a different issue. Anyways, internally I can't access owa via it's public domain name, and I've been told we also can't send or receive mail. Internally, i can ping its domain name ex: mail.mydomain.com. So I don't think this is a DNS issue. Though when I open up a browser, both ie and firefox, it says website can't be found. I am using https ex:

https://mail.mydomain.com/owa.

I did some research on this issue, and I found it could possible be the firewall. I know I've had this issue with a cisco firewall at one time. A way around it was to create a zone record in DNS. Which I tried as well. The funny thing is, I set up a test exchange server at home. I used my own domain name, and I had no problems at all internally or externally, and connecting my phone to exchange via active sync. At home a I have an asus, with DD-WRT. I've also set up exchange server for another client, using a watchguard firewall. That was a firebox edge x with 11.0 os. So could this be an issue with older OS?

 

[tpit]

You need to make an internal NAT policy changing your public IP to a local IP. This is normal behaviour, as your clients resolve your OWA server to be public, this will also route it as public and therefor not set up legitimate TCP/IP sessions.

I can help you set it up. Just contact me through tektips.

Regards,
Tommie

_________________________________
It works! But how?
VoiceByte System Engineer