Open Software Solutions

Considering the following scenario:

• On a Windows Vista-based or Windows Server 2008-based computer, you are running a client application that must connect to a server application. For example, you are running a Microsoft SQL Server client, a Microsoft Internet Security and Acceleration (ISA) Server client, or a Microsoft Office Excel client.
• The computer that hosts the client application is in a workgroup or in a different domain from the domain that hosts the server application.
• On the client computer, you have stored the domain credentials in Credential Manager.

  Note You can use the Stored User Names and Passwords feature in Control Panel to store credentials.

In this case, the client application that has to obtain domain credentials from Credential Manager cannot connect to the server application in the domain.

For example, assume that you store the domain credentials of an authenticated user in Domain A on a Windows Vista-based computer. This computer is in a workgroup. In this example, when you open SQL Server Management Studio, and you try to connect to a SQL Server installation in Domain A, you receive an error message that resembles the following:

Note This issue does not occur on a Windows XP Service Pack 2 (SP2)-based computer.

When a Windows Vista-based or Windows Server 2008-based client application tries to authenticate credentials, it looks for the target domain name together with a port number. The credential should be stored in the following format:

For example, if you run a SQL Server client, you must store the following information:

However, there is no provision to add ort_Number in Credential Manager.

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 the problem described in this article. 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:

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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, the computer must run one of the following:

• Windows Vista with Service Pack 1
• Windows Server 2008

Restart requirement

You must restart the 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 and Windows Server 2008 file information notes

The .manifest files and the .mum files that are installed in each environment are listed separately in the Additional file information for Windows Server 2008 and for Windows Vista section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

For all supported x86-based versions of Windows Server 2008 and Windows Vista

For all supported x64-based versions of Windows Server 2008 and Windows Vista

For all supported Itanium-based versions of Windows Server 2008

Additional file information for Windows Server 2008 and for Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and Windows Vista

Additional files for all supported Itanium-based versions of Windows Server 2008

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

For more information about how to manage stored user names and passwords, click the following article number to view the article in the Microsoft Knowledge Base:

For more information, click the following article number to view the article in the Microsoft Knowledge Base: