two reboots required for cluster to see domain

[azcats]

Whenever I have to reboot any of the servers in my cluster, they require a second reboot and re-addition to the domain. Here is a synopsis:

1) join server to the domain
2) reboot as requested
3) login using domain admin account with no problems, server functions normally

If for some reason the server has to be rebooted after step 3, this is what happens

4) login using admin account takes 3-4 minutes, eventually times out and uses cached login credentials. Server is not on the domain. In the event log I see this message:

"There are currently no logon servers available to service the logon request."

5) take server out of the domain
6) join server to domain again
7) repeat steps 1-3 for server to see the rest of the domain

If there was a bad NIC or perpetually unreachable domain controller this might make sense but the domain re-addition and 2nd reboot seem to solve the problem which is just weird.

Any ideas? Thanks in advance.

 

[Castor66]

HAve a look at your WINS setup. I think you'll find errors about duplicate names on the network which is probably causing the cluster to get its knickers in a twist. I've seen this on NT Clusters before.