Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 376
  • Last Modified:

Exchange 2003 OWA stopped working externally

We have a SBS 2003 server.  For years we have been using OWA with self signed certificate. To login to OWA we used to use https://xxx.xxx.xxx.xxx/exchange.   I recently (few weeks ago) I installed a SSL certficate and everything was working fine until the server was rebooted yesterday.  There was some updates applied during reboot.  FYI.  After I configured SSL, I did not reboot the server.  This was the first time server rebooted since SSL change.   Now we can not access OWA externally.  I checked internally and use http://servername/exchange and that logs me directly into OWA mailbox of current user logged in.  For example, if I use http;//username/exchange on a user workstation, it will log me directly into that user without a login prompt like we were used to seeing.  So what I am really concerned about is the external link to OWA not working. Can anyone shed some light on my issue?  I will provide more info as needed.  Thank you.
0
itechresults
Asked:
itechresults
  • 10
  • 3
  • 2
1 Solution
 
Suliman Abu KharroubIT Consultant Commented:
How do you configure external access ? publish through ISA/TMG or port forwarding ?

what is the error message you get?
0
 
itechresultsAuthor Commented:
I port forwarded 443 to server IP.  No ISA on SBS.  Error I receive is "The page cannot be found"  HTTP Error 404 - File or directory not found.
0
 
Suliman Abu KharroubIT Consultant Commented:
try to access it using IP address, what happen ?

also check the router (firewall) settings, make sure it forward to the correct server.
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
itechresultsAuthor Commented:
I tried using IP address and get same exact error message.  I just double checked firewall settings and they are correct.
0
 
itechresultsAuthor Commented:
I also tried resetting default virtual directories for OWA using method 2.  http://support.microsoft.com/kb/883380
0
 
James HIT DirectorCommented:
Can you verify your public IP and then verify external URL IP?
0
 
itechresultsAuthor Commented:
Hi Spartan:

What do you mean?  Our public IP has not changed and external URL IP is https://remote.domain.com.  An A record is setup pointing to server public IP.
0
 
James HIT DirectorCommented:
Did you have any redirects setup? Can you look at your firewall/router and verify that the traffic is being properly routed to the server?

0
 
itechresultsAuthor Commented:
No redirects.  Firewall is configured properly
0
 
itechresultsAuthor Commented:
If I use external https://remote.domain.com  without /exchange in url; it brings me to our old hosted website on our sbs server.  If I use /exchange I get the error mentioned.  Also I can see the certificate I setup when accessing either urls
0
 
itechresultsAuthor Commented:
Any experts out there with new suggestions???
0
 
Suliman Abu KharroubIT Consultant Commented:
Had you tried iisrset ?
0
 
itechresultsAuthor Commented:
Just tried iisreset and still have same issue
0
 
itechresultsAuthor Commented:
Problem solved.  When I setup ssl; I created a website in iis with same name as external url.  This caused a dns issue after server was rebooted
0
 
itechresultsAuthor Commented:
i resolved my own problem
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 10
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now