Improve company productivity with a Business Account.Sign Up

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

SBS2008 OWA not working when external

HI All

We recently changed the IP subnet, and since then we've lost connectivity to OWA remotely (externally).

We've checked Exchange, SBS console, IIS, certificate, DNS, everything, and nothing seem to work. Not sure what the problem is, but I would hope that someone could advise.

Thanks,
Goraek
0
goraek
Asked:
goraek
  • 9
  • 5
  • 3
1 Solution
 
David AtkinTechnical DirectorCommented:
Hello,

Have you changed the port redirections on your router to the new IP address of your server?

Run the fix my network wizard in the SBS Console to check for configuration issues.
0
 
goraekAuthor Commented:
Yeah I've done that.
I can jump on to OWA internally.
Fixed all issues in the SBS console, all seems to be working ok.
When I try it externally, I receive this:

File Not Found

The requested URL was not found on this server: /owa

Not sure what the problem is.
0
 
David AtkinTechnical DirectorCommented:
Are you trying to connect to OWA using the same name that is on the certificate?
0
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

 
goraekAuthor Commented:
Yes, still no go.
We did change it internally to like mail.domain.com/owa
The certificate is sev.domain.com/owa.
mail and sev still points to the same public IP, but NAT to apporpiate server accordingly.
0
 
David AtkinTechnical DirectorCommented:
Did you change the external address as well or just the internal one?
0
 
goraekAuthor Commented:
Just the internal one.
External is still the same.
0
 
David AtkinTechnical DirectorCommented:
Can you access it on https externally?
0
 
goraekAuthor Commented:
Nope.. nothing at all.
I can access it internally thats the thing.
But externally it just doesnt let me do it.
Its so weird.
Checked all the telneting test, all came ok.
0
 
David AtkinTechnical DirectorCommented:
Can you give me a scrrenshot of the internal and external urls on the OWA page under server configuraiton in exchange.

Have you restarted IIS since you changed the internal name?

If you use the internal name external, does it work?
0
 
JayCarter82Commented:
When you changed the internal name, did you change the certificate? Has your external IP changed for any reason?
0
 
goraekAuthor Commented:
No I didnt change the certificate. No change to external IP.
Even if I revert everything back, the error still the same.... so I dont believe theres anything to do with that..
0
 
JayCarter82Commented:
But does the certificate cover the new internal address at all? Might not make a difference of course, but just best to keep things up to date.
0
 
goraekAuthor Commented:
Certificate doesnt have IP justs DNS
IM just worried that the SBS is broken.
When you try to load, it says File not found.
But internally it works fine??
0
 
JayCarter82Commented:
It really sounds like the port forwarding is not pointed to the server correctly, but if you've checked that then I am scratching my head a bit. Have you tried running the tools on the Microsoft RCA?
0
 
goraekAuthor Commented:
Found what the issue is, its the certificate.
Not sure why it was assigned to the firewall certificate.
How do we change this and bind to the right one?
0
 
goraekAuthor Commented:
Its all fixed!
Found that our firewall was using SSL and HTTP!
Had to disable it - everything started to work again...
Thanks for you help anyway.
0
 
goraekAuthor Commented:
Trial and error
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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