Default website and OWA

I have a front end server running Win2k3, IIS 6.0, and OWA in which the
default website quit working. I had to create a new website on this
server and restore from backup the virtual directories in order to get
OWA working again. Now the http virtual server won't start on this
server in ESM, access to OWA works fine.The http exchange virtual
server on the back end cluster is started and running ok. Being that
the default http virtual server for the front end is crippled because
it's attached to the default website, will creating a new http virtual
server work with the new website or does any http virtual server
created still revert to the default website? I'm looking for the best
way to A) either somehow get the default website working again so that
it and the default http virtual server will actually start and outlook
web access can be accessed from there (I'm thinking now that maybe the
virtual directories were the problem and that maybe if I restore them
from the new website to the default website maybe it will start again)
or B) create a new "http virtual server" in Exchange System Manager
under administrative groups, protocols, http and see if it will point
to the new website I created that is working now with OWA. I'd like to
do this without bringing down OWA as it is working.

The reason I need to do this is we'll be installing RPC over Http and
forms based authentication and the http virtual server has to be
running on both the front end and back end servers.

Any help with this will be greatly appreciated,
Thanks,



--
mmcgowan
------------------------------------------------------------ ------------
Posted via http://www.webservertalk.com
------------------------------------------------------------ ------------
View this thread: http://www.webservertalk.com/message858732.html