8><----snip----snip----snip---- I understand it is an issue with CIFS change/notify events and the way IIS was designed. 8><----snip----snip----snip----
I just wanted to clear up what might actually be happening here....
There were some change/notify issues in earlier versions of ONTAP that only IIS would expose but they've since been cleared up. If you're running Data ONTAP 5.3.6R2 or later (as documented in the IIS paper) along with the latest Windows/IIS patches *AND* have configured the cifs.max_mpx option on the filer (also documented in the white paper), the ASP caching problem should in most cases be resolved. However, there are a still few case where it is a problem. In those cases, the problem has to do with the MS redirector resetting. When the redirector resets, all pending change/notifies are lost. We don't believe this to be a problem with the filer but if you still experience the problem after configuring the cifs.max_mpx setting, please open a call with NetApp customer support.
For reference, here's a link to the white paper (which was updated in December in case you haven't looked at it in a while): http://www.netapp.com/tech_library/3078.html
Best Regards,
Paul Benn Network Appliance