Error message when you try to access a WebDav shared file from a Windows Vista-based computer: "System error 1397 has occurred. Mutual Authentication failed"
Consider the following scenario:
- On a Windows Vista-based computer, you map a drive to a Web Distributed Authoring and Versioning (WebDav) shared file that is located on an Internet Information Services (IIS) 6.0 server. To map the drive, you use the following command:NET USE X: HTTPS://SERVERNAME/SHARENAMENote The X placeholder represents the letter of the drive that you want to map to the shared resource. The SERVERNAME placeholder represents the server on which the shared file is located. The SHARENAME placeholder represents the shared file to which you want to map the drive.
- You select a certificate when you are prompted, and you click OK to confirm.
System error 1397 has occurred. Mutual Authentication failed. The server's password is out of date at the domain controller.This problem may also occur when you use the HTTPS protocol to try to access a WebDav shared file on a Java-based WebDav Server.
- This problem occurs if mutual authentication is enabled on the server that is running IIS 6.0 server.
- If you use the HTTP protocol instead of the HTTPS protocol to access the WebDav shared file, this problem does not occur.
- After the dialog box appears, if you do not click OK to confirm the selection of the certificate within 10 seconds, this problem does not occur.
Service pack informationTo 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 informationA 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.
PrerequisitesNo prerequisites are required.
Restart requirementYou have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other previously released hotfixes.
Registry informationTo use one of the hotfixes in this package, you do not have to make any changes to the registry.
File informationThe 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, x86-based versions
|File name||File version||File size||Date||Time||Platform|
|Package_1_for_kb941298~31bf3856ad364e35~x86~~220.127.116.11.mum||Not applicable||1,783||10-Aug-2007||17:44||Not applicable|
|Package_2_for_kb941298~31bf3856ad364e35~x86~~18.104.22.168.mum||Not applicable||1,999||10-Aug-2007||17:44||Not applicable|
|Update.mum||Not applicable||2,116||10-Aug-2007||17:44||Not applicable|
|X86_45274763ca619b4f51a34200270af390_31bf3856ad364e35_6.0.6000.20658_none_343fec66b0566d0c.manifest||Not applicable||709||10-Aug-2007||17:44||Not applicable|
|X86_a1efd5459b4a9e64bd76f524f81fdbd2_31bf3856ad364e35_6.0.6000.20658_none_56196fc045bd5eb4.manifest||Not applicable||693||10-Aug-2007||17:44||Not applicable|
|X86_microsoft-windows-rdbss_31bf3856ad364e35_6.0.6000.20658_none_584a26bf7d81d7b3.manifest||Not applicable||7,288||10-Aug-2007||17:44||Not applicable|
|X86_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.0.6000.20658_none_539b18afcfca0ba0.manifest||Not applicable||7,339||10-Aug-2007||17:44||Not applicable|
Windows Vista, 64-bit versions
|File name||File version||File size||Date||Time||Platform|
|Amd64_86a0f703e315a7024dc636bab6dfad0c_31bf3856ad364e35_6.0.6000.20658_none_e7bb1cc1b9938584.manifest||Not applicable||697||10-Aug-2007||17:44||Not applicable|
|Amd64_944b14087ea68bec6a79838c0d7f2ee8_31bf3856ad364e35_6.0.6000.20658_none_f9342fdb1e46c2a3.manifest||Not applicable||1,066||10-Aug-2007||17:44||Not applicable|
|Amd64_microsoft-windows-rdbss_31bf3856ad364e35_6.0.6000.20658_none_b468c24335df48e9.manifest||Not applicable||7,548||10-Aug-2007||18:05||Not applicable|
|Amd64_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.0.6000.20658_none_afb9b43388277cd6.manifest||Not applicable||7,369||10-Aug-2007||18:05||Not applicable|
|Package_1_for_kb941298~31bf3856ad364e35~amd64~~22.214.171.124.mum||Not applicable||2,020||10-Aug-2007||17:44||Not applicable|
|Package_2_for_kb941298~31bf3856ad364e35~amd64~~126.96.36.199.mum||Not applicable||2,011||10-Aug-2007||17:44||Not applicable|
|Update.mum||Not applicable||2,130||10-Aug-2007||17:44||Not applicable|
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.
If you use the Open dialog box in a 2007 Microsoft Office program to access a file by using the HTTPS://SERVERNAME/SHARENAME URL, a dialog box appears. After you select a certificate, and you then immediately confirm the selection, the file will be displayed successfully. You will have read-only permission on the file.
If you use the Open dialog box in a Microsoft Office 2003 program to access a file by using the HTTPS://SERVERNAME/SHARENAME URL, the dialog box that appears differs from the dialog box in a 2007 Office program. After you select a certificate, and you then immediately confirm the selection, the file will be displayed successfully. You have read and write permissions on the file.
If you use the same URL in Windows Internet Explorer to access a file, the dialog box will not be displayed. However, you can access the file successfully.
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 updatesThe SRV_CALL structure is in the server call context. This structure provides the abstraction for a remote server. For more information about the SRV_CALL structure, visit the following Microsoft Web site:
For more information about WebDAV, visit the following Microsoft Web sites:
324274 How to configure IIS Web site authentication in Windows Server 2003
ERROR_MUTUAL_AUTH_FAILED, error 1397
Article ID: 941298 - Last Review: 10/08/2011 15:04:00 - Revision: 3.0
Windows Vista Enterprise 64-bit Edition, Windows Vista Home Basic 64-bit Edition, Windows Vista Home Premium 64-bit Edition, Windows Vista Ultimate 64-bit Edition, Windows Vista Business, Windows Vista Business 64-bit Edition, Windows Vista Enterprise, Windows Vista Home Basic, Windows Vista Home Premium, Windows Vista Ultimate
- kbautohotfix kbvistasp1fix kbexpertiseadvanced kbfix kbqfe kbHotfixServer KB941298