By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,870 Members | 1,236 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,870 IT Pros & Developers. It's quick & easy.

ASP.NET User Credentials

P: n/a
I have built an ASP.NET application which has <impersonate = true> in the WEB.CONFIG file. I have verified that the impersonation
appears to be working because the user.identity changes when I switch from true to false.

I then try to use ADO.NET to access an Excel file which is on a file server. I access the file using a connect string that contains
a UNC reference. This works fine on my Windows XP Pro computer, and it works on the target WIN2K server if the file is on the server
C: drive, but it doesn't work if the file is across the network; I get a permission error. I could understand that the ASPNET
account is not allowed to access a file on the network, but why should I get a permission error if the ASP.NET application is
impersonating my identity? Any suggestions appreciated.

Thanks,
Gavin
Nov 18 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Gavin, look further down in the newsgroup, there is a thread "IIS & SQL
Issues" by someone called "TipTop", yesterday's date, there are a number of
responses regarding the "double hop" issue, which is your problem.

"Gavin Jacobs" <no*********@inhell.com> wrote in message
news:un**************@tk2msftngp13.phx.gbl...
I have built an ASP.NET application which has <impersonate = true> in the WEB.CONFIG file. I have verified that the impersonation appears to be working because the user.identity changes when I switch from true to false.
I then try to use ADO.NET to access an Excel file which is on a file server. I access the file using a connect string that contains a UNC reference. This works fine on my Windows XP Pro computer, and it works on the target WIN2K server if the file is on the server C: drive, but it doesn't work if the file is across the network; I get a permission error. I could understand that the ASPNET account is not allowed to access a file on the network, but why should I get a permission error if the ASP.NET application is impersonating my identity? Any suggestions appreciated.

Thanks,
Gavin

Nov 18 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.