How to fix connection string between two domains

Question

0.00/5 (No votes)

See more:

Problem Description:

I have Windows application called appTest (environment: Windows 8.1; Visual Studio 2010; C#).
This application is connected to SQL Server 2008 located in the same domain as my machine, and it runs successfully. In app.config file connection string looks like that:
<add name="strConn" connectionString="Data Source=mccsql1;Initial Catalog=dbTest;Persist Security Info=True;User ID=sa;Password=pwd1" providerName="System.Data.SqlClient" />

Now I changed connection string like that:
<add name="strConnTest" connectionString="Data Source=Domain2ServerName;Initial Catalog=dbTest;Integrated Security=true;" providerName="System.Data.SqlClient" />

I used that type of connection string because client setup my credentials with Windows Authentication.

Then I created setup project and moved appTest.exe and appTest.msi files into the Server2 located in client domain (environment: Windows Server 2012; SQL Server 2012).

Again application appTest runs successfully (both – application and SQL Server again in the same domain Domain2).

Question:
Now I have a request to run my application (Domain1) with client’s SQL Server 2012 (Domain2) using VPN.

I opened client’s VPN (using Cisco AnyConnect), and then ran my application with strConnTest. I got the error:
“Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.”

How to fix this problem?

Thanks,

Posted 13-Aug-15 6:33am

open_door8

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2015-08-13T07:45:00

If the server is in one AD domain and your user account is in another, but default, there is no trust relationship between the two domains. Your login will not work.

To fix this you either need to setup a trust relationship between the domains to that the SQL Server's domain trusts the one your user account is in or you need to create and use an account that's in the same domain as the SQL Server.

There is nothing you can do in the connection string or your code to fix this.