Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Fri, 16 Feb 2007 02:50:05 -0800,    group: microsoft.public.exchange2000.admin        back       


Exchange Virtual Server on Cluster and Public Folders - Error 8004   
We have a two node Exchange 2K3 SP2 Cluster running on W2K3 SP1 that has a 
public folder store; when we attempt to manage the Public Folders in Exchange 
System Manager we get the following error "ID No: 80040e19". The IP address 
of the two nodes in the cluster are .7 and .127, the Exchange Cluster Virtual 
Server IP is .163 and the MS Cluster IP is .162. 

Our IIS Config has three web sites configured; the default site using all 
unassigned IP address, the Exchange Vitual Server site using a .163 address 
and a third site for OWA access using the .163 and a host header.  

Currently to manage the public folders we have to change the IP address of 
the Exchange Virtual Server site to .7 (which is the actual 1st IP Address 
configured on the NIC (listed via IP CONFIG and also listed as the first IP 
address using the down arrow on IP Address in IIS Web Site Properties Dialog 
box. This IP address is the address of the A Node in the cluster as well), 
which also knocks out OWA access.

Having read the MS KB on this problem, the problem seems related to the fact 
that we aren't using the first IP Address assigned to the NIC for the 
Exchange Virtual Server Web Site so the required connection can't be made. I 
don't want to change the IP Address for the WEb Site to us unassigned IP 
address's as the /163 address is the one that it needs to use. The only 
option i can think of to resolve this is to use a host header that's 
identical to the Exchange Virtual Server name to direct the request to the 
right  IIS Web Site but wasn't sure if this was correct. 

As it's a 24x7 envrionment  I thought I'd check to see if anyone had any 
info on whether this ill work or if there's a better way of doing it. 

Thanks

G
date: Fri, 16 Feb 2007 02:50:05 -0800   author:   Gary S

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us