Hi kimpton,
Thanks for your response. Regarding on your further description, I've done
some tests on my side, and found that the problem is acutally caused by
permission issue. Since the sub web folder is point to a remote shared
folder. And the ASP.NET will use the default processAcount (machine\aspnet
for iis 5 or networkservice for iis6) to do the folder monitor. However,
since the default process account is a local account, it'll failed on logon
remote mahcine no matter the remote folder has been grant "Full Control"
to everyone or not. That's the problem you encountered. (You can find the
error in the remote machine's eventlog).
Currently, I think you need to specify another Account which can be
authenticated on the remote machine as the local's ASPNET worker process
account, you can use either a
Domain User Account or an mapping local account( which exists on both the
local and remote machine and have same username and passworld).
Then, use the following means to speicify it as the ASP.NET's process
account:
1. In machine.config, find the <processModel> element and change the
"userName" and "password"
attributes to the certain account's value
2. You can also specify it for only a certain web application(rather than
the whole machine) in the web.config via the <identity impersonate="true"
userName=".." password=".."/>
This is more recommended.
In addition, do make sure that the account has powerful permssions on the
local machine( to run asp.net application, you can make it in the
administrators group) and has sufficient control to the remote folder on
the remote machine. and the following tech article is also helpful:
#How To Create a Custom Account to Run ASP.NET
http://msdn.microsoft.com/library/de...us/secmod/html
/secmod15.asp
Thanks.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx