You have a volume mount point on a network share. In Windows Vista or in Windows Server 2008, when you call the GetVolumePathNameW function on the UNC path of the volume mount point to retrieve the specified mount point path, the function returns only the path of the network share. However, you expect the function to return the mount point path.

In Windows XP or Windows Server 2003, the mount path is returned as expected.

For example, you have a network share whose UNC path is \\Server\Share. In the network share, you have a volume mount point that has the UNC path \\Server\Share\MountDrive. When you pass the UNC path \\Server\Share\MountDrive\SubDir to the GetVolumePathNameW function to retrieve the mount point path, the function returns \\Server\Share. In Windows XP and Windows Server 2003, the function returns \\Server\Share\MountDrive.

On a Windows Vista-based or Windows Server 2008-based computer, you try to access a network share by typing the path of the share in the Run box. However, it may take more than 10 seconds for the network share to open in Windows Explorer.

For example, in the Run box, you type the universal naming convention (UNC) path of the share, such as \\ServerName\ShareName. When you do this, it takes the Windows Explorer more than 10 seconds to open the share.

This issue occurs if the firewall of the server on which the share resides blocks traffic on port 80.

When you use Windows Internet Explorer 7 to open a file that has a local file path or a UNC file path, session cookies may be lost after later operations. These later operations may include opening a new window or closing a new window.

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.

When you try to connect a Windows Vista-based computer to a network printer whose name is not a valid Universal Naming Convention (UNC) path, the connection fails.

This problem affects some third-party printers. If a third-party printer provider does not use a UNC path to name a printer, you cannot connect the computer to the printer.