If the connection from the WAN Accelerator to the origin SMB server is down (ie the origin SMB server is down), shouldn't the WAN Accelerator realize that, and then not be responding to SMB echoes (at least responding as though it was the origin SMB server)? -----Original Message----- From: samba-technical-bounces@xxxxxxxxxxxxxxx [mailto:samba-technical-bounces@xxxxxxxxxxxxxxx] On Behalf Of Volker Lendecke Sent: Monday, December 06, 2010 12:17 PM To: Christopher R. Hertel Cc: Steve French; cifs-protocol@xxxxxxxxx; samba-technical@xxxxxxxxxxxxxxx; Jeff Layton; linux-cifs@xxxxxxxxxxxxxxx Subject: Re: cifs client timeouts and hard/soft mounts On Mon, Dec 06, 2010 at 12:54:30PM -0600, Christopher R. Hertel wrote: > There are a lot of companies out there that do WAN acceleration and each of > them do things differently, so there is no good answer to your quite > rational question. Some of the vendors are very focused on "just like the > real thing" behavior while others are willing to compromise behavior in > favor of acceleration. > > The best-known product in this market would be Riverbed. BlueCoat is > another, I think. Sorry, but if a WAN accelerator does not have the smarts to see that if a client sends smbechos, it is in trouble, then that WAN accelerator is just broken. It does not necessarily need to send these echos across the WAN link, but it must trigger its own server liveliness check at this point. Volker -- 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