Thanks for the help David. The article looks good and has
some good information. After going through it, I am still
having some problems, though. I'll go into a bit more
detail this time:
What we are trying to accomplish is to get our custom web
application to work over 5 IIS servers with the data
residing in one share location. (One of the 5 IIS servers
is a Domain Controller, in case that is relevant.)
I have an application pool setup to run as the same user
account that has full rights to the web data. (We'll call
the account "web".) I have the websites pointed to the
UNC path and connecting to these servers as "web". I have
created WebService Extensions to allow our custom .dll
files to run.
If the data is local, everything works fine. If I change
it to the UNC path, it's only our custom application it
cannot open. Standard .html and .asp files pull up fine.
My secure web directories are asking for authentication
and that is working fine, too.
I was just looking through the thread on "ISAPI filters
and IIS 6.0" that you had responded to, as well. It's
possible that this can relate somehow to my issues as well
and I am looking into that more now. Please, if you have
any other suggestions, they are greatly appreciated!
-JP
>> Stay informed about: IIS6, Custom App not working properly