I agree with Ryan, I think this is possibly an issue with your cluster
service account. I would guess that if you re-start the cluster service on
your currently working node, it would then also fail to restart. Any changes
to the cluster service account won't take affect in the cluster until the
cluster service is restarted.
I'd recommend reviewing the following KB and ensure that the permissions and
user rights are assigned properly to your cluster service account:
http://support.microsoft.com/kb/269229
Regards,
John
Visit my blog:
http://msmvps.com/blogs/jtoner
"Ryan Sokolowski [MVP]" <> wrote in message
news:87D807EC-05CB-4BCF-891D-...
> You've obviously got some additional security complexities here, being in
a
> government situation. I'd really recommend triple-checking all the
accounts
> and permissions and try troubleshooting / re-producing this in your Test
> environment.
>
> --
> Ryan Sokolowski
> MVP - Clustering
> MCT, MCITP x3, MCTS x8, MCSE x2, CCNA, CCDA, BCFP
>
>