"Kevin0Tech" wrote:
> I have 3 Win2k3 Terminal Servers in a cluster. Using single NIC with
> multicast on a layer 2 switch. All was working beautifully for about 18
> months. Then, all of a sudden the Term01 server dropped out of the cluster
> and started hosing the connections to the virtual IP. Being the middle of the
> day, I just removed it from the Cluster and shut it down. This week I finally
> had a chance to work the issue, and am unable to add it back to the Cluster.
> It always wants to prompt me for credentials when I go to add it. None of the
> other cluster servers have ever asked, since I am logged in with Domain Admin
> rights to the server and network. I ran a test and removed Term03 from the
> Cluster, then added it back with no prompt for credentials. It is only this
> Term01 server that will not allow me to re-add to the cluster. I removed this
> server from the domain, then added it back usking a domain adminitrator
> account. I ran secedit to restore the default policy rights to the server,
> and rebooted several times. I also removed NLB services rebooted and
> reinstalled. This server just will not re-join the cluster. No firewall is
> enabled for the individual servers, and they are all on the same subnet. I am
> at a loss of what to try next short of rebuilding the server, which is about
> an 8 hour process because of the application configurations. Any advice?
Problem resolved. I noticed that in procexp from sysinternals that
wuauclt.exe was bound to tcp port 1765. This interfered with the winmgmt for
wlbs. I killed the process and the parent srvchost.exe that pid was locked
to. After that I was able to restart the WLBS Manager and bring this server
back into the cluster. I then restarted the update services, and it rebound
to an alternate port.
|
Similar Threads
Linear Mode
