Yes, there was a lot of discussion of W2K and disk caching some time ago. The upshot seems to be: make sure all W2K machines in the loop (workstations and server, if applicable) are running Service Pack 2.
http://www.levelextreme.com/wconnect/wc.dll?FournierTransformation~2,15,540525At a network level, you can consider disabling opportunistic locking on both server and workstations:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q296264http://support.microsoft.com/default.aspx?scid=kb;EN-US;q126026http://support.microsoft.com/default.aspx?scid=kb;EN-US;q306981http://support.microsoft.com/default.aspx?scid=kb;EN-US;q224992Notwithstanding all of the above, there is no reason to be uneasy about a properly implemented cache; the CPU you're using to read this message no doubt implements one and you've never seen it fail or, I bet, even thought about it.
The key phrase of course, is, "properly implemented". Maintaining cache coherency in a network file system is not trivial.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
