This is actually a complicated question. If your web server is on W2K3/IIS6, the short answer is that DMX runs in the context of the application pool service account associated with the DNN web site. Things become further complicated dependent upon which version of .NET you are running (1.1 or 2.0) and what Trust level you are running. However, I have not found any mechanism to allow an admin to permit only a specific trusted assembly to access (read/write) to a folder or share. I spent significant time with Microsoft PSS attempting to address that exact requirement under .NET 2.0.

So the best you can accomplish at this time is to isolate a specific web site (from other web sites on the same server), by using an application pool and unique service account, and allow that web site access to the desired folder/share. Since you indicated a UNC path, you would need to run the application pool under a Domain user account and give that account the permission required to the UNC share.

I know this probably leaves you with a lot of new questions, but they are really more IIS/.NET/Windows issues than a DMX issue.

Hope that sheds a little light on the question.

Rob Ralston

Thanks. That is what I had thought and tried to run under a Domain account but I was getting "Application Unavailable" so I thought I would post just to see if anyone else tried this.

I will go back and continue down my original path and figure out why I am getting that error.