Unable to access Windows local file shares using the Veritas Cluster Server (VCS) virtual server name or virtual server IP address configured for Lanman and IP resources.
Article ID: 100053055
Updated On:
Description
Error Message
N/A
Cause
File share scoping was introduced in Windows 2008 and later, which changes the way the cluster service interoperates with the server service on a cluster node.
Resolution
Veritas Engineering has updated functionality for the Lanman and FileShare resources to create file shares without scoping. Shares created without scoping can be accessed using local hostname, VCS virtual name, or VCS virtual IP.
Configure the DisableServerNameScoping registry key:
**Note: Incorrectly editing the registry may severely damage your system. Back up the registry before making changes.
- Open Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\BundledAgents
- Click Edit --> New --> Key and create a key named Lanman if it does not exist
- Select the Lanman key and click Edit --> New --> Key and create a key by the name __Global__
- Select the __Global__ key and add a DWORD type key with name DisableServerNameScoping and value of 1
- Re-online Lanman and FileShare resources to disable file share scoping with VCS
Issue/Introduction
Unable to access Windows local file shares using the Veritas Cluster Server (VCS) virtual server name or virtual server IP address configured for Lanman and IP resources. Shares created on Windows are not visible with the VCS Lanman virtual name, and VCS shares are not visible with server hostname. No shares are visible with the VCS virtual IP.
Was this article helpful?
Yes
No
Powered by
