Hi Metze, I am unable to reproduce the reported behavior. Please note that the Node being used for witness registration must be available for expected behavior. For example, if you rely on stopping SOFS role to simulate disconnect, the witness node becomes unreachable. So there won't be an unregister call coming from client.
Using software based mechanisms to kill the TCP connection for the SMB session will cause a quick recovery (transient network connection recovery). So it wouldn't involve witness server sending any notifications to client as Nodes are online, shares didn't move. Temporarily pausing VM to simulate the unavailability of Node does simulate the expected behavior i.e. witness server notifies client so that Unregister event can be sent from client and I see that happening. Perhaps you are using a different mechanism to reproduce the issue ? Please share your thoughts. 3.2.7.1 Handling a Network Disconnect ... If Connection.Dialect belongs to the SMB 3.x dialect family and if Session.TreeConnectTable is empty in all sessions in the Connection.SessionTable for which Connection.ServerName matches the server name, the client SHOULD invoke the event as specified in [MS-SWN] section 3.2.4.3. Question 5: I don't see this happening from a Windows Server 2022 acting as client. The witness registration stays until a reboot. There's also no new witness registration after a reconnect to a different ip, which means that the smb connection and witness connection may stay on the same server ip address, which means there's no benefit from it. Can you please update this with a product behavior note reflecting the reality with all Windows versions. Regards, Sreekanth Nadendla Microsoft Windows Open Specifications
_______________________________________________ cifs-protocol mailing list cifs-protocol@lists.samba.org https://lists.samba.org/mailman/listinfo/cifs-protocol
