You cannot access a network share on a Unisys MCP server from a Windows Vista-based computer by typing a UNC path that does not include the share name

Article translations Article translations
Article ID: 943451 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You have a server on a network that runs the ClearPath MCP operating system from Unisys.
  • 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 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 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 and ServerFQDNname represent one of the following:
    • The fully qualified domain name (FQDN) 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.

CAUSE

The Unisys MCP server does not support Remote Administration Protocol named pipes. Therefore, Windows Vista has to create a new connection to enumerate the share list. To do this, Windows Vista uses the user's logon credentials instead of the credentials that user types when they map the network drive. However, in this situation, the credentials that user types when they map the network drive are required. Therefore, this problem occurs.

In the same situation, Windows XP uses the credentials that user types when they map the network drive. Therefore, this problem does not occur on a Windows XP-based computer.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Vista, 32-bit versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Update.mumNot Applicable2,68008-Oct-200716:23Not Applicable
X86_015e3a0b972b27aef1a331b0abccc412_31bf3856ad364e35_6.0.6000.20695_none_64252ccd39bebc33.manifestNot Applicable69608-Oct-200716:23Not Applicable
X86_52806b255b2e1eb0721e4bb49cb9f230_31bf3856ad364e35_6.0.6000.20695_none_56834f844cfc9bc6.manifestNot Applicable70108-Oct-200716:23Not Applicable
X86_microsoft-windows-netapi32_31bf3856ad364e35_6.0.6000.20695_none_8b7b29781dcb6a10.manifestNot Applicable12,66308-Oct-200716:23Not Applicable
X86_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.0.6000.20695_none_89220400a6016cd4.manifestNot Applicable7,28808-Oct-200716:23Not Applicable
Netapi32.dll6.0.6000.20695425,98406-Oct-200702:58x86
Mrxsmb20.sys6.0.6000.2069557,85606-Oct-200701:08x86
Windows Vista, 64-bit versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_015e3a0b972b27aef1a331b0abccc412_31bf3856ad364e35_6.0.6000.20695_none_c043c850f21c2d69.manifestNot Applicable69808-Oct-200716:23Not Applicable
Amd64_250491a2663398a049bb8b675c8d8b2f_31bf3856ad364e35_6.0.6000.20695_none_43f05e7f785fbce9.manifestNot Applicable70008-Oct-200716:23Not Applicable
Amd64_2fe51f8fa16c5acdd1a08614f9c76528_31bf3856ad364e35_6.0.6000.20695_none_4067e84526d813d1.manifestNot Applicable70508-Oct-200716:23Not Applicable
Amd64_microsoft-windows-netapi32_31bf3856ad364e35_6.0.6000.20695_none_e799c4fbd628db46.manifestNot Applicable12,70108-Oct-200716:27Not Applicable
Amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.0.6000.20695_none_e5409f845e5ede0a.manifestNot Applicable7,30008-Oct-200716:27Not Applicable
Package_1_for_kb943451~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,79508-Oct-200716:23Not Applicable
Package_2_for_kb943451~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable2,69508-Oct-200716:23Not Applicable
Update.mumNot Applicable1,92508-Oct-200716:23Not Applicable
Netapi32.dll6.0.6000.20695606,72006-Oct-200703:53x64
Mrxsmb20.sys6.0.6000.2069578,84806-Oct-200701:18x64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Vista Service Pack 1.

MORE INFORMATION

For more information about named pipes, visit the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/library/aa365590.aspx
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates


The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Properties

Article ID: 943451 - Last Review: October 8, 2011 - Revision: 4.0
APPLIES TO
  • Windows Vista Enterprise 64-bit Edition
  • Windows Vista Ultimate 64-bit Edition
  • Windows Vista Business
  • Windows Vista Business 64-bit Edition
  • Windows Vista Enterprise
  • Windows Vista Ultimate
Keywords: 
kbautohotfix kbvistasp1fix kbexpertiseadvanced kbfix kbqfe kbHotfixServer KB943451

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com