Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Outlook Setup of Exchange Server changes server name

Status
Not open for further replies.

svankley

MIS
Aug 25, 2000
45
US
I have an issue with our test server and setting up an Outlook client.

We're running Exchange 2007 with all patches and when I set up the account server (mail.myserver.com) and name in Outlook and click the "Check Name" button, the Exchange server field is changed to our internal FQDN (tpa.myserver.local). The name is now underlined so it found it, but the server is changed to our internal name.

I went in and changed the 'Client Properties' field "Specify the FQDN this connector will provide in response to HELO" to 'mail.myserver.com', but that didn't change anything.

Is this the right place to chaneg this or am I way off base.

Please assist as I have tested OWA, smartphone and all works fine except for this... the final piece to it all working.

Thanks in advance for any help!!

Steve
 
I saw on another thread that I need run cmdlets to let Exchange know what the "internet" name is for my server. I read through the whole list and can't find one particular one that does this. Is this the solution to my problem??

Thanks!!
 
That gets set on both the SEND and RECEIVE connectors. With the receive connector, you can only change it to your .com name if EXCHANGE SERVER AUTHENTICATION is not checked for authentication.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Steve, what you are describing is normal. There is nothing wrong with the internal name showing. If you are trying to set up Outlook Anywhere, you will then configure the Exchange Proxy (or Remote Exchange, or whatever) settings and specify the external FQDN there.

Don't worry about the cmdlets at this point if OWA and ActiveSync are already working, as you are likely to break things.

Dave Shackelford
Shackelford Consulting
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top