🚀 go-pugleaf

I have sort of a unique situation here, I have written an ISAPI DLL using
BCB 5 Ent./SP1 w/ informal ADO patch 14080, MDAC 2.6, SQL Server 6.5, and
IIS 4 on NT Server 4 SP6a.

My DLL connects fine to a SQL Server development DB within my own subnet -
Network A (e.g., Network Neighborhood), but I have trouble connecting to our
production machine.  Our production DB machine has 2 networks cards,
straddling 2 networks (Network A and Network B).  In that machine's setup,
it is a member of the Network B domain.

I wrote a small test app to test the ADO connection and read data from the
DB.  I can run this on my web machine on Network A and pull in data with no
problems.

However, when my DLL tries to connect to the DB (using the EXACT same
connection string as my test app), the Web server comes back with this
error:

Internal Server Error 500
----------------------------------------------------------------------------
----
Exception: EOleException
Message: Login failed- User: _ Reason: Not defined as a valid user of a
trusted SQL Server connection

I am using a specific username and password in my connection string.

I am wondering if the problem is that the web server is run as a service,
which is what is running my DLL.  And this is the application that is trying
to connect to the DB machine residing (essentially) in another domain.

Does any of this make sense to anyone?  I'm not really that familiar with
this aspect of NT or SQL server security issues.  Do I need to make changes
to SQL Server or Windows security?

Any help would be greatly appreciated.  Thanks,

Rob Clawson