I'm creating the administration module of the my application. I started by using my local machine as the web server. Currently, the application contains functionality that will: move a file to a server on the network, delete a file from the server on the network, and create a file on the server on the network. All of these functions worked beautifully on my local machine.
Now, I have moved my application from my local machine to the live web server for further testing. All of my functionality, at first, did not work. I would receive "Access denied" messages -- hence, a permission problem. (Keep in mind that there are two separate servers on the network that are used for IO operations in this app)
The network admin and I started at the first logical place -- folder permissions on both of the servers. To make a long story short, we set "Full Control" for "Everyone" on the one directory for server 1. This actually resolved the problem creating, moving, and deleting of files through my app. (Although, not the best solution, obviously) However, when setting the permissions for the other server, (and setting them identical to the first), the application still gets "Access denied" errors.
Can someone throw some suggestions my way, as to what permissions need to be set on these directories to work properly? I'm thrown off by the fact that it worked when my local machine acted as the web server, but not on the live web server. I also confirmed that the IIS settings for both my machine and live web server applications were identical. (Although my machine is running IIS 6, and the live server is 5 I believe)
Thanks!
IIS 5 uses ASPNET to do work - IIS6 uses Network Authority
check outhttp://asp.net/faq/AspNetAndIIS6.aspx
On the servers - you can edit the Local Security Policy to log failed logons - and then you can see the account being used
Hope that Helps
I apologize...my local machine account is using IIS 5 and the web server is 6. I'll check out that article...
The server that is not allowing me to add/move/delete files does not have .NET installed. Stupid question, but is that what's causing the problem here? Do I need to install .NET and then add an ASPNET group to the directory?
Lots of possible issues here. First is how you're authenticating in the app. If you use anonymous access, the user has changed, and may be a network account if the server is a domain controller. Remember that the accounts on your workstation were likely local accounts and you would need to change the account for your app or duplicate that account on the network.
My guess is you're authenticating users since giving the Everyone group full control fixed the access. They may not need Full Control, and Modify might eb enough on the folders. You may even be authenticating without realizing it since IE will pass authentication credentials if the network is seen as being local or in the intranet security zone. Remove Windows Integrated authentication in your web site if you don't intend to authenticate.
Might try Filemon from Sysinternals.com to check access on specific files. This can help quite a bit on the server to server issues.
Jeff
0 comments:
Post a Comment