An SMBv2 session is reset incorrectly if FindCloseChangeNotification function is called immediately after the FindFirstChangeNotification function is called in Windows Server 2008 R2 , in Windows Server 2008, in Windows Vista or in Windows 7
Consider the following scenario:
- You share files on a computer that is running Windows Server 2008 R2, Windows Server 2008, Windows 7 or Windows Vista acting as the file server.
- You run an application to monitor changes of the shared files and folders on the computer from a SMB client computer by using the Server Message Block version 2 (SMBv2) protocol.
- The application calls the FindFirstChangeNotification function and then immediately calls the FindCloseChangeNotification function to cancel the previous change notification.
In this scenario, the TCP session of the SMBv2 session is reset incorrectly after 4 minutes. Therefore, you may experience data loss or file corruption if you transfer data or files during the SMBv2 session.
For more information on this issue, including potential causes, workarounds, and resolutions, see: Microsoft KB Article KB2493869.