Consider the following scenario:

• You have a server that runs the Unisys MCP operating system on a network.
• On this network, the credentials that users use to access the MCP server differ from the logon credentials that they use to log on to the domain.
• A user accesses a network share on the Unisys MCP server by using a Windows Vista-based client computer.
• To access this network share, this user types the Uniform Naming Convention (UNC) path of the MCP server.

In this scenario, Windows Vista does not enumerate the share list on the server.

However, if the user accesses a network share on the Unisys MCP server by typing the Uniform Naming Convention (UNC) path together with the share name, the user can access the network share.

For example, if the user tries to access the share by typing the following UNC path, the user cannot obtain the share list on the server:

\\ServerName

However, the user can access the share by typing the UNC path together with the share name, as in the following example:

\\ServerFQDNname\ShareName

Notes:

• In these examples, ServerName represents one of the following:
  • The FQDN name of the server
  • The IP address of the server
  • The NetBIOS name of the server
• This issue does not occur on a Windows XP-based client computer.