Thank you Tim,
So is my problem a client profile issue???? If so, how would I change
it.
I will try anything at this point.
"Tim Hackbart [MSFT]" wrote:
I think this is more of a DNS name resolution issue.
When you create an Outlook Profile, the OL client will pull down the
NetworkAdress attributes that contains the "name" for the Exchange
server.
Outlook will then choose the name for the protocol that it is trying to
use,
in most cases the ncacn_ip_tcp name and that will be the Internal FQDN
of
the server.
Long story short is that you will need to create HOSTS files on your
external clients that point the internal fqdn to the external IP address
of
the exchange server.
Hope this helps.
--
Tim Hackbart M.C.S.E.
This posting is provided "AS IS" with no warranties, and confers no
rights.
Please do not send email directly to this alias. This alias is for
newsgroup
purposes only.
"Louis" <Louis@discussions.microsoft.com> wrote in message
news:B4C838DA-40A5-4D03-B3F5-58A492877569@microsoft.com...
If one installs exchange 2003 with the .local instead of .com
extension.
Do
you kill 100% conectivity for outlook clients from the outside world.
All of my staff can connect internally but but from home. If an
employee
types in from home the exchange server IP address or DNS name outlook
clients
initially finds the user, CONVERTS the exchange server name to
Excahnge.MyDOmain.local and continues the setup with no problem.
However,
once its profile is changed to local. The outlook client can no longer
connect to the exchange server.
Is .local dooming me?
--
Louis
Expand AllCollapse All
--
Louis
Reply With Quote