Hi Ralph, Thanks for your question. I've created case number 2509250040006209to track this issue. Please leave the number in the subject line and use reply all your correspondence. One of our engineers will contact you soon.
Best regards, Michael Bowen Sr. Escalation Engineer - Microsoft® Corporation  -----Original Message----- From: Ralph Boehme <[email protected]> Sent: Thursday, September 25, 2025 7:46 AM To: Interoperability Documentation Help <[email protected]> Cc: [email protected] Subject: [EXTERNAL] MS-SMB2: Reconnect of second disconnected PH on a file fails if contending open broke H lease Hi dochelp! I'm sorry, but I just ran into another issue I fail to understand... :) Scenario: Reconnect of second disconnected PH on a file fails if contending open caused a break of the H lease. Server: Windows 2025, Fileserver for General Use Client: smbtorture CG := Create Guid LK := Lease Key 1. Client 1: open file with PH, lease=RWH, LK=X, CG=Y 2. Client 1: another open on the same file with PH, lease=RWH, LK=X, CG=Z (same LK as in 1) 3. Disconnect 4. Client 2: content disconnected handles with another open that triggers a break and is suspended 5. Client 1 reconnects 6. Client 1 reconnects first PH 7. Server sends lease break for LK=X to NONE to client 1 8. Client 1 acks lease break 9. Client 1 attempts to reconnect second PH but this fails with STATUS_FILE_NOT_AVAILABLE In my understanding 9 should not fail and in my implementation of PH in Samba it succeeds. Am I missing anything in the docs why 9 should fail? In my testing with various lease levels and different sharemodes and access masks of the contending open, the pattern seems to be that the second reconnect alway fails if the contending open triggered a H lease break. Thanks! -slow _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
