Shirish Pargaonkar wrote: : > Is SMB Echo command the only way to determine whether to reconnect or not? The SMB Echo can only be sent from the client to the server. The server has no mechanism, within the SMB protocol, to "ping" the client. The Echo is used by the client as a way to test whether it is the connection that has failed or if the server is simply taking a very long time to respond to a particular request. > The assumption here is SMB server is unresponsive. > There could be other circumstances on the server box (or even client > box) that are slowing down the SMB server responses such as slow > network, slow network stack, memory pressure etc. Right. So how do you know whether it is the transport connection or the SMB server that is having trouble? In theory, the SMB server should answer the Echo right away, even if it is having other problems. > So server could be fine all along and yet client would ask for reconnection! If the network is slow, that's a transport problem. It's also why the 45 second timeout value is adaptable. See the earlier message in which I pointed to the sections in [MS-CIFS] that explain the 45 second timeout and point at the related KB articles. Chris -)----- -- "Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)----- crh@xxxxxxxxxxxx OnLineBook -- http://ubiqx.org/cifs/ -)----- crh@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
