TADOConnection question - In connecting to an MS SQL Server (2014, if it matters) that's got security locking it down to specific machine ID and IP and preventing Windows Authentication, how do you tell it to do Server Authentication? It seems to work at run-time for inexplicable reasons, but I can't get it to connect at design-time. It gives this error:

-
TADOConnection question - In connecting to an MS SQL Server (2014, if it matters) that's got security locking it down to specific machine ID and IP and preventing Windows Authentication, how do you tell it to do Server Authentication? It seems to work at run-time for inexplicable reasons, but I can't get it to connect at design-time. It gives this error:

Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

Well, yeah, because it's configured to accept SERVER Auth ONLY!

There's no way to enter Server Auth creds into the standard connection dialog that comes up. What's the workaround?

Comments

  1. Agustin OrtuJanuary 7, 2017 at 1:00 PM

    /sub

    ReplyDelete
  2. Jeroen Wiert PluimersJanuary 8, 2017 at 1:25 AM

    from my SQL Server days in .NET, I remember the connection string for SQL Server username/password authentication to be like these:

    "Persist Security Info=False;User ID=***;Password=***;Initial Catalog=DatabaseName;Server=ServerName"
    "Persist Security Info=False;User ID=***;Password=***;Initial Catalog=DatabaseName;Server=ServerName\InstanceName"

    I guess that's what "Server Auth" needs. Does it work for you?

    ReplyDelete
  3. David SchwartzJanuary 8, 2017 at 7:49 AM

    I'll try it Monday.

    ReplyDelete

Post a Comment