Hi,

I keep getting numerous requests from customers of our application
about how they can access data stored in other network locations. Most
of the time when they try this they get a message which states the
Directory could not be accessed.

On our test system here we are successfully able to access other
network data by adding the following line to the Web.config file

<identity impersonate="true" userName="DOMAIN\Username"
password="password"></identity>

However, in many customer sites, this still does not resolve the problem.

What other methods can I use to get ASP.Net to run as a different
network user, so that it can access network data ?

Thanks!

---

Request for Question Clarification by answerguru-ga on 06 Sep 2006 10:55 PDT

Hi snazbaz-ga,

Having experience the same problem before myself, I believe I know why
your users are having this problem.

Depending on how you are trying to provide your users access to
content on your network, security restrictions built into Windows may
prevent you from doing so.

Although impersonation is the only practical way of accessing network
content, I can provide you with the reasoning for why you can't (and
may not be able to) accomplish what you describe.

Let me know if you are interested.

Thanks,
answerguru-ga

The obvious that the domain and user name you are putting into the web
config file is not a administrator on your customers network domain
and as such cannot access the network drives.

You need to set the windows authentication to be that of the user
being logged on to the computer, and that will allow them to access
the network.

The obvious thind is that the domain and user name you are putting
into the web config file is not a administrator on your customers
network domain and as such cannot access the network drives.

You need to set the windows authentication to be that of the user
being logged on to the computer, and that will allow them to access
the network.

hi snazbaz,

i believe you should be able to access the network drive. you can try
the below configuration. if you have already gave it a try, just
ignore this.

<identity impersonate="true"/> in the web.config and select
Only Integrated Windows Authentication in the IIS website properties
(do not select anonymous access).

when the end user tries to login to the system, he will be prompted
with the windows domain name and password.

the access (read\write) will be granted to the logged in user
depending on his network credentials on the web server.

cheers,
sazid.