imherson
asked on
file server failover cluster 2008 r2
Hello,
I'm trying to setup file services in a failover cluster with 2008 r2. Running through the "configure a service wizard, it fails to bring the resource on line with this error:
The Cluster service failed to bring clustered service or application 'computer'' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
I'm trying to setup file services in a failover cluster with 2008 r2. Running through the "configure a service wizard, it fails to bring the resource on line with this error:
The Cluster service failed to bring clustered service or application 'computer'' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
ASKER
disks are defined
2 nodes set a possible owners
The only dependency is that defined by configure service wizard
Note: server name resource status failed but IP and cluster disk are both online. fyi, this name/ IP is a defined in dns as an "a record"
Kerberos status access denied? and luster network name resource 'Fileserver' failed to create its associated computer object in domain xyz' for the following reason: Unable to create computer account.
2 nodes set a possible owners
The only dependency is that defined by configure service wizard
Note: server name resource status failed but IP and cluster disk are both online. fyi, this name/ IP is a defined in dns as an "a record"
Kerberos status access denied? and luster network name resource 'Fileserver' failed to create its associated computer object in domain xyz' for the following reason: Unable to create computer account.
Was this a manually created record in DNS?
ASKER
we don't have ddns. It's static bind dns
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes Thanks creating computer in active directory manually allowed the name resource to start
Also - did you create the share as a cluster resource using the "Provision a Shared Folder Wizard"?
In case you haven't seen this guide - http://technet.microsoft.com/en-us/library/cc731844(WS.10).aspx