You need another IP address for your non-Microsoft-firewall to map to the exchange 2000 server (NAT). Or you can use an alternate port (PAT - port address translation) if you can't come up with another IP address. It will not be seamless. To make it seamless requires a front-end server. From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Danny Sent: Thursday, November 02, 2006 11:04 AM To: exchangelist@xxxxxxxxxxxxx Subject: [ExchangeList] OWA options with 2nd Exchange server at different site My previous question on this topic caused some confusion, so here is another go: Previous environment: x1 Exchange 2000 Server on Windows 2000 Server SP4 Current environment: x1 Exchange Server 2003 SP2 on Windows Server 2003 R2 - OWA, Outlook RPC over HTTPS x1 Exchange 2000 Server on Windows 2000 SP4 - brought out of semi-retirement with recently migrated mailboxes from a different Exchange org. External email access traffic flow: Internet | v A firewall from a non-Microsoft vendor - HTTPS/443 & SMTP/25 open | v ISA 2004 SP2 - OWA & Outlook RPC publishing to Exchange Server 2003 | v Exchange Server 2003 - OWA, Outlook RPC over HTTPS | v Corporate WAN | v Different site - same AD, same Exchange org | v Exchange 2000 Server with mailboxes What options would I have for the Exchange 2000 users to access OWA from the Internet? Thanks, ...D