Second Exchange server - No OWA from Internet

[SNosko]

I have two Exchnage servers. Exchange server "A" has a NAT IP address to the Internet and works just fine. I installed Exchange Server "B" across a WAN link and moved a mailbox to it. It does not have a NAT IP address. When email is sent from the Internet thru Server A to a mailbox on Server B it works just fine.

Internet -> Server A -> Server B

I created a Virtual Server in HTTP and OWA works on Server B from inside the company but OWA won't work from the Internet. The MX record is pointing to Server A. I was assuming that Server A would redirect the OWA traffic to B and act as a pass-thru but it doesn't work that way.

Any suggestions?

 

[julianf]

Howsit,

I have the same problem. Just posted my own thread before I saw yours. After we migrated from exchange 5.5, it stopped working for the remote site.)

I wonder if it has anything to do with SSL...since it is required for OWA on exchange 2000. I have installed an SSL certificate on the main exchange server, but not on the remote one. Perhaps this is needed???

I also assumed that the main exchange server would simply redirect the request to the other server, as it did with 5.5?

Regards,

Julian

 

[Petje]

What you could do is have a front-end exchange server setup. This server would then relay the mailbox information and things like that to the right server. this way your servers don't have to be reached directly from the internet.



Petje
A+, MCP, MCSE on NT4.0 and windows 2000 with messaging specialty and CCEA

 

[julianf]

Hi,

Isn't this the default setup? When users access the main server, they get redirected to the other one, if their mailbox residesed there?

If not, how does one setup the above...? Has this issue got nothing to do with the fact that SSL certificate has not been setup on the 2nd server.

Julian

 

[SNosko]

Internally the OWA does switch to the correct server but from the Internet it doesn't. Here is how I chose to get around this issue:

I created a second A record in our External DNS pointing to the a public IP address that we own. Using NAT I pointed the public address to the private address of the second server.

Snosko

 

[julianf]

SNosko,

Thanks for the info. Do you mean that I have to create a new A-record with our primary DNS holders....or can I just create an entry on the local DNS server...?

Please explain?

Regards,

Julian

 

[peterpark]

Firstly, a frontend exchange server can only be setup using Exchange 2000 enterprise edition.

Secondly, for your second server(without the frontend/backend exchange setup), for you to access it externally via OWA, then you at least need a public ip address for this 2nd server. You don't really need an A record for the 2nd server to access it. Just point to it using the public ip address, if you are comfortable using ip addresses to access, else you can setup an A record for it. Hope that doesn't confuse you further

 

[julianf]

Hi,

Basically you are saying that the 2nd exchnage server needs it's own legal IP to be accessed. Why has this been setup this way? Exchange 5.5 was different...mailboxes on the remote server could be accessed via the same IP/URL???

What a mission....I am currently running a trial copy and will be installing enterprise edition later on in the week. Perhaps enterprise version will have other options?

Julian

 

[SNosko]

Julian,

The subject is Outlook Web Acces only and not getting emails from the Internet to a second server across the wan. If an email comes in from the Internet it contacts my main exchange server and then that server transfers the email to the second if necessary but OWA is a problem.

Steve