blocks|key|350292|text|尝试使用其他有效的登录using+RUNAS+command|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|350293|runas+/user:domain\user+“C:\Program+Files\Microsoft+SQL+Server\90\Tools\Binn\VSShell\Common7\IDE\ssmsee.exe”+

runas+/user:domain\user+“C:\WINDOWS\system32\mmc.exe+/s+\”C:\Program+Files\Microsoft+SQL+Server\80\Tools\BINN\SQL+Server+Enterprise+Manager.MSC\”"+

runas+/user:domain\user+isqlw+|code-block|syntax|javascript|350294|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/jgalloway/archive/2007/09/07/tip-use-runas-to-set-your-windows-auth-domain-for-database-connections.aspx^0|B|J|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

try using a different valid login <a href="http://weblogs.asp.net/jgalloway/archive/2007/09/07/tip-use-runas-to-set-your-windows-auth-domain-for-database-connections.aspx" rel="nofollow noreferrer">using RUNAS command</a>

<pre><code>runas /user:domain\user “C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\ssmsee.exe” 

runas /user:domain\user “C:\WINDOWS\system32\mmc.exe /s \”C:\Program Files\Microsoft SQL Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC\”" 

runas /user:domain\user isqlw 
</code></pre>

blocks|key|3128545|text|为了启用windows身份验证，两台计算机需要在同一个域中。为了允许管理工作室传递当前凭据并在sql框中进行身份验证|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3128546|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|$]]

in order to enable windows authentication both computers need to be in the same domain. in order to allow managment studios to pass the current credentials and authenticate in the sql box

blocks|key|3341364|text|该问题是由关闭Active+Directory+Server引起的，该服务器当然无法对Windows帐户进行身份验证。谢谢你的帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3341365|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|$]]

The issue was caused by a down Active Directory Server, which of course could not authenticate the Windows account. Thank you for your assistance.

blocks|key|3341374|text|这可能发生的另一个原因(刚刚发生在我身上)+...是用户的密码过期。我没有意识到这一点，直到我试图远程进入实际的服务器，并提示我更改我的密码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3341375|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|$]]

Another reason this might happen (just happened to me) ... is the user's password expires. I didn't realize this until I tried to remote into the actual server and was prompted to change my password.

blocks|key|347904|text|对我来说，这是因为我没有将帐户添加到SQL数据库本身，使其具有我想要使用的角色。也是由于错误的密码尝试通过复制粘贴锁定帐户的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|347905|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|$]]

For me, it was because i did not add the account to have roles I wanted to use to the SQL Database itself. And also due to a bad password attempts via copy paste problem locking account.

blocks|key|3341456|text|对我来说，我必须断开(更改工作组/域)与域的连接，然后重新连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3341457|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|$]]

For me, I have to disconnect (change workgroup/domain) from the Domain and reconnect.

blocks|key|3341481|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3341482|“该问题是由关闭Active+Directory服务器引起的，该服务器当然不能验证Windows帐户”|blockquote|3341483|3341484|当然不是--因为如果AD不可用，那么Kerberos身份验证将退回到NTLM+(域帐户凭据被缓存在本地，即使AD/Kerberos不可用，用户也可以使用它登录)。我猜您可能有两种同时发生这种失败的情况：|3341485|3341486|SQL+Server不是本地的(在另一台计算机上)|unordered-list-item|3341487|信任配置为“仅Kerberos”|3341488|3341489|或其他特定的安全网络/服务器/AD/机器配置|3341490|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|R|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|S|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|T|7|@]|8|@]|9|$]]|$1|E|3|F|4|5|6|U|7|@]|8|@]|9|$]]|$1|G|3|-4|4|5|6|V|7|@]|8|@]|9|$]]|$1|H|3|I|4|J|6|W|7|@]|8|@]|9|$]]|$1|K|3|L|4|J|6|X|7|@]|8|@]|9|$]]|$1|M|3|-4|4|5|6|Y|7|@]|8|@]|9|$]]|$1|N|3|O|4|5|6|Z|7|@]|8|@]|9|$]]|$1|P|3|-4|4|5|6|10|7|@]|8|@]|9|$]]]|Q|$]]

<blockquote>
 "The issue was caused by a down Active Directory Server, which of course could not authenticate the Windows account" 
</blockquote>

It is not "of course - because if AD is not available then Kerberos authentication falls back to NTLM (domain account credentials are cached locally, one can login with it even if AD/Kerberos is not available). I guess that you have possibly 2 simultaneous conditions for this failure to happen: 

<ul>
<li>SQL Server is not local (on another machine) </li>
<li>The trust is configured "Kerberos only" </li>
</ul>

or other specific security network/server/AD/machine configurations

blocks|key|3128664|text|我一直在尝试从域帐户登录SQL+Server+2008。SQL+Server+2008托管在不属于该域的另一台工作组计算机上。听起来很奇怪，在运行SQL+server+2008的工作组服务器上，我必须转到系统属性%7C计算机名称(选项卡)%7C更改(按钮)%7C计算机名称更改%7C更多...(按钮)并输入“此计算机的主DNS后缀”(为空，因此请为您的网络输入所需的后缀)，然后选中“当域成员身份更改时更改主DNS后缀”框。这样，Windows身份验证过程就可以在登录到SQL+Server+2008时完成。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3128665|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 have been trying to log into a SQL Server 2008 from a domain account. The SQL Server 2008 is hosted on a different workgroup computer that is not part of the domain. As strange as it sounds, on the workgroup server where SQL Server 2008 is running, I had to go to System Properties | Computer Name (tab) | Change (button) | Computer Name Change | More... (button) and enter the "Primary DNS suffix of this computer" (it was blank, so enter the desired suffix for your network) and check the "Change primary DNS suffix when domain membership changes" box. This allowed the Windows Authentication process to complete when logging into the SQL Server 2008.

blocks|key|3128676|text|对我来说，当我编辑了一个空白的drivers/etc/hosts文件，并为一个本地网站添加了一个条目，但忽略了添加127.0.0.1+localhost时，就会发生这种情况|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3128677|entityMap^0|F|H|1L|J|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|$]]

For me, this happened when I edited a blank <code>drivers/etc/hosts</code> file, and added an entry for a local website, but neglected to add <code>127.0.0.1 localhost</code>

blocks|key|3128685|text|我更换了连接线，它开始工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3128686|从…|3128687|main_sqlconnection+=+New+SqlConnection("Data+Source=Server1\SQLEXPRESS;Initial+Catalog=Master;Trusted_Connection=True")|code-block|syntax|javascript|3128688|至|3128689|main_sqlconnection+=+New+SqlConnection("Data+Source=Server1\SQLEXPRESS;Initial+Catalog=Master;User+ID=ARM;Password=1;")|3128690|我在Microsoft+SQL+Server+Management+Studio中创建了帐户User+ID=User;Password=1;：单击Security并添加一个新用户。|offset|length|style|CODE|3128691|entityMap^0|0|0|0|0|0|1A|O|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|Z|8|@$O|10|P|11|Q|R]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

I replaced the connecting string and it started working

from

<pre><code>main_sqlconnection = New SqlConnection("Data Source=Server1\SQLEXPRESS;Initial Catalog=Master;Trusted_Connection=True")
</code></pre>

to

<pre><code>main_sqlconnection = New SqlConnection("Data Source=Server1\SQLEXPRESS;Initial Catalog=Master;User ID=ARM;Password=1;")
</code></pre>

I created the account <code>User ID=User;Password=1;</code> in Microsoft SQL Server Management Studio: click on Security and add a new user.

blocks|key|353141|text|只需从连接字符串中删除Trusted_Connection=True属性即可。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|353142|entityMap^0|B|N|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|$]]

Just remove <code>Trusted_Connection=True</code> property from the connection string.

blocks|key|347967|text|我在本地机器上的一个服务器实例上遇到了这个问题，并发现这是因为我在hosts文件中指向了127.0.0.1，而不是"localhost“。在我的例子中，有两种方法可以解决这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|347968|347969|清除主机文件中指向127.0.0.1的有问题的条目|ordered-list-item|347970|使用"localhost“，而不是指向127.0.0.1|347971|的主机文件中的其他名称|347972|*只有当我在本地计算机上运行sql+server实例并尝试从同一台计算机访问它时，这才适用于我。|347973|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I had this issue for a server instance on my local machine and found that it was because I was pointing to 127.0.0.1 with something other than "localhost" in my hosts file. There are two ways to fix this issue in my case:

<ol>
<li>Clear the offending entry pointing to 127.0.0.1 in the hosts file</li>
<li>use "localhost" instead of the other name that in the hosts file that points to 127.0.0.1</li>
</ol>

*This only worked for me when I was running the sql server instance on my local box and attempting to access it from the same machine.

