NLB Add Host -- Access Denied After Upgrade

I have a NLB cluster with 3 hosts. The hosts were running Server 2003 SP1
(AD Forest A), Server 2003 SP1 (AD Forest A), and Server 2003 SP2 (AD Forest
B). I updated one of the SP1 hosts to SP2 tonight and migrated it via ADMT
to AD Forest B. Now it won't add back to the cluster (it was removed before
the upgrade).

The error that I receive is a logon prompt with a title of 'Unable to
connect'. 'Specify the credentials of a user with administrative privileges
on host "computername". I get this regardless which 3 of the systems that
I'm on. The system that was upgraded cannot even connect to existing
cluster. I'm logged on as an domain account that is a local administrator
on all 3 systems (there is a forest trust in place). I can browse the
administrative shares in both directions. I also tried the local
administrator credentials, which are the same on all 3 systems without
success, too.

AD Forest B requires NTLMv2 or Kerberos and disables NetBIOS. I don't think
that this is an issue as the original AD Forest B has been working and
continues to operate fine. I can even remove and add it back to the cluster
perfectly.

Any ideas on how to resolve this?
--
Tim

I found the solution. I ran wmidiag and it provided the fix:

22779 20:47:31 (1) !! ERROR: DCOM Status:
.................................................. ................................................
ERROR!
22780 20:47:31 (1) !! ERROR: => The DCOM configuration on this computer is
DISABLED.
22781 20:47:31 (0) ** This prevents WMI to work correctly.
22782 20:47:31 (0) ** You can fix the DCOM configuration by:
22783 20:47:31 (0) ** - Executing the 'DCOMCNFG.EXE' command.
22784 20:47:31 (0) ** - Expanding 'Component Services' and 'Computers'
nodes.
22785 20:47:31 (0) ** - Editing properties of 'My Computer' node.
22786 20:47:31 (0) ** - Editing the 'Default properties' tab.
22787 20:47:31 (0) ** - Activate the 'Enable Distributed COM on this
computer' checkbox.
22788 20:47:31 (0) ** From the command line, the DCOM configuration can
be corrected with the following command:
22789 20:47:31 (0) ** i.e. 'REG.EXE Add HKLM\SOFTWARE\Microsoft\Ole /v
EnableDCOM /t REG_SZ /d Y /f'
22790 20:47:31 (2) !! WARNING: => The DCOM Default Authentication is NOT set
to 'Connect'.
22791 20:47:31 (0) ** This could prevent WMI to work correctly.
22792 20:47:31 (0) ** You can fix the DCOM configuration by:
22793 20:47:31 (0) ** - Executing the 'DCOMCNFG.EXE' command.
22794 20:47:31 (0) ** - Expanding 'Component Services' and 'Computers'
nodes.
22795 20:47:31 (0) ** - Editing properties of 'My Computer' node.
22796 20:47:31 (0) ** - Editing the 'Default properties' tab.
22797 20:47:31 (0) ** - Set the 'Default Authentication level' listbox to
'Connect'.
22798 20:47:31 (0) ** From the command line, the DCOM configuration can
be corrected with the following command:
22799 20:47:31 (0) ** i.e. 'REG.EXE Add HKLM\SOFTWARE\Microsoft\Ole /v
LegacyAuthenticationLevel /t REG_DWORD /d 2 /f'
22800 20:47:31 (0) **

--
Tim

"Tim Chin" <donotemail> wrote in message
news:...
>I have a NLB cluster with 3 hosts. The hosts were running Server 2003 SP1
>(AD Forest A), Server 2003 SP1 (AD Forest A), and Server 2003 SP2 (AD
>Forest B). I updated one of the SP1 hosts to SP2 tonight and migrated it
>via ADMT to AD Forest B. Now it won't add back to the cluster (it was
>removed before the upgrade).
>
> The error that I receive is a logon prompt with a title of 'Unable to
> connect'. 'Specify the credentials of a user with administrative
> privileges on host "computername". I get this regardless which 3 of the
> systems that I'm on. The system that was upgraded cannot even connect to
> existing cluster. I'm logged on as an domain account that is a local
> administrator on all 3 systems (there is a forest trust in place). I can
> browse the administrative shares in both directions. I also tried the
> local administrator credentials, which are the same on all 3 systems
> without success, too.
>
> AD Forest B requires NTLMv2 or Kerberos and disables NetBIOS. I don't
> think that this is an issue as the original AD Forest B has been working
> and continues to operate fine. I can even remove and add it back to the
> cluster perfectly.
>
> Any ideas on how to resolve this?
> --
> Tim