Steve, I've done a lot of consulting work for companies that create this sort of proxy. Companies like Peribit (now part of Juniper), FineGround (now part of Cisco), and Certeon (now part of history, I think). You are correct. A WAN accelerator that does proxy caching might very well respond to an SMB Echo and various meta-data requests without actually sending those requests to the "real" server. If the link is down, or if the real server is down, the proxy may still respond to some SMB messages. To some extent, that is a problem inherent in the use of WAN accleration systems. Question (for which I do not have an answer): How much work do you want to do to make their intentionally broken model work? WAN accelerators are actually cool technology. I like them, but I also know (and most of the companies that make them know) that there are inherent problems when proxying SMB servers. Chris -)----- Steve French wrote: > On Sun, Dec 5, 2010 at 10:34 PM, Volker Lendecke > <Volker.Lendecke@xxxxxxxxx> wrote: >> Hi! >> >> On Sun, Dec 05, 2010 at 08:16:46PM -0600, Steve French wrote: >>> I am more worried about firewall rule changes and similar events >>> than about broken servers - but the idea of waiting forever on stat >>> to a server that is never going to respond seems odd. >> That would be a strange fw rule that allows SMBEcho but not >> other SMB requests. I think if someone puts up such a silly >> rule, some pain is deserved :-) > > Aaah - remember the proxies that cut out "chatty" smb traffic by > responding on behalf of remote servers in the interest of optimizing > traffic over slow links :) > > -- "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
