OWA Redirecting to Internal Server Name

Posted on 2009-04-07
Last Modified: 2012-05-06
For some reason, when accessing our OWA site through our external DNS it gets redirected to https://server.domain.local.  Internally and externally produces the same results even though I created an A record for

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
Question by:paintb4707
  • 3
  • 3
LVL 65

Expert Comment

ID: 24089376
Sounds like some kind of redirection has been set, possibly to enforce the use of SSL.
Has it ever worked correctly?


Author Comment

ID: 24089660
Yes, it has.  I had to go through some PCI compliance crap recently, I wonder if this has anything to do with it?
LVL 65

Expert Comment

ID: 24089697
What I was think of was this:

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.

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.


Author Comment

ID: 24089731
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.
LVL 65

Accepted Solution

Mestha earned 350 total points
ID: 24089787
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?


Author Closing Comment

ID: 31567628
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.


Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Can't send to contact 6 39
memory size used for Exchange email used on Andriod 3 21
exchange, 2 15
exchange, script 1 23
Utilizing an array to gracefully append to a list of EmailAddresses
This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

911 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now