Your network connection may be reset when you try to perform a file operation on a remote Windows Server 2003-based computer

When you perform a file operation on a remote Microsoft Windows Server 2003-based computer, such as saving a file from a local Windows Server 2003-based computer, the remote computer may reset the network connection during the operation.

For example, when you perform a Microsoft SQL Server database-backup operation on the local server, you can specify a location on the remote server to store the backup file in. However, the backup operation may not be completed successfully in this scenario. Additionally, events that are similar to the following may be logged in the Application event log:

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: Date
Time: Time
User: N/A
Computer: Computer Name
Description:
Application popup: Windows - Delayed Write Failed: Windows was unable to save all the data for the file \\Server.domain.name\BackupFolder\MyBackUp.bak. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: Date
Time: Time
User: User Name
Computer: Computer Name
Description:
18204 : BackupDiskFile::CreateMedia: Backup device '\\Server\BackupFolder\MyBackUp.bak' failed to create. Operating system error = 64(The specified network name is no longer available.)

This problem occurs if a client Server Message Block (SMB) redirector connection on the Windows Server 2003-based computer that is running the SMB service is not initialized correctly. When a new client or the server itself creates a new SMB session to the server that is running the SMB service, the server may not correctly determine whether the SMB session request is made by the new client or by the existing client. If the server incorrectly determines that the existing client made the new SMB session request, it resets the network connection for the existing client.

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: 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 do not have to 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 tool in Control Panel.

Windows Server 2003 64-bit editions

Windows Server 2003 32-bit editions

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

For additional information about standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base: