Which will be faster than not being able to connect at all!
-----Original Message----- From: Tom Meunier [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 11, 2002 1:44 PM To: Exchange Discussions Subject: RE: Internal Exchange Name vs. external Internet Address/Name Yeah, they'll love the interface and switch to complaining about the performance. > -----Original Message----- > From: Andy David [mailto:[EMAIL PROTECTED]] > Posted At: Wednesday, September 11, 2002 12:38 PM > Posted To: MSExchange Mailing List > Conversation: Internal Exchange Name vs. external Internet > Address/Name > Subject: RE: Internal Exchange Name vs. external Internet Address/Name > > > Thats a big 10-4 Rubber Ducky. > > > -----Original Message----- > From: David Wright [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 11, 2002 1:35 PM > To: Exchange Discussions > Subject: RE: Internal Exchange Name vs. external Internet Address/Name > > > Our users have complained about OWA (5.5)... Is OWA any > better (more user > friendly) in Exchange 2000? > > > -----Original Message----- > From: Andy David [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 11, 2002 10:27 AM > To: Exchange Discussions > Subject: RE: Internal Exchange Name vs. external Internet Address/Name > > > 2 > or use > OWA > > > -----Original Message----- > From: David Wright [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 11, 2002 1: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] > > -------------------------------------------------------------- > -------------- > -- > The information contained in this email message is privileged > and confidential information intended only for the use of the > individual or entity to whom it is addressed. If the reader > of this message is not the intended recipient, you are hereby > notified that any dissemination, distribution or copy of this > message is strictly prohibited. If you have received this > email in error, please immediately notify Veronis Suhler > Stevenson by telephone (212)935-4990, fax (212)381-8168, or email > ([EMAIL PROTECTED]) and delete the message. Thank you. > > ============================================================== > ============== > == > > > _________________________________________________________________ > 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] > > _________________________________________________________________ > 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] > > -------------------------------------------------------------- > ---------------- > The information contained in this email message is privileged > and confidential information intended only for the use of the > individual or entity to whom it is addressed. If the reader > of this message is not the intended recipient, you are hereby > notified that any dissemination, distribution or copy of this > message is strictly prohibited. If you have received this > email in error, please immediately notify Veronis Suhler > Stevenson by telephone (212)935-4990, fax (212)381-8168, or > email ([EMAIL PROTECTED]) and delete the message. Thank you. > > ============================================================== > ================ > > > _________________________________________________________________ > 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] > _________________________________________________________________ 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] ------------------------------------------------------------------------------ The information contained in this email message is privileged and confidential information intended only for the use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copy of this message is strictly prohibited. If you have received this email in error, please immediately notify Veronis Suhler Stevenson by telephone (212)935-4990, fax (212)381-8168, or email ([EMAIL PROTECTED]) and delete the message. Thank you. ============================================================================== _________________________________________________________________ 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]