blocks|key|353160|text|另一个可能的原因是:+DB+Server上新创建的本地帐户设置了：“用户必须在下次登录时更改密码”标志集。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|353161|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|$]]

And another possible reason: 
The new created local Account on DB Server had the: "User must change Password at next Login" Flag set.

blocks|key|347995|text|您需要先启用sa帐号，并使用sa帐号登录到您的SQL+management+studio+(请选择SQl服务器身份验证)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|347996|使用sa帐户登录后，转到security，右键单击logins，选择new+login，选择SQL+Server+authentication，创建一个用户名(不使用/或任何其他特殊字符，只创建一个名称)，然后为其提供密码，确认该密码，并在该页面的底部选择您的默认数据库。|347997|转到logins，右键单击您创建的用户，然后单击properties。|347998|转到Server+Roles并选择要为您创建的用户分配的角色。|347999|单击OK并返回到login+properties，单击User+Mapping，双击要将此用户映射到的数据库，然后在底部窗口中选择该数据库的数据库角色成员资格。|348000|entityMap^0|6|2|E|2|0|C|8|P|6|Y|9|1A|P|2B|1|0|2|6|O|A|0|2|C|0|2|2|8|G|R|C|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]]|O|$]]

You need to enable the <code>sa</code> account first and log in to your SQL management studio with the <code>sa</code> account (please chose SQl Server authentication).

After you logged in with the sa account, go to <code>security</code>, right-click on <code>logins</code>, select <code>new login</code>, select <code>SQL Server authentication</code>, create a user name (no <code>/</code> or any other special characters, just a name), then give it a password, confirm the password and at the bottom of that page select your default Database.

Go to <code>logins</code>, right-click on the user you created and click on <code>properties</code>.

Go to <code>Server Roles</code> and select the roles you want to give to the user you created.

Click <code>OK</code> and go back to <code>login properties</code>, click on <code>User Mapping</code>, double-click on the database you want to map this user to and select the database role membership for that database in the bottom window.

blocks|key|350478|text|好吧，完全由我来回答。我从一个托管在VM+VirtualBox上的开发环境中得到了这个错误。三台服务器:+SharePoint、SQL+DB和域控制器。SharePoint服务器无法连接到配置数据库。我仍然可以使用SA帐户通过ODBC进行Sql身份验证，但不能使用Windows身份验证。但是该用户会很高兴地登录到sql服务器本身上的SSMS。我也从ODBC得到了更好的错误消息，还通过检查sql+server上的失败登录消息：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|350479|select+text+from+sys.messages+where+message_id+=+'18452'+and+language_id+=+1033|code-block|syntax|javascript|350480|这不能归功于此，因为我向我们的企业系统管理员寻求帮助，他在大约5分钟内诊断出了这个问题，我给他发了几张屏幕截图。的问题是域控制器的时钟设置不正确！不敢相信。服务器设置为仅主机联网，因此没有互联网来同步时钟。这也解释了为什么当我知道系统正在工作时，回滚到较早的快照并不能解决问题。|offset|length|style|BOLD|350481|编辑:在服务器上安装Guest+Additions将使来宾时钟与主机同步。|350482|entityMap^0|0|0|1K|H|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|@$I|T|J|U|K|L]]|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|$]]

Okay, completely out there answer from me. I was getting this error from a development environment hosted on VM VirtualBox. Three servers; SharePoint, SQL DB and Domain Controller. The SharePoint server couldn't connect to the configuration database. I could still connect via ODBC for Sql authentication using SA account but not Windows authentication. But that user would happily log into SSMS on the sql server itself. I got a better error message from ODBC too and also by checking the failed login messages on sql server:

<pre><code>select text from sys.messages where message_id = '18452' and language_id = 1033
</code></pre>

Can't take credit for this because I asked one of our Enterprise Systems Administrators for help and he diagnosed it in about 5 minutes of looking at a few screen shots I sent him. Problem was that the Domain Controller’s clock was set incorrectly! Couldn't believe it. The servers are setup for Host Only networking so don't have internet to sync the clock with. That also explains why rolling back to an earlier snapshot when I know the system was working didn't solve the problem.

Edit: Installing the Guest Additions on the server syncs the guest clock with the host.

blocks|key|3128828|text|下面是为我解决这个问题的方法:网络连接属性单击："Internet+Protocol+version4+(TCT/IPv4)“。单击“属性”按钮。单击“高级”按钮。选择"DNS“选项卡。删除“此连接的DNS后缀”中的文本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3128829|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|$]]

Here's what fixed it for me:
Properties of network connection
Click on: "Internet Protocol Version 4 (TCT/IPv4)".
Click "Properties" button.
Click "Advanced" button.
Select "DNS" tab.
Delete text in "DNS suffix for this connection".

blocks|key|3128836|text|请确保您未连接到另一个域\用户上的VPN。或者，反之，如果这是必需的，请确保您已连接。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3128837|entityMap^0|0|F|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|$]]

Make sure you aren't connected to a VPN on another domain\user. Or, conversely, make sure you are connected, if that is what is required.

blocks|key|3341709|text|我也无法远程连接到SQL服务器。SQL+server和远程服务器都在同一个域中。几天前，我被要求更改密码。重新启动SQL服务器和我试图从其访问SQL服务器的远程服务器对我起到了很好的作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3341710|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 wasn't able to remotely connect to the SQL server either. Both SQL server and remote server where in the same domain. And I had been requested a password change some days before.
Restarting both the SQL server and the remote server I was trying to access SQL server from did the trick for me.

blocks|key|353222|text|我不得不使用netonly来让它在现代Windows上工作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|353223|runas+/netonly+/user:domain\user+"C:\Program+Files+(x86)\Microsoft+SQL+Server\110\Tools\Binn\ManagementStudio\ssms.exe"|offset|length|style|CODE|353224|entityMap^0|0|0|3B|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I had to use netonly to get this to work on modern Windows:

<code>runas /netonly /user:domain\user "C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\ssms.exe"</code>

blocks|key|3341793|text|在我们的例子中，事实是开发人员在他自己的帐户下运行应用程序池，并且重置了他的密码，但忘记了在应用程序池上更改它。嗯..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3341794|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|$]]

In our case it was the fact that the developer was running the application pool under his own account, and had reset his password but forgot to change it on the application pool. Duh...

blocks|key|350553|text|在我的例子中，服务器在域控制器中被禁用。我进入Active+directory中的计算机OU，右键单击服务器，将其启用，然后从SQL+server执行gpupdate+/force。它花了一段时间，但最终还是起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|350554|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|$]]

In my case, the server had been disabled in the domain controller. I went into the COMPUTERS OU in Active directory, right-clicked on the server,enabled it, then did a gpupdate /force from the SQL server. It took a moment, but it finally worked.

blocks|key|3341856|text|在我的例子中，在主机文件中，机器名是用旧的IP硬编码的。我用新的IP替换旧的IP，问题就解决了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3341857|主机文件位置|3341858|WindowsDrive:\Windows\System32\drivers\etc\hosts|3341859|Modifications+159.xx.xx.xxx+MachineName|offset|length|style|BOLD|3341860|entityMap^0|0|0|0|E|P|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@$H|R|I|S|J|K]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

In my case, in the host file, the machine name is hard coded with older IP. 
I replace the older IP with the new one, the issue is resolved.

Host file location

WindowsDrive:\Windows\System32\drivers\etc\hosts

Modifications done
159.xx.xx.xxx MachineName

blocks|key|348164|text|另一个reason>用户更改了默认SQL用户的密码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|348165|几分钟前在我切换到新的域控制器时发生了这种情况...|348166|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|$]]

Another reason> 
someone changed the password for the default SQL user

this happened to me a couple of minutes ago by switching to a new domain controller ...

blocks|key|3129008|text|jTDS驱动程序中有一个名为USENTLMV2的设置，默认情况下设置为false。在我的数据库软件(DBVisualizer)中将其设置为'true‘解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3129009|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|$]]

There is a setting on the jTDS driver called USENTLMV2 that is set to false by default. Setting this to 'true' in my db software (DBVisualizer) solved it.

blocks|key|348246|text|以上这些对我来说都不起作用。我要做的是:在登录屏幕上的SQL+Server+Management+Studio中，在“网络”部分中选择“Options+>>”，将“网络协议”更改为“命名管道”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|348247|此外，为了让它在<default>设置下工作，我必须禁用无线网络(机器还连接到有线lan)。|offset|length|style|CODE|348248|entityMap^0|0|8|9|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

None of the above worked for me. What I had to do was:
In SQL Server Management Studio on the login screen, select Options >>
In the Network section change the Network protocol to Named Pipes.

Also, what I had to do to make it work with the <code>&lt;default&gt;</code> setting was to disable the wireless network (the machine was also connected to the wired lan).

blocks|key|353303|text|确保你没有在某个地方使用"Trusty_Connection=yes“。我也遇到了同样的问题，我只需将其设置为"no“即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|353304|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|$]]

Make sure you are are not using "Trusty_Connection=yes" somewhere. I had this same problem and I fix by simply setting this to "no".

blocks|key|353318|text|我的修复方法是更改web.config文件，使其与我的新服务器名相关联(IT+Security刚刚对我的开发箱进行了netdom重命名。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|353319|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|$]]

My fix was to change the web.config file to correlate with my new server name for SQL Connection (IT Security had just done a netdom rename on my development box.

blocks|key|353327|text|对于遇到这种情况的其他人，我在我的hosts文件中有以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|353328|127.0.0.1+++localhost
127.0.0.1+++customname|code-block|syntax|javascript|353329|我需要它是这样的：|353330|127.0.0.1+++localhost
127.0.0.1+++localhost+++customname|353331|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

For anyone else who runs into this, I had this in my hosts file:

<pre><code>127.0.0.1 localhost
127.0.0.1 customname
</code></pre>

and I needed it to be this:

<pre><code>127.0.0.1 localhost
127.0.0.1 localhost customname
</code></pre>

blocks|key|3129106|text|当我想在另一台PC上运行我的项目时，我也遇到了同样的问题。更改连接字符串|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3129107|Data+Source=JOHN-PC\JJ;Initial+Catalog=MyDatabase;Integrated+Security=True;Pooling=False|code-block|syntax|javascript|3129108|至|3129109|Data+Source=JOHN-PC\JJ;Initial+Catalog=MyDatabase;Persist+Security+Info=True;User+ID=MyUserName;Password=MyUserPassword|3129110|帮了我。|3129111|这是原始答案所在的链接：Login+failed.The+login+is+from+an+untrusted+domain...|offset|length|3129112|希望这能有所帮助。|3129113|entityMap|0|LINK|mutability|MUTABLE|url|http://www.codeproject.com/Questions/1081462/Login-failed-the-login-is-from-an-untrusted-domain^0|0|0|0|0|0|C|1H|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|15|8|@]|9|@$O|16|P|17|1|18]]|A|$]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

I had the same problem when I wanted to run my project on another PC. Changing connection string from

<pre><code>Data Source=JOHN-PC\JJ;Initial Catalog=MyDatabase;Integrated Security=True;Pooling=False
</code></pre>

to

<pre><code>Data Source=JOHN-PC\JJ;Initial Catalog=MyDatabase;Persist Security Info=True;User ID=MyUserName;Password=MyUserPassword
</code></pre>

helped me.

This is the link where original answer is: <a href="http://www.codeproject.com/Questions/1081462/Login-failed-the-login-is-from-an-untrusted-domain" rel="nofollow">Login failed.The login is from an untrusted domain...</a>

Hope this would help.

blocks|key|3342162|text|您可能会遇到的另一种情况是，当您尝试从已登录的SSMS会话连接到另一个SQL+server时，您更改了密码。事件的顺序可能类似于：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3342163|在服务器A(您的SQL+Server)上使用|3342164|RDP，打开SSMS并登录到同一域中服务器-B的|ordered-list-item|3342165|+RDP，然后在服务器A上将您的|3342166|会话更改为RDP会话，然后通过SSMS尝试将另一个数据库添加到现有的AlwaysOn可用性组中。当连接到复本时，您会看到"untrusted+domain"-login-error|3342167|3342168|要解决此问题，只需注销并重新登录即可|3342169|entityMap^0|0|0|0|0|0|0|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|F|7|R|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|T|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

Another scenario where you might see this is when you are attempting to connect to another SQL server from an SSMS session that was already logged-in while you changed your password. Sequence of events might go something like:

<ol>
<li>RDP to Server-A (your SQL Server), open SSMS and login</li>
<li>RDP to Server-B in the same domain and change your password</li>
<li>Return to RDP session on Server-A and via SSMS attempt to add another DB into an existing AlwaysOn availability group. When connecting to replicas you get "untrusted domain"-login-error</li>
</ol>

To resolve, simply logoff and log back in

blocks|key|350709|text|我在C:\Windows\System32\drivers\etc下的主机文件中有错误的条目|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|350710|[Microsoft][SQL+Server+Native+Client+11.0][SQL+Server]Login+failed.+The+login+is+from+an+untrusted+domain+and+cannot+be+used+with+Windows+authentication.|code-block|syntax|javascript|350711|确保有如下条目|350712|127.0.0.1+++localhost
127.0.0.1+++localhost+++servername|350713|entityMap^0|2|V|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

I had wrong entry in hosts file under <code>C:\Windows\System32\drivers\etc</code> 

<pre><code>[Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
</code></pre>

Make sure to have entry like below

<pre><code>127.0.0.1 localhost
127.0.0.1 localhost servername
</code></pre>

blocks|key|350718|text|我修复了机器禁用环回检查设置时的这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|350719|#en1#+to+>编辑Windows注册表:+Start+->+Run+>+Regedit|350720|Navigate+to:+HKLM\System\CurrentControlSet\Control\LSA|unordered-list-item|350721|
|350722|Add+a+DWORD值“DisableLoopbackCheck”|350723|350724|Set+|350725|to+1|ordered-list-item|350726|350727|350728|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|X|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|Y|8|@]|9|@]|A|$]]|$1|K|3|H|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|F|7|10|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|11|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

I fixed this issue on machine disabling the loopback check setting:

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

blocks|key|3129249|text|我使用的是指向"127.0.0.1“的SQL+Server实例的别名。将其更改为"localhost“确实起到了作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3129250|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 was using an alias for an SQL Server instance that pointed to "127.0.0.1".
Changing it to "localhost" instead did the trick.

blocks|key|3342234|text|对于本地使用的用户名，您可能会被误导。这就是我在Windows10家庭版中的情况。当我在控制面板中查看用户时，我看到了名称usrpc01。但是，当我键入net+config+workstation时，用户名似乎是spc01。似乎有人重命名了用户，但内部名称保持不变。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|3342235|由于不知道如何修复windows用户名(以及C:\Users下的文件夹名称，它也是指原来的内部名称)，我在我的数据库服务器上添加了一个新的用户帐户。|3342236|entityMap^0|G|39|24|M|0|0|22|M|8|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]|$9|N|A|O|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|D]]|E|@]|F|$]]|$1|I|3|-4|5|6|7|U|8|@]|E|@]|F|$]]]|J|$]]

You may be misleaded about the username you use locally. That was my case in Windows 10 Home. When I look at users in control panel, I see the name usrpc01. However when I type <code>net config workstation</code>, it appears that the user's name is spc01. Seems like someone renamed the user, but the internal name remained unchanged.

Not knowing how to fix windows user name (and the folder name under <code>C:\Users</code>, which also refers to the original internal name), I added a new user accout on my db server.

blocks|key|3129337|text|如果您的Sql+Server运行的服务器不是域的一部分，并且在连接字符串中您将完全限定的域名(例如xyz.mypc.com)与集成Security=True一起使用，则可能必须切换到使用IP地址、MachineName+(SERVER01)或点(.)以防它在本地托管。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3129338|这对我很有效，使用fqdn导致了上面的错误。|3129339|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|$]]

If your Sql Server is running on a server that's is not part of a domain and in the connection string you use a fully qualifed domain name (e.g. xyz.mypc.com) with Integrated Security=True, you might have to switch to using either the IP address, MachineName (SERVER01), or the dot (.) in case it's locally hosted.

This worked for me, using the fqdn resulted in the above error.

When attempting to connect to a SQL Server 2008 Instance using Management Studio, I get the following error:

<blockquote>
 Login failed. The login is from an
 untrusted domain and cannot be used
 with Windows authentication.
 (Microsoft SQL Server, Error: 18452)
</blockquote>

I can login using SQL Authentication without problem. I've been getting this error all of a sudden. I have Mixed Mode Authentication turned on. 

Does anyone have any experience with this?

Additional Info:
64-bit version of SQL
Enterprise Edition
On Windows 2003 Server

SQL Server 2008 Windows Auth Login Error: The login is from an untrusted domain

数据库软件

身份验证

SQL数据库

SQL Server

数据库

服务器

Windows

尝试使用Management Studio连接到SQL Server 2008实例时，出现以下错误：登录失败。该登录名来自不受信任的域，不能用于Windows身份验证。(Microsoft SQL Server，错误: 18452)我可以使用SQL身份验证登录，没有问题。我突然收到了这个错误。我打开了混合模式身份验证。...

问SQL Server 2008 Windows身份验证登录错误:登录来自不受信任的域
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SQL Server 2008 Windows身份验证登录错误:登录来自不受信任的域EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SQL Server 2008 Windows身份验证登录错误:登录来自不受信任的域
EN