Greetings,
So I setup an Exchange 2007 that runs off Windows 2008 R2 configured as a DC. It's my home server so it's a simple, straight forward setup; one box does it all for me. I enabled all the features necessary in IIS to install the Outlook webmail feature. While it works fine, I ran into a snag when accessing it from outside the home network.
I configured the server to use a fictitious DNS TLD; homenet.local. After all, this box will never synchronize with other DC's outside this network nor will it ever delegate schema roles to others as well, so I found no need to use a real TLD. But apparently, the Outlook webmail that comes with Exchange 2007 makes use of redirection in IIS, whereas for example if one uses a pointer record such as outlook.mydomain.com to access Outlook webmail from the outside, IIS will accept the inbound request after you authenticate a valid Exchange-enabled AD account in the pop-up username/password window, then redirect you to an Outlook webmail home page where you have to authenticate again using the same credentials.
The problem lies when I get to this second authentication page. IIS redirects to this page using the FQDN I setup internally instead of using an external pointer record. As you may expect, I get "Page not Found" since homenet.local isn't a real TLD and if it were real, I don't own it anyway.
In Exchange 2003, IIS didn't use the internal FQDN to open Outlook webmail. It simply asked for credentials once using the pop-up username/password box and you were in.
Any way around this? Or does this all sound like Chinese?
TIA
↧