visual studio 2017 sql server windows authentication

I've also tried additional string options such as Trusted_Connection (tried true and false) and Integrated Security=SSPI.Īll the server connection settings are correct (allow remote connection, ports, both Windows and SQL authentication allowed), and I can connect to the server on SSMS using the username and password just fine.Īssuming my settings are correct (there's bound to be something wrong somewhere), doesn't this defeat the point of using a SQL user login if I can't log in remotely? Anyway, any help is appreciated. The connection string is (details omitted and edited for readability): Share Follow answered at 14:24 Dave Markle 94.3k 20 146 169 1 Sergio Tapia: use the Integrated Security flag. Log in as an Administrator on the box, connect using Integrated Windows Authentication, and you should be a system admin. Fixed a bug that ssis project targeting SqlServer 2019 execute will fail if the machine install sqlserver 2019 at the same time. the login is from an untrusted domain and cannot be used with windows authentication. You probably should not connect using Sql Server Authentication. Fixed a bug that testing connection in OData connection manager failed when the authentication type is Microsoft Dynamics CRM online and target server version is SQL Server 2016 or SQL Server 2017. As soon as it is on one of the others outside the domain, including non-domain accounts on my machine, this error occurs.

On my development machine the connection string works perfectly fine and isn't using Windows authentication. I've been trying to solve this for several days now.

I have a C# application that connects to a SQL server with SQL authentication, but the machines that are to be using it aren't on the domain.

Visual studio 2017 sql server windows authentication