TheWizardofInt
Junior Contributor
I create a web service that a .Net web site needs to connect to
For it to work, it needs to connect to another computer on the domain where it resides, in someone's office, behind a firewall, connection using static IP, and read a file.
So, for example, the Web Server in the office is Web_Server, and it needs to read c:\apps\myfile.txt on Joes_PC
This works in the test environment in my office. 1/2 the time when I deploy it, it doesn't. It returns an error for "I cannot get into that file", which makes me say 'Rights issue."
ASPNet as a domain user has rights to the file. I have reconfigured .Net security on both PC's to allow access on the Intranet
Should I be installing the dotnetfix to the Domain Server in order for it to handle the IUSR? I don't think that this is the problem, as we can create an ASPUser user, put it in the Admin group, and then reset Machine.Config to impersonate ASPUser, and it will still not have access.
For it to work, it needs to connect to another computer on the domain where it resides, in someone's office, behind a firewall, connection using static IP, and read a file.
So, for example, the Web Server in the office is Web_Server, and it needs to read c:\apps\myfile.txt on Joes_PC
This works in the test environment in my office. 1/2 the time when I deploy it, it doesn't. It returns an error for "I cannot get into that file", which makes me say 'Rights issue."
ASPNet as a domain user has rights to the file. I have reconfigured .Net security on both PC's to allow access on the Intranet
Should I be installing the dotnetfix to the Domain Server in order for it to handle the IUSR? I don't think that this is the problem, as we can create an ASPUser user, put it in the Admin group, and then reset Machine.Config to impersonate ASPUser, and it will still not have access.