shuigen
Fri Jul 14 16:48:56 CDT 2006
Ben Winzenz [Exchange MVP] wrote:
> I'm not sure the point of doing what you are attempting to do.
>
> Why do you need to separate OWA from OMA/ActiveSync? They all work by
> default using the default website. Is there something specific you are
> trying to accomplish other than making your setup extremely complicated?
>
> --
> Ben Winzenz
> Exchange MVP
> MessageOne
> Read my blog!
>
http://winzenz.blogspot.com
>
http://feeds.feedburner.com/winzenz (RSS Feed)
>
>
> "shuigen" <shuigen@gmail.com> wrote in message
> news:1152884406.865755.70240@35g2000cwc.googlegroups.com...
> >I have an issue here, I hope someone can help.
> >
> > Exchange 2003 SP2 Back end
> >
> > Exchange 2003 SP2 Front end.(two nics teamed for one ip address)
> > Each virtual server has it's own ip address on the main nic.
> >
> > Default http virtual Servers (http, oma, actisync, pf work great)
> > Tried to setup another virtual server for;
> > http vitual 1 (owa, public folders)
> > http virtual 2 (oma, activesync)
> > default http server stopped
> >
> > Purpose is to have two sites, one for owa and one for oma
> >
> > I setup the config and it does not work. I can get owa to work when
> > disable the main http server, but not reliably.
> > anyone setup anything like this,
> > BE and FE are setup identically (the virtual servers match.
> >
> > Maybe it cannot use teaming nics?
> >
> > thanks,
> >
Upper Management decision,
separate OWA site from OMA site.
Users hit OWA.site.com for web email and
OMA.site.com for OMA site
This is what is wanted. If it can be done, great. IF not oh well.
I just need to answer this.
thanks,