Create a DNS entry for mail.company.com and have the users add company.com to their DNS suffix search order if it isn't there already. If this box is exposed to the internet then requiring VPN would be the wisest and safest strategy though.
> -----Original Message----- > From: David Wright [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 11, 2002 12:24 PM > To: Exchange Discussions > Subject: Internal Exchange Name vs. external Internet Address/Name > > > Hi All, > > Is there a way to have Outlook NOT rename the Exchange Server > after it resolved the server address? > > Our situation: > Internally, the server is named MAIL > It can be reached via the web at TEST.company.com > When we configure Outlook, we enter TEST.company.com and it > validates the user... Then it changes the server name to MAIL. > > Of course, Outlook will no longer work because the address > MAIL is not valid on the net. > > We have 2 solutions, but we do not like either: > 1) Add HOSTS table entry on remote machines (but then they > fail internally) > 2) Require VPN connection > > Of course, had I foreseen this issue, I would have named the > Exchange server TEST.company.com to begin with (assuming that > is even possible). > > Thanks for any ideas/insight, > David _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
