RE: Exchange 2k3 Cluster IIS Problem
- From: <ChongJa@xxxxxxxxxxxxxxxx>
- To: <exchangelist@xxxxxxxxxxxxx>
- Date: Wed, 28 Dec 2005 17:07:36 -0500
Did you install Ex sp1? Read some threads about other users having OWA
issues after installing sp1. Also did you make any recent changes?
________________________________
From: Jeffrey Moscone [mailto:jeff@xxxxxxxxxxxxxx]
Sent: Wednesday, December 28, 2005 2:39 PM
To: [ExchangeList]
Subject: [exchangelist] Exchange 2k3 Cluster IIS Problem
http://www.MSExchange.org/
Greetings-
I have a Microsoft Exchange 2003 2 Node Active/Passive Cluster.
I 'can' connect Outlook 2003 clients to each node when they are active.
I 'can' utilize OMA, OWA, and ActiveSync on one particular node. When
the Cluster Group moves to the other node I 'cannot' use OMA, OWA, and
ActiveSync (page cannot be displayed and can't connect to the
server/synchronization error). Also, my default web site will not
display on that node, but that's not very important at this time.
I have set the two nodes IIS/Virtual Directories configurations the
same. I've also read and tried a Microsoft KB article on how to reset
default web Virtual Directories and this has not helped either.
The two servers utilize their local Inetpub directories and the
\\.\Backoffice(etc.) <file:///\\.\Backoffice(etc.)> for IIS. Should
this be? Is there a way to set IIS to use the cluster quorum for the
Exchange Virtual Directories? Has anyone seen this?
Thanks
Jeff
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as:
chongja@xxxxxxxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to info@xxxxxxxxxxxxxx
Other related posts: