Sql-server – SQL Server 2000 + ASP.NET: Login failed for user ‘NT AUTHORITY\ANONYMOUS LOGON’

I would test with an explicit account that I set up on the local computer and put into the IIS app as the anonymous user. That way you can test it from SSMS or VS and be sure that you can connect to the server and database without issue.

Once that is working, or if it's not, you can debug where in the ASP side it might be failing. The SQL side is simple, though I've not tried the Network Service account. Should be no reason it doesn't work, but I haven't seen anyone use it.

The more secure method uses Windows authentication. This will allow you to write your application without a password included in any of the connection strings or config file.

One each system you will create a user account. This should not be an administrator account, just a regular user account. One both systems create the user with the same name and password.

Now on your IIS system edit the application pool settings. Change the identity to run as the user account that you just created. At this point you will need to type in the password for the user.

On the SQL server create a login account that is associated with the Windows use account that you have created. You can use the normal SQL Server permissions to grant/deny the actions that your application requires.

Now in your application connect to the SQL server using integrated security. The app pool user will be used when making the SQL connection.

No password in your config or app and a secure database connection!