June 13th, 2003, 07:57 AM
I have an ASP page that uses a COM componenemt on a Win2000 server.
The same server contains my SQL Server 2000, which the COM object is querying on.
I use a constant login/password to login into the SQL Server, so it shouldn't matter which domain user is using the page.
It works fine for every user -=that is defined in the Win2000 computer Admins list=- , it doesn't work at all for users that are not (Connection failure)....
I am not sure why, since how I see it, it shouldn't matter to the SQL Server which user is trying to login (since I use the same constant user/password for all of them...).
It might be either an IIS or SQL Server problem (or maybe even Win2000 related), Anyone ever encountered such an issue?
June 24th, 2003, 08:19 PM
What sort of errors are being generated? Is the com object performing your authentication?
July 10th, 2003, 10:06 PM
I've ran into something similar....
I've seen some mssql servers be set up to grab NT credentials by default, ergo ignoring all sql login's passed to it (constant or not) and using the NT credentials. I'm not sure what that admins part you were talking about means really.
Win2000 computer Admins
are those all admins on doman X? or are those admins local NT grouped on that server only? If it's domain X, only domain X has access to the db as you say, and other users besides domain X try and access it and get rejected due to the NT credential login which has precedence over SQL login. Maybe that's the cause....