I have to create a virtual directory under my existing DNN website virtual directory.

• Parent Directory points to a folder on local machine.
• Child Directory points to a fodler on a shared Computer.

Now if use this combo for a normal ASP.Net site, it works fine but in DNN it does not allows me to browse any page. Say for e.g I create a simple Hello html page and if I try to Browse it it does not works.  It does not seem to find web.config and gives the error.

Since child apps will always inherit Parent's web.config, I don't see why it should not find it. I even tried creating a local web.config on the shared folder, It also does not works.

Would appericiate your thoughts on this.

Thanks

Ashi

Hi Ian

I am trying to create a shared fodler where I will keep data to be accessed by my two web servers. So web1 and web2 both will point to this common folder for data and that way we can synchronise data changes.

I am not trying to create any site within a site. It is a just a virtual directory that should be accessible by UNC path. It sounds so simple when it is done in normal Dot Net framework and works fine but it somehow fails when we give it location as Shared computer.

I have tried creatign a virtual directory pointing to a shared folder on the same machine and using the "Share  located on another computer" option and giving the Network path pointing to shared folder in the same machine. This also works.

But the problem comes when I replace this network path by another machine path.

Thanks

Ashi

I am trying to browse using

http://10.xx.xx.xxx/Testshare/test.zip

where  http://xx.xx.xx.xxx is the parent DNN application.  This above mentioned URL works fine and I am able to open the file or for that mattre even a html page also as long as the "share on another computer" Network path points to Shared folder on the same machine.

I also tried

        ** giving same permissions to the shared fodler on external machine

       ** creating identical users in both machines having same password.

Then adding these users to the permissions log and givign them full rights.

      **  tried enabling Parent Path under Configuration of parent directory

The funny thing is it works so smoothly with regular .Net site :)