On 04/20/98 04:38:04 you wrote:
Mike Patchen - Verio Southern California wrote:
This is a bug in IIS. MS and netapp are aware of it. Frontpage also has a bug where all content has to be on local disk so we cannot use our filer on these accounts. MS says this will be fixed in the FP99 release.
We had the exact same problems you describe.
-Mike Patchen Verio Southern California
On Fri, 17 Apr 1998, Jimy Liu wrote:
But I think I did not use FrontPage. And if I use other PC(win95) as NT's network drive running IIS. It worked fine. Why Netapp Not ? MS may say "We can work with Normal network drive like win95. NetApp filer may be not Normal".
It is not unusual for Microsoft to violate their own spec. I don't know specifically what is wrong in IIS, but probably the filer is advertising something perfectly reasonable (that win95 doesn't), but IIS isn't handling it correctly. If Microsoft says this is a problem with IIS, then I see no reason to doubt them. (Yes, they may initially accuse Netapp, but the impression I am getting is that they aren't doing so now.)
About two month ago, my customer ran Notes server on NT using NetApp filer => Notes boot Fail . If she ran Notes server on this NT using another NT's disk as network drive => Notes boot Success. Again why filer can't ? (ps: I hope to resolv IIS with filer first )
I know these sorts of things happened in earlier versions of the filer CIFS software. Whether or not it happens now is hard to say. I would upgrade your filer software, try it, and if it still doesn't work, contact Netapp so they can open a bug on it.
Bruce