Exchange 2007 on Server 2008 Geo-Cluster

When we fail over our cluster to our passive node, the cluster ip address is
getting associated with the Heartbeat adapter, which is what I think is
causing the cluster to not be able to register the dns record. I can't
figure out why the failed over Exchange Clustered server won't register its
dns record.

If I look at the two nodes in Cluster Manager (Nodes) the failing clustered
server default network connection is listed as the Heartbeat nic where as
the working NIC lists the correct nic.

I'm wondering if there is a configuration that some how got flipped and we
can't find it. This used to all work and we can't find anything that has
changed.

Thoughts???

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

Figured it out, stupid on my part. It was just a networking order issue, as
far as name issue.

Still can't figure out why the cluster won't register its dns name when it
fails over. ???

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"Paul Bergson [MVP-DS]" <pbbergs@no_spammsn.com> wrote in message
news:...
> When we fail over our cluster to our passive node, the cluster ip address
> is getting associated with the Heartbeat adapter, which is what I think is
> causing the cluster to not be able to register the dns record. I can't
> figure out why the failed over Exchange Clustered server won't register
> its dns record.
>
> If I look at the two nodes in Cluster Manager (Nodes) the failing
> clustered server default network connection is listed as the Heartbeat nic
> where as the working NIC lists the correct nic.
>
> I'm wondering if there is a configuration that some how got flipped and we
> can't find it. This used to all work and we can't find anything that has
> changed.
>
> Thoughts???
>
> --
> Paul Bergson
> MVP - Directory Services
> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> 2008, 2003, 2000 (Early Achiever), NT4
> Microsoft's Thrive IT Pro of the Month - June 2009
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup This
> posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Make sure you don't haven't entered a static DNS record for the cluster.
I've seen that cause problems. Also, make sure that the CMS account owns
the cluster DNS entry.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"Paul Bergson [MVP-DS]" <pbbergs@no_spammsn.com> wrote in message
news:...
> Figured it out, stupid on my part. It was just a networking order issue,
> as far as name issue.
>
> Still can't figure out why the cluster won't register its dns name when it
> fails over. ???
>
> --
> Paul Bergson
> MVP - Directory Services
> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> 2008, 2003, 2000 (Early Achiever), NT4
> Microsoft's Thrive IT Pro of the Month - June 2009
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup This
> posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Paul Bergson [MVP-DS]" <pbbergs@no_spammsn.com> wrote in message
> news:...
>> When we fail over our cluster to our passive node, the cluster ip address
>> is getting associated with the Heartbeat adapter, which is what I think
>> is causing the cluster to not be able to register the dns record. I
>> can't figure out why the failed over Exchange Clustered server won't
>> register its dns record.
>>
>> If I look at the two nodes in Cluster Manager (Nodes) the failing
>> clustered server default network connection is listed as the Heartbeat
>> nic where as the working NIC lists the correct nic.
>>
>> I'm wondering if there is a configuration that some how got flipped and
>> we can't find it. This used to all work and we can't find anything that
>> has changed.
>>
>> Thoughts???
>>
>> --
>> Paul Bergson
>> MVP - Directory Services
>> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
>> 2008, 2003, 2000 (Early Achiever), NT4
>> Microsoft's Thrive IT Pro of the Month - June 2009
>>
>> http://www.pbbergs.com
>>
>> Please no e-mails, any questions should be posted in the NewsGroup This
>> posting is provided "AS IS" with no warranties, and confers no rights.
>>
>>
>
>

I believe the virtual machine account owns the record. There are no errors
that I can find blocking the machine from registering either. Really odd.

I'm stumped, may have to give PSS a call.

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"Ed Crowley [MVP]" <> wrote in message
news:...
> Make sure you don't haven't entered a static DNS record for the cluster.
> I've seen that cause problems. Also, make sure that the CMS account owns
> the cluster DNS entry.
> --
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> .
>
> "Paul Bergson [MVP-DS]" <pbbergs@no_spammsn.com> wrote in message
> news:...
>> Figured it out, stupid on my part. It was just a networking order issue,
>> as far as name issue.
>>
>> Still can't figure out why the cluster won't register its dns name when
>> it fails over. ???
>>
>> --
>> Paul Bergson
>> MVP - Directory Services
>> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
>> 2008, 2003, 2000 (Early Achiever), NT4
>> Microsoft's Thrive IT Pro of the Month - June 2009
>>
>> http://www.pbbergs.com
>>
>> Please no e-mails, any questions should be posted in the NewsGroup This
>> posting is provided "AS IS" with no warranties, and confers no rights.
>>
>> "Paul Bergson [MVP-DS]" <pbbergs@no_spammsn.com> wrote in message
>> news:...
>>> When we fail over our cluster to our passive node, the cluster ip
>>> address is getting associated with the Heartbeat adapter, which is what
>>> I think is causing the cluster to not be able to register the dns
>>> record. I can't figure out why the failed over Exchange Clustered
>>> server won't register its dns record.
>>>
>>> If I look at the two nodes in Cluster Manager (Nodes) the failing
>>> clustered server default network connection is listed as the Heartbeat
>>> nic where as the working NIC lists the correct nic.
>>>
>>> I'm wondering if there is a configuration that some how got flipped and
>>> we can't find it. This used to all work and we can't find anything that
>>> has changed.
>>>
>>> Thoughts???
>>>
>>> --
>>> Paul Bergson
>>> MVP - Directory Services
>>> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
>>> 2008, 2003, 2000 (Early Achiever), NT4
>>> Microsoft's Thrive IT Pro of the Month - June 2009
>>>
>>> http://www.pbbergs.com
>>>
>>> Please no e-mails, any questions should be posted in the NewsGroup This
>>> posting is provided "AS IS" with no warranties, and confers no rights.
>>>
>>>
>>
>>
>