I have an Exchange 2013 server deployed in my network (on Server 2012). I have an Exchange 2007 server as well for the time being until I have permission to migrate the client (scheduled in a few days). At any rate, I have everything setup
correctly for the various protocols (OWA, ECP, etc.). However, with ECP only I am having an issue. When I navigate to the external url: https://mail.mycompany.com/ecp I get the ECP login page as expected. And when I login, I then get
a 403 page could not be displayed error. Based off of this evidence alone, I know that my router is configured correctly as I am making it to the ECP page to begin with. The same goes for my URL being published to the outside world. Additionally,
my login is not failing because I am not getting a UN/PW error. This leaves me to believe that I DNS record of some sort to correctly navigate to my new exchange server. (I have split DNS setup, where some of my DNS records are hosted off-site
and some are hosted internally). On my DNS server I have a CNAME record that points mail.mycompany.com to a officemail.mycompany.com record. Then an A record points officemail.mycompany.com to my old server (Exch2k7). Now before I get flamed
for this, I inherited this network and I'm not sure what the original person's intentions were, but I prefer to leave things alone until they break. So here is what I think is happening, when I login mail.mycompany.com/ecp is being redirected to my Exch2k7
server which obviously is not going to work. However, if I change the A record to point to my new server (Exch2k13), then I can no longer access the ECP login screen and get the 403 page cannot be displayed by going to the external URL (https://mail.mycompany.com/ecp). Any thoughts on how I can get this to work? I can't create 2 CNAME records and I'm not even sure I need it anymore since everything is Proxied through the new server. But if changing the record breaks the website entirely from the outside
world, then no bueno either. Help!!!
↧