An OpenAFS share cannot be accessed on a Microsoft Windows XP-based client if the client is not using the network to access the share. A Network Monitor trace shows the following error code: Additionally, events in the Security logs may show that Kerberos tickets for the Common Internet File System (CIFS) server cannot be obtained.

Back to the top

Hotfix information

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
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: 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

You must be running Windows XP with Service Pack 1 or Windows XP with Service Pack 2 to install this hotfix. Additionally, you must follow these steps.

1.

Disable the loopback check on the client. a. Click Start, click Run, type regedit, and then click OK. b. In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa c. Right-click Lsa, point to New, and then click DWORD Value. d. Type DisableLoopbackCheck, and then press ENTER. e. Right-click DisableLoopbackCheck, and then click Modify. f. In the Value data box, type 1, and then click OK. g. On the File menu, click Exit. h. Restart the computer.

2.

Configure the client to use the loopback authentication service to access the OpenAFS share. a. Click Start, click Run, type regedit, and then click OK. b. In Registry Editor, locate and then click the following subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 c. On the Edit menu, point to New, and then click Multi-String Value. d. In the Name column, type BackConnectionHostNames, and then press ENTER. e. Right-click BackConnectionHostNames, and then click Modify. f. In the Value data box, type the host name or the host names for the OpenAFS shares on the computer, and then click OK. Note Type each host name on a separate line. g. On the File menu, click Exit.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 XP, all versions

File name	File version	File size	Date	Time
Lsasrv.dll	5.1.2600.2908	726,016	14-May-2006	08:30
Msv1_0.dll	5.1.2600.2908	132,608	14-May-2006	08:30

Back to the top

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

Back to the top