Cluster Shares Appear in Browse List Under Other Names

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q170762
This article has been archived. It is offered "as is" and will no longer be updated.
If you create a file share resource within Microsoft Cluster Server, youmay be able to see the share in browse lists under multiple servers.
Microsoft Cluster Server allows resources to be moved from one server toanother in a cluster. When a network share is defined as a clusterresource, the share is offered by the server service on a particularcluster node. Because of multiple network names that may belong to the samecomputer, shared resources may appear under these names and may also beaccessible through them. This is by design.

NOTE: It is very important to use the network name associated with the group to which the shared resource belongs. If the group fails over toanother cluster node, the resource will only be available through thegroup's network name and through other network names on the other node.Thus, if a client uses the wrong network name, it may not re-establishnetwork connections after failover.

Additionally, if you create shares on the server and do not create them asa resource within the cluster software, the share will not be able tofail over to another node. Then it is considered a local share.
To avoid client connectivity interruptions, make sure that clients use thenetwork name associated with the group in which the shared resourcebelongs.
MSCS netbios server cluster

Article ID: 170762 - Last Review: 02/23/2014 01:07:59 - Revision: 3.4

Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Datacenter Server, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Cluster Server 1.1

  • kbnosurvey kbarchive kbprb kbsetup KB170762
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)