We have an ASP.NET 3.5 application running on Windows 2003. For migration purposes this application connects through ODBC to a very old version of SQL Server 4.21. It always worked until one day stop to work (server doesn't exists or access denied) on all the servers. After a week of research we realize that the problem is the account that run the application pool used in the web application (network service), if we change this account to "local service" or "local system" the connection works, but with these account many other problems appear. with "local system" account all works, but we think is not secure to use an account with admin privileges.
The goal would be:
Maybe we need to grant some privileges to an odbc library or something like that, maybe some security update from windows update was causing the problem.
Some clues:
Any thoughts?
You can connect to SQL running as the network service account. On the SQL end, make sure that you have granted access to the DB for "\\$". If you are in domain EMEA and the machine's name is "machine1", then the user to grant access to is "EMEA\\machine1$".
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.