.local vs .com

[Louis]

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

[John Oliver, Jr. [MVP]]

No, in fact this is very secure and prefered method. First question is how
are your users connecting from home? RPC orver HTTP or VPN? What version
of Outlook and are they using Cached Mode or Offline Mode?

--
John Oliver, Jr.
MCSE, MCT, CCNA, Exchange MVP
Microsoft Certified Partner

"Louis" <Louis@discussions.microsoft.com> wrote in message
news:994FD38F-21A2-419E-9445-6C6898C293CC@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