Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

OWA Redirecting to Internal Server Name

For some reason, when accessing our OWA site through our external DNS https://webmail.domain.com/exchange it gets redirected to https://server.domain.local.  Internally and externally produces the same results even though I created an A record for webmail.domain.com.

What really baffles me though is that OWA still works externally, even though the internal server name is displayed in the address bar.  The biggest problem however is since the incorrect address is being shown we're getting a certificate error.

Any ideas what this could be?

Thanks in advance
0
paintb4707
Asked:
paintb4707
  • 3
  • 3
1 Solution
 
MesthaCommented:
Sounds like some kind of redirection has been set, possibly to enforce the use of SSL.
Has it ever worked correctly?

Simon.
0
 
paintb4707Author Commented:
Yes, it has.  I had to go through some PCI compliance crap recently, I wonder if this has anything to do with it?

http://support.microsoft.com/kb/834141
0
 
MesthaCommented:
What I was think of was this:
http://support.microsoft.com/kb/839357

The simple way to avoid the problem is to simply not open port 80 on the firewall. Make the users enter the https: version of the URL. After a few days of getting the error they will soon learn.

Simon.
0
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.

 
paintb4707Author Commented:
I do force HTTPS on our OWA server, since we're behind NAT and we also have a webserver, http is not an option externally.  I figured setting a redirection would be a waste of effort.
0
 
MesthaCommented:
The only reason Exchange directs to the server's internal FQDN is when you have multiple Exchange servers and you login to the wrong one. It then redirects you to the correct one. If you only have a single server then that shouldn't be happening.

If you undo the change that you made above and then run IISRESET does that resolve the problem?

Simon.
0
 
paintb4707Author Commented:
Yup, that was it.  Silly me.  I originally set the "Usehostname" command which I guess set it to the internal FQDN.  I used the "Sethostname" command to our external address and that fixed it.

Thanks
0

Featured Post

Become an Android App Developer

Ready to kick start your career in 2018? Learn how to build an Android app in January’s Course of the Month and open the door to new opportunities.

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