owa setup, what did i forget

Tags:
Microsoft Exchange
just upgraded from 5.5 to 2003, now im in the process of setting up owa. i've had my isp setup to send all http and ssl request to the public ip address, and setup my firewall to send all request from that public address to the email server inside. internally it works if i just type http://server/exchange the outside should work with webmail.domain.org i have mail.domain.org sending to a spam filter. am i missing something? i set this up on a 2000 server a few years ago just cant remember what i did.
1

Answer Wiki

Thanks. We'll let you know when a new response is added.

When you type http://???.???.???.???/exchange do you get to the OWA? “???” is your ip address? If you do get to it it sounds like a DNS problem.

Discuss This Question: 8  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Chrisbf
    no i dont get owa. i just get page cannot be displayed. would that a firewall issue then?
    0 pointsBadges:
    report
  • I730Guru
    As long as you have port 80 forwarding to your exchange server, there shouldn't be any problems with the router. How do you have it setup? JC
    0 pointsBadges:
    report
  • Marcola
    My questions are: 1. "Are you running a single Exchange server?" 2. "When you try to hit the Excahnge server from outside do you get an authentication prompt?" 3. "Are you running Exchange and OWA on the same box?" Tips: 1. If you have port 80 in your firewall/router open for your exchange server then you do not have a firewall issue. 2. Authentication has to be HTTPS on the front-end and Anonymous on the back-end since the front end handles all SSL encryption. -Marcola
    0 pointsBadges:
    report
  • Chrisbf
    1. "Are you running a single Exchange server?" yes just one exchange server 2. "When you try to hit the Excahnge server from outside do you get an authentication prompt?" no just get a "this page canot be displayed" 3. "Are you running Exchange and OWA on the same box?" trying to. i've been doing some reading and everything i read about owa 2003 says something about front end and back end server... is that required?
    0 pointsBadges:
    report
  • Marcola
    NO ... Front-end / Back-end is not required but it does make your setup a ton easier and safer. The only extra work and expense is having another box with the pricy Exchange sitting on it doing nothing but bridgehead work and routing. You will need to look at this excellent link on Exchange.org http://www.msexchange.org/tutorials/OWA_Exchange_Server_2003.html
    0 pointsBadges:
    report
  • PhilReed
    Make sure that you can resolve the external name "webmail.domain.org" from outside - if not then you need to add it to the external DNS (I presume run by your ISP). Try https://webmail.domain.org as SSL is being forwarded.
    0 pointsBadges:
    report
  • Espettit
    You also need to forward HTTPS from your firewall to the internal server.
    0 pointsBadges:
    report
  • Chrisbf
    it works from the outside our network now. i guess it was a combination of the changes i had my isp make taking longer then exspect to take effect, and internal dns issues. now i just need to figure out how to get it to work from inside our network with the same address. guess im just missing something in dns.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: