Got that. The first Exchange server is redirecting to secondserver.ecsdnet.local, which is its FQDN. I can't make that FQDN accessible via the internet because of the name, of course.
Can that FQDN that the frist server redicrets to be modified? Or am I looking at putting up a third server temporarily and use it as a front end....that may be a better way to go I am thinking now. JK > -----Original Message----- > From: Simon Butler > If you aren't using a frontend server then both Exchange > servers need to be accessible from the Internet with their > own FQDN. The first Exchange server will then redirect you to > the second server (and vice versa if you connect to the > second server first). > The proxy-ing (is that a word?) of OWA to multiple servers > via a single entry point is one of the main functions of a > frontend / backend scenario. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
