Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Name coordination between Cluster service and Network and Dial-up Connections

Updated: January 21, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Name coordination between Cluster service and Network Connections

In the Windows Server 2003 family, each physical network adapter in a computer is represented by a named icon in the Network Connections folder. The Cluster service coordinates the names of its network interface objects with the names of the icons in the Network Connections folder.

Automatic renaming of networks

Windows Server 2003 family operating systems automatically ensure that both a server cluster and the Network Connections folder use the same name to reference any individual network interface. For example, if you use any cluster administration tool to rename a cluster network object, the Windows Server 2003 family operating system automatically renames the corresponding icon in the Network Connections folder. Similarly, if you rename a network connection icon in the Network Connections folder, the Windows Server 2003 family operating system renames the matching cluster network object, if one exists.

The Windows Server 2003 family operating system ensures that cluster nodes also use the same name for the network object and corresponding icons in the Network Connections folder. Therefore, if you rename a cluster network object on one node of a cluster, the name of the network object on the other nodes and the icon name in the Network Connections folders on all nodes also change. The operating system does not notify you when it renames a related cluster network object or icon in a Network Connections folder.

The following table summarizes the actions the Windows Server 2003 family operating system takes in response to any renaming you perform.

 

Action Result

Set up a new cluster.

The Windows Server 2003 family operating system uses the names of the icons in the Network Connections folder as the default names for cluster network objects. If you choose to rename any of the cluster network objects, the operating system renames the corresponding icon in the Network Connections folder.

Add a new node to an existing cluster.

The Windows Server 2003 family operating system renames icons in the Network Connections folder to match the names of the cluster network objects.

Rename a network object using a cluster administration tool.

The corresponding icon in the Network Connections folder is renamed on all cluster nodes.

Rename an icon in the Network Connections folder.

The Windows Server 2003 family operating system renames the corresponding cluster network object. It renames the corresponding icon in the Network Connections folder on the other node.

Network name conflicts

When you change the name of a network object or an icon in the Network Connections folder on one node of a cluster, you introduce the possibility of a naming conflict. For example, assume you have a cluster consisting of Node 1 and Node 2, and you change the name of a cluster network object on Node 1 from Public Network to Corporate Network. If an icon in the Network Connections folder on either Node 1 or Node 2 is already named Corporate Network, then the renaming attempt creates a name conflict.

Windows Server 2003 family operating systems prevent name conflicts by appending a number to any existing icon or network object names that would cause a name conflict with whatever new name you enter. In the previous example, the operating system renames the existing Corporate Network icon to Corporate Network (2). This feature ensures that whenever you attempt to rename a network object or an icon in the Network Connections folder, your renaming attempt succeeds without generating any name conflicts.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.