If my IIS Web app tries to access SQL Server 2000 Developer DB on same PC, works okay. If it tries to access SQL Server 7 on three other PCs, works okay. But when I upgraded one of the SQL Server 7 to 2000 Developer, it cannot connect, with error: "Reason: Not associated with a trusted SQL Server connection." Query Analyzer can log in with that user-id okay. The user-id is known only by the DBs, _not_ by Windows (want it that way). How do I fix this?

ASP.NET web apps try to access the database as the ASPNET user - if using trusted connection, and assuming that you haven't twiddled with the application pool settings on your Win2k3 server.

I have answered this Q before. Please see - http://shrinkster.com/acv

Sahil Malik [MVP C#]
Author: Pro ADO.NET 2.0
http://www.winsmarts.com

Sorry, this suggestion did not help. I have 2 PCs running WinXP-Pro and one running Server-2003. IIS-6 only runs on Server-2003; XP-Pro runs IIS-5.1. It does not matter which one is running the Web app, it can see only that machine's SQL Server or a 4th PC's SQL Server 7.0.

That seems to be the key. What changed from SQL Server 7 to 2000 Developer? As I said, Query Analyzer has no problem seeing other PCs, so it must be possible.

Any ideas? I really need to know how to handle this, so I can sell my app.