Windows Server 2008
In a cluster, a Network Name resource can be important because other resources depend on it. A Network Name resource can come online only if it is configured correctly, and is supported correctly by available networks and network configurations.
The Network Name resource could not register one or more Domain Name System (DNS) names. If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering." If the event contains an error code that you have not yet looked up, see "Finding more information about error codes that some event messages contain." After reviewing event messages, check the following:
To perform the following procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.
To open Event Viewer and view events related to failover clustering:
To find more information about the error codes that some event messages contain:
NET HELPMSG errorcode
To verify that a Network Name resource can come online:
To perform a quick check on the status of a resource, you can run the following command.
To use a command to check the status of a resource in a failover cluster:
CLUSTER RESOURCE ResourceName /STATUS
If you run the preceding command without specifying a resource name, status is displayed for all resources in the cluster.
Network Name Resource Availability
If you are running in an environment that has a third-party (Bind) DNS server, you will need to apply this Hotfix.
- Go to DNS find the record ( A & Pointer record) for the cluster name resource.
- Make a right click
- Go to properties
- In the security make sure the "Authenticated users" group is included
- Make sure it has "Write" rights and Special permissions
- Click Advanced, locate authenticated users and click edit
- Make sure Write all properties Read permissions All Validated Writes selected
- Click OK tree times to exit