Hi Gal,
Thank you for posting.
As for the ASP.NET application deploying in two machines scenario, here are
some of my understanding and suggestion:
1. For IIS 5.X , the ASP.NET worker process is aspnet_wp.exe and the
default process identity is machine\aspnet account and the password is
controled by machine. also, we do not recommend that user manualy change
the account's password. Actually we can create a separate custom ASP.NET
process account, see the below msdn article:
http://msdn.microsoft.com/library/en...9.asp?frame=tr
ue
http://msdn.microsoft.com/library/en...01.asp?frame=t
rue
2. For SQL Server, since it is always be accessed remotly from ASP.NET
application, so if the ASP.NET application is not using impersonate, it
should always use the worker prcess account to access the remote sqlserver,
no matter the client user visit the page from local or remote client
machine. is your ASP.NET applicaiton using windows authentication and
impersonate?
Anyway, I suggest you turn on the SQL Profiler on the sqlserver machine to
check what's the account used to access the sqlserver and get denied...
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.)