F
Fred Colclough
I have an interesting one here:
Brand new Exchange Svr 2007, fresh install.
Set up all external & internal URLs for autodiscovery, webservices, etc. accurately. DNS is set up.
All Outlook 2007 clients (both IN the domain and OUT of the domain) get the following FQDN for the Exchange Server:
Exchangesvr.spacefoundation.internal
This URL is the INTERNAL only FQDN, NOT the external URLs set in the config& in DNS, which are:
Exchange.spacefoundation.org
The domain Outlook clients all work fine, since they're inside & have visibility to this internal FQDN.
But the OUTSIDE Outlook 2007 clients, obviously have NO visibility to the "..internal" name Exchange Server provided during autodiscovery.
I can't even CHANGE it using manual settings in Outlook 2007!!!
The ONLY way I've gotten it to work, is by placing a HOSTS file entry routing the .internal URL to the public IP. What a work-around, huh?!
I'd sure like to fix the root problem here.
Anyone know why Exchange is giving out it's internal computer name to Outlook clients?? (Incidentally, mobile devices, such as Blackberries, iPhones, all work fine!)
Thanks!
-Fred.
--
-------------------------------
Frederick H. Colclough
Dir., Information Technology
Space Foundation
http://www.spacefoundation.org
-------------------------------
Brand new Exchange Svr 2007, fresh install.
Set up all external & internal URLs for autodiscovery, webservices, etc. accurately. DNS is set up.
All Outlook 2007 clients (both IN the domain and OUT of the domain) get the following FQDN for the Exchange Server:
Exchangesvr.spacefoundation.internal
This URL is the INTERNAL only FQDN, NOT the external URLs set in the config& in DNS, which are:
Exchange.spacefoundation.org
The domain Outlook clients all work fine, since they're inside & have visibility to this internal FQDN.
But the OUTSIDE Outlook 2007 clients, obviously have NO visibility to the "..internal" name Exchange Server provided during autodiscovery.
I can't even CHANGE it using manual settings in Outlook 2007!!!
The ONLY way I've gotten it to work, is by placing a HOSTS file entry routing the .internal URL to the public IP. What a work-around, huh?!
I'd sure like to fix the root problem here.
Anyone know why Exchange is giving out it's internal computer name to Outlook clients?? (Incidentally, mobile devices, such as Blackberries, iPhones, all work fine!)
Thanks!
-Fred.
--
-------------------------------
Frederick H. Colclough
Dir., Information Technology
Space Foundation
http://www.spacefoundation.org
-------------------------------