S
Scott Kuriger
Guest
I manage a Windows 2000 domain, that has 2 windows 2000 domain controllers, DC1 and DC2. There are multiple Windows 2003 servers in the domain.
There are 2 Windows 2003 servers that are clustered, and here is the issue:
When DC2 is down, one of the cluster groups will not come up, it just bounces from one node to another, and in the Event log I see this error:
Type: Error
Source: Service Control Manager
Event ID: 7000
Event Time: 7/10/2008 5:13:13 PM
User: n/a
Computer: Node1
Description:
The Node1 Server SVPDW1 service failed to start due to the following error:
The account name is invalid or does not exist, or the password is invalid for the account name specified.
The SVPDW1 service uses the Clustersvc account, as does all the other cluster groups. It just cannot come up if DC2 is down.
I have transferred all the FSMO roles to DC1, and put DC1 at the top of the list in the DNS servers in the TCPIP settings, but that did not resolve the issue.
Is there any setting to force authentication from a particular DC? I'm thinking whoever built this server may have done something to that effect. I am only concerned, because DC2 is very old hardware, and if it dies, so does that cluster group.
Scott
There are 2 Windows 2003 servers that are clustered, and here is the issue:
When DC2 is down, one of the cluster groups will not come up, it just bounces from one node to another, and in the Event log I see this error:
Type: Error
Source: Service Control Manager
Event ID: 7000
Event Time: 7/10/2008 5:13:13 PM
User: n/a
Computer: Node1
Description:
The Node1 Server SVPDW1 service failed to start due to the following error:
The account name is invalid or does not exist, or the password is invalid for the account name specified.
The SVPDW1 service uses the Clustersvc account, as does all the other cluster groups. It just cannot come up if DC2 is down.
I have transferred all the FSMO roles to DC1, and put DC1 at the top of the list in the DNS servers in the TCPIP settings, but that did not resolve the issue.
Is there any setting to force authentication from a particular DC? I'm thinking whoever built this server may have done something to that effect. I am only concerned, because DC2 is very old hardware, and if it dies, so does that cluster group.
Scott