Hej, we are successfully using Exchange2003 SP2 in W2003-Cluster (SP1) . We are going to define a second IMAP-Service for Exchange.Therefor we created another IP-clusterressource and defined a clusterdependecy for this new IPAddress. All cluster ressources are online When we are gonig te define the second IMAP-Service in Exchange, we can't select this new IP-Adderess as IP for the new service. Only the cluster-IP is offered. And as usual: in our testenvironment this works fine.. Any idea what we did wrong or what we missed to do? Thanks Ruth
We just learnt something new (Q293510): then new IP has to be listed with then Exchange network name in DNS. Thisi s not done in our DNS -why??? Ruth "Ruth Thieme" schrieb im Newsbeitrag news:uPAZCtwWHHA.4720@TK2MSFTNGP04.phx.gbl... > Hej, > > we are successfully using Exchange2003 SP2 in W2003-Cluster (SP1) . > > We are going to define a second IMAP-Service for Exchange.Therefor we > created another IP-clusterressource and defined a clusterdependecy for > this new IPAddress. All cluster ressources are online > When we are gonig te define the second IMAP-Service in Exchange, we can't > select this new IP-Adderess as IP for the new service. > Only the cluster-IP is offered. > > And as usual: in our testenvironment this works fine.. > > Any idea what we did wrong or what we missed to do? > > Thanks > Ruth >
