Additional Exch 2003 SP2 Server problems with OWA, OMA, EAS   

I have installed an additional Exchange Ent 2003 SP2 server into our simple 
environment (one site, same lan) and started testing by moving over a mailbox 
to the new server. For the moment let's say that the server will not have any 
dedicated connectors to the outside, it will merrely add additional mailbox 
capacity to the exch org. After I moved a mailbox over, I had no problems 
with outlook finding teh new home during startup (it works great). However, 
when testing EAS, then OMA and finally OWA, they all failed for this newly 
moved mailbox. When doing internal testing, I can access OWA and OMA by 
entering in the new Exch server's IP that is hosting teh test mailbox and 
entering credentials (NTLM prompt)  and get in just fine. However, if I try 
to go through OWA by entering the first exch server's IP , I am prompted for 
credentials from that first server, then prompted for credentials from the 
second server (where the mailbox resides). I have a ISA 2004 server that is 
publishing OWA and OMA, but it is only pointing back to the first exchange 
server. When testing this for the moved mailbox externally, I get an error 
fro OWA, OMA and EAS. My question is this: should the original exchange 
server be able to handle serving as the go-between for mailboxes stored on 
the second server for OWA, OMA and EAS or does the second Exchange server 
need to be setup to independently provide those services to the mailboxes 
located on that server? And, if that is the case, how do administrators 
manage that and also the specifc ip information/owa addresses for people 
homed on each server?

Thanks,

Ted

date: Mon, 25 Aug 2008 10:32:23 -0700   author:   Ted

Re: Additional Exch 2003 SP2 Server problems with OWA, OMA, EAS   

If you don't have a front-end server OWA and OMA will redirect from the 
first server to the second.  If you have a firewall, NAT and/or missing DNS 
entries, your Internet-based client simply won't like that.  The answer when 
you have more than one back-end server is a front-end server, which proxies 
web requests for back-end server, allowing you to expose only the front-end 
server to the Internet.
-- 
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.

"Ted"  wrote in message 
news:E9AFA384-9E10-4A2C-B28A-BF5E70445184@microsoft.com...
>I have installed an additional Exchange Ent 2003 SP2 server into our simple
> environment (one site, same lan) and started testing by moving over a 
> mailbox
> to the new server. For the moment let's say that the server will not have 
> any
> dedicated connectors to the outside, it will merrely add additional 
> mailbox
> capacity to the exch org. After I moved a mailbox over, I had no problems
> with outlook finding teh new home during startup (it works great). 
> However,
> when testing EAS, then OMA and finally OWA, they all failed for this newly
> moved mailbox. When doing internal testing, I can access OWA and OMA by
> entering in the new Exch server's IP that is hosting teh test mailbox and
> entering credentials (NTLM prompt)  and get in just fine. However, if I 
> try
> to go through OWA by entering the first exch server's IP , I am prompted 
> for
> credentials from that first server, then prompted for credentials from the
> second server (where the mailbox resides). I have a ISA 2004 server that 
> is
> publishing OWA and OMA, but it is only pointing back to the first exchange
> server. When testing this for the moved mailbox externally, I get an error
> fro OWA, OMA and EAS. My question is this: should the original exchange
> server be able to handle serving as the go-between for mailboxes stored on
> the second server for OWA, OMA and EAS or does the second Exchange server
> need to be setup to independently provide those services to the mailboxes
> located on that server? And, if that is the case, how do administrators
> manage that and also the specifc ip information/owa addresses for people
> homed on each server?
>
> Thanks,
>
> Ted

date: Mon, 25 Aug 2008 13:51:59 -0400   author:   Ed Crowley [MVP]

Re: Additional Exch 2003 SP2 Server problems with OWA, OMA, EAS   

Thanks for the reply Ed. You are correct, there is no front-end server. It 
makes sense as to why it is happening that way. Thanks for the answer.


Thanks,

Ted


"Ed Crowley [MVP]" wrote:

> If you don't have a front-end server OWA and OMA will redirect from the 
> first server to the second.  If you have a firewall, NAT and/or missing DNS 
> entries, your Internet-based client simply won't like that.  The answer when 
> you have more than one back-end server is a front-end server, which proxies 
> web requests for back-end server, allowing you to expose only the front-end 
> server to the Internet.
> -- 
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> ..
> 
> "Ted"  wrote in message 
> news:E9AFA384-9E10-4A2C-B28A-BF5E70445184@microsoft.com...
> >I have installed an additional Exchange Ent 2003 SP2 server into our simple
> > environment (one site, same lan) and started testing by moving over a 
> > mailbox
> > to the new server. For the moment let's say that the server will not have 
> > any
> > dedicated connectors to the outside, it will merrely add additional 
> > mailbox
> > capacity to the exch org. After I moved a mailbox over, I had no problems
> > with outlook finding teh new home during startup (it works great). 
> > However,
> > when testing EAS, then OMA and finally OWA, they all failed for this newly
> > moved mailbox. When doing internal testing, I can access OWA and OMA by
> > entering in the new Exch server's IP that is hosting teh test mailbox and
> > entering credentials (NTLM prompt)  and get in just fine. However, if I 
> > try
> > to go through OWA by entering the first exch server's IP , I am prompted 
> > for
> > credentials from that first server, then prompted for credentials from the
> > second server (where the mailbox resides). I have a ISA 2004 server that 
> > is
> > publishing OWA and OMA, but it is only pointing back to the first exchange
> > server. When testing this for the moved mailbox externally, I get an error
> > fro OWA, OMA and EAS. My question is this: should the original exchange
> > server be able to handle serving as the go-between for mailboxes stored on
> > the second server for OWA, OMA and EAS or does the second Exchange server
> > need to be setup to independently provide those services to the mailboxes
> > located on that server? And, if that is the case, how do administrators
> > manage that and also the specifc ip information/owa addresses for people
> > homed on each server?
> >
> > Thanks,
> >
> > Ted 
> 
> 
>

date: Mon, 25 Aug 2008 11:00:03 -0700   author:   Ted