>I have 1 Exchange 2000 server, and I just added an Exchange 2003 server, and
>moved all of the mailboxes over. Now, the OWA clients can not access their
>E-mail from the Web.
Did you update the firewall rules to allow them to access the new
server? Surely you don't allow access to every IP address on your LAN
from the 'net, do you?
>What changes have been made, or must be made in order
>for this to work.
None, if the server's accessible from outside the organization.
>I would rather keep the old 2000 server, for now, as the
>server to forward OWA requests to the new server. Is this possible?
No. But you can install Exchange 2003 on it and make it a front-end
server.
>Do I
>have to create a NAT entry to the new server?
Do you want the server to access, or be accessed from, the Internet?
>Do I have to open more ports?
Nope. Port 443 is all you should need.
>Currently, we have a PIX that performs NAT to the 2000 Exachange server and
>has the needed ports open for OWA 2000.
Ummm . . . where's the Exchange server? Not in the DMZ, I hope!

Signature
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
if you are directing folks with OWA to the Exchange 2000 server still and
expecting the server to auto-redirect them, you need to make sure the FQDN
you use externally for the new server matches the actual name of the server
(you can't use a split DNS type of setup, since your 2000 server will
redirect to exchange2003server.domain.com (where domain.com is your AD
domain). You also need to make sure that the IP that resolves from the FQDN
externally is NAT'ed through the firewall correctly to your new server and
has 443 open (like Rich mentioned). Hope this helps
> I have 1 Exchange 2000 server, and I just added an Exchange 2003 server, and
> moved all of the mailboxes over. Now, the OWA clients can not access their
[quoted text clipped - 8 lines]
> Thanks
> Tony