Link to home
Start Free TrialLog in
Avatar of SpeedRacer1972
SpeedRacer1972

asked on

Exchange 2007 OWA not working externally

I just installed an addtional Exchange server in my Exchange Org. The Org started out as 2003 but I have added a 2007 server that has the CAS, HUB and Mailbox roles running on a 2008 server. All is working except OWA externally. while I know i have not install the web cert on this box as of yet, i would think that OWA should still work. From an external client I goto the web address of the OWA server, i get the cert warning, i click continue and then get the following message:

The URL you requested has been blocked. URL = invalid.

I know the my firewall is configured corectly as I am getting email on port 25, i can RDP in on port 3389 and i get the cert warning page, all of which are on the same box.  I have made sure that the interal and external address is the correct within Exchange Management console for Server config and client access.

any help would be greatly apprecaited.
ASKER CERTIFIED SOLUTION
Avatar of kollenh
kollenh
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of SpeedRacer1972
SpeedRacer1972

ASKER

I can get to the OWA internally, just not externally. I am only forwarding 25, 443, 3389 on the firewall. The URLs for internal and external are set to be the same in ESM. I guess i do not know IIS on Server 2008 well enough to check if they match. I have looked in all places i can find and have no luck. i assume the setting i am looking for would be under sites\Default Web Site\OWA.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
the internal and external URLs are both set to the external DNS names, which is what my MX record is pointing to. I am able to test from my home network, hitting the OWA address. hitting the IP address does the same thing.  

I would think that if it were a firewall issue, using a Fortinet WiFi 60B, them RDP or SMTP would not work which are all forwarding in the same firewall rule to the same IP.
so i decided to take a harder look at my firewall. As it turns out Fortinet considers the actual address of my OWA server as in valid. I had a check box to block invalid URLs, as soon as i unchecked that the started working. Thank you for the help
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
yes, i plan on settting up Outlook anywhere and a cert, i just wanted to get OWA working before i took any anything new.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial