blocks|key|3234990|text|为什么不使用Server帐户并同时传递用户名和密码？|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3234991|原因如下。|3234992|简而言之，您似乎遇到了身份验证问题。|3234993|工作组的问题是没有像Active+Directory+(AD)这样的公共访问控制列表。如果使用ODBC或JDBC，则传递错误的凭据。|3234994|即使在安装了SQL+Express+(SE)的计算机(SE)上创建本地windows帐户(LWA)，从客户端计算机(CM)传递的凭据也将是CM\LWA。|3234995|entityMap^0|0|Q|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|U|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|V|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|O|$]]

Why not use a SQL Server account and pass both the user name and password?

Here is the reason why.

In short, it looks like you have an authentication issue.

The problem with workgroups is there is no common Access Control List like Active Directory (AD). If you are using ODBC or JDBC, the wrong credentials are passed.

Even if you create a local windows account (LWA) on the machine (SE) that has SQL Express installed (SE\LWA), the credentials that will be passed from your client machine (CM) will be CM\LWA.

blocks|key|3235033|text|为了使用Windows身份验证，有两件事必须是正确的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3235034|您正从与数据库服务器相同的机器上执行。|ordered-list-item|3235035|您有一个Active+Directory环境，应用程序正在执行的用户(通常是登录用户)有权连接到该数据库。|3235036|如果这两件事都不是真的，你必须做两件事中的一件：|3235037|建立Windows域控制器，将所有相关计算机连接到该控制器，然后修复SQL服务器以使用域帐户；|3235038|更改SQL+server以同时使用Windows和Server帐户。|3235039|到目前为止，最简单的方法是将Server更改为同时使用Windows和SQL+server帐户。然后，只需在DB服务器上创建一个sql服务器用户，并更改连接字符串即可。|3235040|最好的情况选择1将需要一整天的安装和配置。备选案文2约需5分钟。|3235041|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|U|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|V|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|W|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|X|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Y|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Z|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|R|$]]

In order to use Windows Authentication one of two things needs to be true: 

<ol>
<li>You are executing from the same machine as the database server. </li>
<li>You have an Active Directory environment and the user the application is executing under (usually the logged in user) has rights to connect to that database.</li>
</ol>

If neither of those are true you have to do one of two things: 

<ol>
<li>Establish a Windows Domain Controller, connect all of the relevant machines to that controller, then fix SQL server to use domain accounts; OR, </li>
<li>Change SQL server to use both Windows and SQL Server accounts. </li>
</ol>

By FAR the easiest way is to change SQL Server to use both Windows and SQL server accounts. Then you just need to create a sql server user on the DB server and change your connection string to do that.

Best case option 1 will take a full day of installation and configuration. Option 2 ought to take about 5 minutes.

blocks|key|840798|text|摆脱Integrated+Security=true对我起了作用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|840799|entityMap^0|2|O|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Getting rid of <code>Integrated Security=true</code> worked for me.

blocks|key|3235060|text|如果用于访问SQL服务器的帐户被域锁定，也会发生此错误消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3235061|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This error message can also occur if the account you are using to access the SQL server is locked out by the domain.

blocks|key|3235070|text|在使用DNS别名和主机文件连接到使用不同域名的计算机时，我也遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3235071|假设您有一个名为sql1+on+mydomain.com的SQL服务器--这是一个Active域--并且您还有一个用于mydomain.net的DNS区域，并且--为了一致性，您为database.mydomain.net+-->+sql1.mydomain.com设置了一个DNS别名(CNAME)记录。|offset|length|style|CODE|3235072|您将能够使用连接到sql1.mydomain.com，但即使它是同一个服务器，也无法连接到database.mydomain.net+，因为域名与AD域不匹配。|BOLD|3235073|entityMap^0|0|8|4|G|C|2I|17|0|9|H|19|L|1V|D|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@$D|O|E|P|F|G]|$D|Q|E|R|F|G]|$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|U|8|@$D|V|E|W|F|G]|$D|X|E|Y|F|G]|$D|Z|E|10|F|J]]|9|@]|A|$]]|$1|K|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|L|$]]

I've had this same issue when using DNS aliases and hosts files to connect to a machine using a different domain name.

Say you have a SQL server called <code>sql1</code> on <code>mydomain.com</code> - which is an Active Directory domain - and you also have a DNS zone for mydomain.net, and - for consistency - you set up a DNS alias (CNAME) record for <code>database.mydomain.net --&gt; sql1.mydomain.com</code>

You'll be able to connect to <code>sql1.mydomain.com</code> using Windows integrated security, but won't be able to connect to <code>database.mydomain.net</code> even though it's the same server because the domain name doesn't match your AD domain.

blocks|key|3235154|text|如果您的Server位于一个域控制器上，并且试图从另一个域控制器连接到它，则当|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3235155|IntegratedSecurity+=+true;|code-block|syntax|javascript|3235156|即使您在连接字符串中包含了有效的Server用户名和密码，也会发生这种情况，因为它们将自动与windows登录和密码一起被重写。集成安全性意味着-使用windows凭据对Server进行登录验证。因此，如果您登录到另一个域控制器，那么它将失败。在使用两个不同域控制器的情况下，您别无选择，只能使用|3235157|IntegratedSecurity+=+false;|3235158|现在，当集成安全性为false时，Server将使用连接字符串中提供的Server登录名和密码。为此，Server实例必须将其身份验证模式配置为混合模式，即Server和Windows身份验证模式。|3235159|若要在Server中验证或更改此设置，可以打开，右键单击服务器名称，然后选择“属性”。在出现的弹出窗口上，选择Security，如果需要，您将看到更改此设置的位置。|3235160|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

If your SQL Server is on one domain controller and you are trying to connect to it from another domain controller then you will get this error when 

<pre><code>IntegratedSecurity = true;
</code></pre>

This will happen even if you include a valid SQL Server username and password in your connection string as they will automatically be over-written with your windows login and password. Integrated security means simply - use your windows credentials for login verification to SQL Server. So, if you are logged in to a different domain controller then it will fail. In the case where you are on two different domain controllers then you have no choice but to use

<pre><code>IntegratedSecurity = false;
</code></pre>

Now, when Integrated security is false SQL Server will use the SQL Server login and password provided in your connection string. For this to work, the SQL Server instance has to have its authentication mode configured to mixed mode, being, SQL Server and Windows Authentication mode. 

To verify or change this setting in SQL Server you can open the SQL Server Management Studio and right-click on your server name and then select Properties. On the pop-up that appears select Security and you will see where to alter this setting if you need to.

blocks|key|3235171|text|在我的示例中，SQLNativeClient11.0配置中的别名指向无效的server/IP。一旦更新，它就正常工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3235172|检查:+1.启动“Server配置管理器”2.导航到"SQL本机客户端11.0配置“，然后”别名“3。确保TCP/IP正确匹配”别名名称“和”服务器“|3235173|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In my case the Aliases within SQL Native Client 11.0 Configuration were pointing to invalid server/IP. Once updated it worked correctly.

To check:
1. Start "SQL Server Configuration Manager"
2. Navigate to "SQL Native Client 11.0 Configuration" and then "Aliases"
3. Ensure "Alias Name" and "Server" match correctly for TCP/IP

blocks|key|3235204|text|接下来，我可以使用Windows身份验证从另一台机器访问Server。这种方法可能只在开发/测试环境中有用。当你在工作机器上更改密码时，你需要手动更新密码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3235205|在带有Server的计算机上，转到Control并添加新的Windows用户，其用户名和密码与工作机器上的用户名和密码相同。然后为该用户创建Server登录名：|3235206|CREATE+LOGIN+[SQLSERVERHOST\myuser]+FROM+WINDOWS;|code-block|syntax|javascript|3235207|现在，您可以使用此登录名进行Windows身份验证。|3235208|如果收到错误“登录来自不受信任的域”，这可能意味着您更改了工作机器上的密码，现在需要更新Server机器上的密码。|3235209|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Following worked for me to get access from another machine to SQL Server using Windows Authentication. This approach may be useful only in development/test environment. E.g. you need to update password manually once you change it on your working machine.

On machine with SQL Server go to Control Panel and add new Windows User with same username and password as is on your working machine. Then create SQL Server login for this user:

<pre><code>CREATE LOGIN [SQLSERVERHOST\myuser] FROM WINDOWS;
</code></pre>

Now you can use this login for Windows Authentication.

If you receive error 'The login is from an untrusted domain', this may mean that you changed password on your working machine and now need to update password on SQL Server machine.

blocks|key|3235218|text|跟随者为我工作。希望这对你有帮助|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3235219|<add+name="getconn"+connectionString="Data+Source=servername;Initial+Catalog=DBName;Persist+Security+Info=True;User+ID=sa;Password=***"+/>|code-block|syntax|javascript|3235220|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Following was working for me. hope this helps you

<pre><code>&lt;add name="getconn" connectionString="Data Source=servername;Initial Catalog=DBName;Persist Security Info=True;User ID=sa;Password=***" /&gt;
</code></pre>

blocks|key|3235233|text|正如前面提到的这里，您可能需要禁用环回。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3235234|可以通过添加注册表项来删除回送检查，如下所示：|3235235|使用regedit编辑注册表。(启动->+Run+>+Regedit+)|unordered-list-item|3235236|导航至:+HKLM\System\CurrentControlSet\Control\LSA|3235237|添加一个名为“DisableLoopbackCheck”的DWORD值，将此值设置为1|3235238|entityMap|0|LINK|mutability|MUTABLE|url|https://blog.sqlauthority.com/2017/04/18/sql-server-login-failed-login-untrusted-domain-cannot-used-windows-authentication/^0|7|2|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|C|$]]|$1|I|3|J|5|H|7|10|8|@]|9|@]|C|$]]|$1|K|3|L|5|H|7|11|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

As mentioned <a href="https://blog.sqlauthority.com/2017/04/18/sql-server-login-failed-login-untrusted-domain-cannot-used-windows-authentication/" rel="nofollow noreferrer">here</a>, you might need to disable the loopback

Loopback check can be removed by adding a registry entry as follows:

<ul>
<li>Edit the registry using regedit. (Start –> Run > Regedit ) </li>
<li>Navigate to: HKLM\System\CurrentControlSet\Control\LSA </li>
<li>Add a DWORD value called “DisableLoopbackCheck” Set this value to 1</li>
</ul>

blocks|key|3235265|text|在添加解决方案的建议时，我有一个VM服务器的副本，用于开发和测试，我在数据库上创建了数据库，其中“sa”拥有数据库的所有权。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3235266|然后，我将数据库还原到活动的VM服务器上，但我得到的错误与前面提到的相同，尽管数据返回仍然是正确的。我查找了'sa‘用户映射，可以看到它没有映射到数据库，当我试图应用映射时，我得到了另一个错误"Fix:无法使用特殊的主体’sa‘.，错误:+15405“。所以我用这个代替了|3235267|更改对数据库的授权：：dbname+TO+sa|3235268|我重新检查了用户映射，它现在被分配给我的db，它为我解决了很多访问问题。|3235269|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Just adding my suggestion for a resolution, I had a copy of a VM server for developing and testing, I created the database on that with 'sa' having ownership on the db. 

I then restored the database onto the live VM server but I was getting the same error mentioned even though the data was still returning correctly. I looked up the 'sa' user mappings and could see it wasn't mapped to the database when I tried to apply the mapping I got a another error "Fix: Cannot use the special principal ‘sa’. Microsoft SQL Server, Error: 15405". so I ran this instead

ALTER AUTHORIZATION ON DATABASE::dbname TO sa 

I rechecked the user mappings and it was now assigned to my db and it fixed a lot of access issues for me.

blocks|key|3235303|text|如果使用windows身份验证，请确保用户的密码未过期。过期密码可以解释此错误。这就是我的问题所在。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3235304|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you using windows authentication make sure that password of the user hasn't expired. An expired password can explain this error. This was the problem in my case.

blocks|key|841042|text|我们现在使用一个特权帐户管理解决方案，定期更改我们的密码。在更改密码后，我最终收到了此错误。关闭并重新打开使用新密码的SSMS解决了我的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|841043|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

We now use a privileged account management solution that changes our passwords regularly. I ended up receiving this error after my password was changed. Closing and re-opening SSMS with the new password resolved my issue.

blocks|key|841047|text|当我试图使用“windows身份验证”登录到SSMS时，我开始收到此错误。在我重命名Windows服务器之后，这种情况就开始发生了。我尝试了所有方法来解决这个错误，在我的特殊情况下，更改“主机”文件中的机器名称以反映名称SQL服务器名称的更改解决了这个问题。C：\Windows\System32+32\驱动程序\etc\主机|type|unstyled|depth|inlineStyleRanges|entityRanges|data|841048|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I started to get this error when i tried to login to SSMS using 'windows Authentication'. This started to happen after i renamed the Windows SQL server. I tried everything to resolve this error and in my particular case changing the machine names in the 'hosts' file to reflect the name SQL server name change resolved the issue. C:\Windows\System32\Drivers\etc\hosts

blocks|key|1917071|text|我遇到了这个问题，因为我们使用一个来自旧服务器的DNS名称，ponting到一个新服务器。使用新服务器\inst1地址，已工作。newserver\inst1和oldserver\inst1都指向同一个IP。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1917072|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had this problem because we where using a DNS name from an old server, ponting to a new server. Using the newserver\inst1 address, worked. both newserver\inst1 and oldserver\inst1 pointed to the same IP.

blocks|key|1917077|text|还有一件事要检查：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1917078|在另一名开发人员远程访问QA服务器并试图在中午启动还原作业之后，我们的夜间QA还原作业突然停止工作，随后出现了“不受信任域”消息失败。不知何故，服务器指向的是作业的维护计划被改变了(？)使用ip地址，而不是本地机器的名称。用机器名称替换后，问题就解决了。|1917079|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Yet another thing to check: We had our nightly QA restore job stop working all of a sudden after another developer remoted into the QA server and tried to start the restore job during the middle of the day, which subsequently failed with the "untrusted domain" message. Somehow the server pointed to be the job's maintenance plan was (changed?) using the ip address, instead of the local machine's name. Upon replacing with the machine name the issue was resolved.

blocks|key|1917121|text|在连接到侦听器上的SQL时，我遇到了这个问题。禁用回循环检查解决了该问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1917122|使用regedit编辑注册表。(启动->+Run+>+Regedit+)|ordered-list-item|1917123|导航到：HKLM\System\CurrentControlSet\Control\LSA|offset|length|style|CODE|1917124|添加一个名为DWORD的“DisableLoopbackCheck”值|1917125|将此值设置为1|1917126|https://blog.sqlauthority.com/2017/04/18/sql-server-login-failed-login-untrusted-domain-cannot-used-windows-authentication/|1917127|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|4|15|0|6|5|C|M|0|6|1|0|0|3F|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Y|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|Z|8|@$G|10|H|11|I|J]]|9|@]|A|$]]|$1|K|3|L|5|D|7|12|8|@$G|13|H|14|I|J]|$G|15|H|16|I|J]]|9|@]|A|$]]|$1|M|3|N|5|D|7|17|8|@$G|18|H|19|I|J]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1A|8|@]|9|@$G|1B|H|1C|1|1D]]|A|$]]|$1|Q|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|P]]]]

I was facing the issue while connecting to SQL Always On Listener. Disabling the loop back check resolved the issue.

<ol>
<li>Edit the registry using regedit. (Start –> Run > Regedit )</li>
<li>Navigate to: <code>HKLM\System\CurrentControlSet\Control\LSA</code></li>
<li>Add a <code>DWORD</code> value called <code>“DisableLoopbackCheck”</code></li>
<li>Set this value to <code>1</code></li>
</ol>

<a href="https://blog.sqlauthority.com/2017/04/18/sql-server-login-failed-login-untrusted-domain-cannot-used-windows-authentication/" rel="noreferrer">https://blog.sqlauthority.com/2017/04/18/sql-server-login-failed-login-untrusted-domain-cannot-used-windows-authentication/</a>

blocks|key|1917136|text|如果您有两个服务器在同一个域(例如。通过在两台匹配的机器上设置本地用户(用户名和密码相同)，您也可以在APP和MSSQL之间使用Windows身份验证。如果您没有匹配密码，它可能会抛出此错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1917137|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you have two servers on the same domain (eg. APP and DB), you can also use Windows Authentication between the app and MSSQL by setting up local users on both machines that match (same username and password). If you don't have the passwords matched up, it can throw this error.

blocks|key|3235438|text|在.net核心中，如果设置了Trusted_Connection=True；，也可能会得到此错误。appsettings.json中的样本设置|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3235439|ConnectionStrings":+{
"DefaultConnection":+"Server=serverName;+Database=DbName;+uid=userId;+pwd=password;+MultipleActiveResultSets=true"|code-block|syntax|javascript|3235440|},|3235441|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In .net Core also you may get this error if Trusted_Connection=True;
Is set. Sample setting in appsettings.json
<pre><code>ConnectionStrings&quot;: {
&quot;DefaultConnection&quot;: &quot;Server=serverName; Database=DbName; uid=userId; pwd=password; MultipleActiveResultSets=true&quot;
</code></pre>
},

blocks|key|1917185|text|TLDR:将DNS服务器更改为循环回地址对我有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1917186|我在VirtualBox工作，安装了两个Windows+2016实例。服务器A配置为域控制器，服务器B配置为Server。在将服务器B添加到我没有从服务器A与Management连接到的域之后，我得到了“登录来自不受信任的域，不能用于Windows身份验证”。|1917187|我最初的配置让服务器从VirtualBox+DHCP服务器获取其IP。|1917188|我将此更改为使用静态IP，并在主DNS中输入了127.0.0.1地址，这对我有效。|1917189|希望这对路过的人有帮助。|1917190|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

TLDR: Changing the DNS server to the loop back address worked for me.
I am working in VirtualBox and had setup two Windows Server 2016 instances. Server A is configure as a Domain Controller and Server B as an SQL Server. After adding Server B to the domain I cold not connect to with Management Studio from Server A. I was getting the &quot;The login is from an untrusted domain and cannot be used with Windows authentication&quot;.
My initial configuration had the server getting its IP from the VirtualBox DHCP server.
I changed this to use static IP and entered the 127.0.0.1 address in the Primary DNS and this worked for me.
Hope this helps someone passing by.

blocks|key|1917237|text|我在连接属性中启用了信任服务器证书，它对我起作用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1917238|​|1917239|📷|atomic|offset|length|1917240|1917241|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/dbc7be63af40d5a5b65a5a25a192d2c4.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

I enabled Trust Server Certificate in the Connection Properties and it worked for me
<a href="https://i.stack.imgur.com/oo6Gs.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/oo6Gs.png" alt="connection properties" /></a>

blocks|key|841333|text|加入一个工作组，然后重新加入域，为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|841334|我在使用Virtual时遇到了这个错误，当我将VM文件移动到一个新的驱动器位置或计算机时，问题就开始发生了。|841335|希望这对VM的人有帮助。|841336|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Joining a WORKGROUP then rejoining the domain fixed this issue for me.
I got this error while using Virtual Box VM's. The issue started to happen when I moved the VM files to a new drive location or computer.
Hope this helps the VM folks.

blocks|key|841388|text|您可能会发现您有多个连接字符串，而忘记将另一个更改为Integrated为false。这事发生在我身上。这个答案可能对某人有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|841389|我专注于web配置和访问权限，经过很长时间的忙忙碌碌之后，我想起我的一个类中有另一个连接字符串用于电子邮件，我不得不更改类上的连接字符串以使用web配置字符串。|841390|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You might find out that you have more than one connection string, and you forgot to change the other one to Integrated Security to false. It happened to me. This answer might help someone.
I was focusing on the web config and the access rights, after a long hustle i remembered that I have another connection string in one of my classes for the emails, I had to change the connection string on the class to use the web config one.

blocks|key|841406|text|我把Integrated+Security=true和Trusted_Connection=True都除掉了，为我工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|841407|entityMap^0|2|O|R|N|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

i removed <code>Integrated Security=true</code> and <code>Trusted_Connection=True</code> both of them , worked for me..

blocks|key|3235645|text|Visual环境中的连接字符串错误|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3235646|我们的开发数据库服务器最近获得了一个自签名证书，因此它自动变得不可信.这导致了上面引用的登录错误。我将TrustServerCertificate=True添加到连接字符串中，现在它可以工作了。|offset|length|style|CODE|3235647|"Server=TheServerAddress;+Database=TheDataBase;+User+Id=TheUsername;+Password=ThePassword;+TrustServerCertificate=True"|3235648|我是通过将我在几个答案中找到的信息和一些关于这个问题的源代码文档来发现这个答案的：成功地与服务器建立了连接，但在登录过程中发生了错误。(错误编号:+233)。|3235649|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/34430550/a-connection-was-successfully-established-with-the-server-but-then-an-error-occ/71229027#71229027^0|0|1F|R|0|0|3B|0|15|11|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@$D|11|E|12|1|13]]|A|$]]|$1|L|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

<h3>Connection String Error in Visual Studio dev environment</h3>
Our development database server was recently given a self-signed certificate so it automatically became untrusted. This resulted in the login error cited above. I added <code>TrustServerCertificate=True</code> to my connection string and it works now.
<code>&quot;Server=TheServerAddress; Database=TheDataBase; User Id=TheUsername; Password=ThePassword; TrustServerCertificate=True&quot;</code>
I discovered this answer by combining information I found in several of the answers and some of source documentation to this question: <a href="https://stackoverflow.com/questions/34430550/a-connection-was-successfully-established-with-the-server-but-then-an-error-occ/71229027#71229027">A connection was successfully established with the server, but then an error occurred during the login process. (Error Number: 233)</a>

blocks|key|1917364|text|有时SSMS挂起并突然关闭，然后当您重新连接到SSMS时会出现以下错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1917365|(+i)登录来自不受信任的域，不能与Windows身份验证一起使用|1917366|或|1917367|(2)目标主体名称不正确，.Cannot生成SSPI上下文。|1917368|在这两种情况下，RESTART+YOUR+MACHINE。|offset|length|style|CODE|1917369|entityMap^0|0|0|0|0|8|K|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@$J|U|K|V|L|M]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

Sometime SSMS hang and close all of sudden ,then you get below error when you reconnect to SSMS
i) The Login is From an Untrusted Domain and Cannot be Used with Windows Authentication
OR
ii) The target principal name is incorrect .Cannot generate SSPI context.
In both cases <code>RESTART YOUR MACHINE</code>.

blocks|key|3235699|text|我也有一个类似的错误，但后来我意识到，我只是更改了我的系统密码，这导致了这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3235700|要解决这个问题，我只需退出当前会话，并再次登录，而这一次。|3235701|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I also had a similar error but then I realised I just had changed the password for my system which caused this error.
To resolve it , I simply logged out of the current session and logged in again and this time

I am trying to host a SQL server database, but whenever I try to connect to it I get this error:

<blockquote>
 The login is from an untrusted domain and cannot be used with Windows
 authentication
</blockquote>

I am connecting through Matlab using the following command:

<pre><code>conn = database('Clinical_Data','DoyleLab07\Acc','','com.microsoft.sqlserver.jdbc.SQLServerDriver','jdbc:sqlserver://DOYLELAB07\SQLEXPRESS:54287;database=Clinical_Data;integratedSecurity=true;').
</code></pre>

Connecting to the database using matlab worked fine as long as I was using matlab on the computer which I was using to host the server. However, when I use another computer and the same Matlab command I get the error I showed above. 

When I look under control panel\system. I notice that no domain is listed on my host PC or the PC I am using to connect to the host, but both computers are in the same workgroup. Would I be able to fix my problem by creating a domain and adding the foreign PC and the host to that domain? If so, how can this be accomplished?

Any suggestions will be very much appreciated. 
Thank you for reading my post.

Trouble Connecting to sql server Login failed. "The login is from an untrusted domain and cannot be used with Windows authentication"

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我试图托管一个SQL服务器数据库，但是每当我试图连接到它时，我都会得到以下错误：该登录来自不受信任的域，不能与Windows身份验证一起使用我使用以下命令通过Matlab进行连接：conn = database('Clinical_Data','DoyleLab07\Acc','','com.microsoft.sql...

问连接到sql服务器登录失败。“登录来自不受信任的域，不能与Windows身份验证一起使用”
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问连接到sql服务器登录失败。“登录来自不受信任的域，不能与Windows身份验证一起使用”EN