Trusted_Connection defaulting to YES

  • I have a bit of a different problem regarding trusted_connection.  Does anyone know where the default for this value is stored?  Or how to change it?

    I have a DSN that is created using SQL Server Authentication, but when my application calls to Microsoft to pull the actual connection string, it gives the following:

    DSN=UAT_DB;UID=abcuser;APP=Appname;DATABASE=UAT_DB;Trusted_Connection=Yes

    Where is it pulling the Trusted_Connection setting from? 

    Some additional software settings: MDAC 2.6, SQL Server 2000, Client WS = WinNT4

    Thanks for your help..  Elizabeth

  • Hi Elizabeth,

    When connecting from a piece of custom software, i am accustomed to building the connection string myself, and then judiciously using the Trusted_Connection property as I need to, but my problem is where does EM and QA get this setting, which on my PC is obviously set to No? I think the answer to your question is the answer to mine. I suspect that it is in the Registry somewhere, but rather than searcing from top to bottom, I'm hoping that someone will be able to point us both in the right direction.

    Regards,

    Morpheus


    "See how deep the rabbit hole goes..."

  • it was setup when the connection was first defined. When EM was first registering it's connection to SQL Server, it was defined then. It's at that time that you could use a windows (integrated) or SQL Server(standard) security for the connection. In EM, you can delete the registration and re-register it using standard.

    QA can be done from File->Connection

  • Thanks for all the responses.  I discovered the reason for my problem.  Using MDAC 2.6 RTM, there is a bug where the driver will ignore any authentication settings in the DSN and automatically use NT Authentication.  (Microsoft Article ID: 279526)

    Elizabeth

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply