|
Subject:
|
ASP.NET and directory security
|
|
Posted By:
|
quintesv
|
Post Date:
|
9/26/2006 5:59:53 AM
|
Hi all,
I come from a win forms background, and am building a web site that needs to interface to a FOXPRO database (DBF files). My problem is as follows:
I have created a virtual directory on the same machine as where the DBF files are located. I have created a share for the DBF files, and I've given the <SERVER>\ASPNET account access to this folder where they are residing.
My code to connect to the folder where the DBF files are located is basically as follows:
1. Connect to a DLL which authenticates our users according to <USERNAME>, <PASSWORD> and <DIRECTORY> where the DBF files are.
2. IF the connect is successful, continue processing any queries through Visual FoxPro OLEDB PRovider 8.0 to the data.
This works fine if I am testing on the machine locally, i.e the web project is opened on the machine - in this case my development machine - and it connects to the Foxpro Database folder - also on my development machine - successfully.
If I try to connect to that same database and project from another machine I get security warning, " the specified file does not exist" . I use System.IO.File.Exists to see if I can access one of the files in the folder specified, but get access denied.
What do I need to setup in terms of permissions to access a FOLDER on another machine via asp.net, or what do I need to do?
Thanks in advance
Q
|
|
Reply By:
|
dparsons
|
Reply Date:
|
9/26/2006 9:41:56 AM
|
Ok, let see if i understand this correctly.
The application you created you have on your development machine and is executing fine when you run the application from that machine.
Now, when you go to another machine it is not working. Are you moving the entire application to that second PC or are you calling the application from your development machine?
As far as security goes you will have to grant permission to the ASPNET user account which is normally server\IWAM_[machinename].
hth
--Stole this from a moderator
I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.
|
|
