<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Login failed for user &lt;xx&gt;, Msg 18456, Level 14, State 1</title><link>http://blogs.msdn.com/b/sql_protocols/archive/2007/06/30/login-failed-for-user-xx-msg-18456-level-14-state-1.aspx</link><description>This post focus on a typical cause of sql login failure issue described as the title. 
 In real world, a customer log on to the machine as a domain\user or local machine accout, he can connec to SQL Server through SQL Server Management Studio. However</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Login failed for user &lt;xx&gt;, Msg 18456, Level 14, State 1</title><link>http://blogs.msdn.com/b/sql_protocols/archive/2007/06/30/login-failed-for-user-xx-msg-18456-level-14-state-1.aspx#6971435</link><pubDate>Thu, 03 Jan 2008 23:05:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6971435</guid><dc:creator>John</dc:creator><description>&lt;p&gt;These issue i have had with this error message is our application using the jtds open source driver &amp;nbsp;which by default uses NTLM authentication. &amp;nbsp;Our client used NTLMv2. &amp;nbsp;We were able to put ';useNTLMv2\=true' into our connection string and no longer got this error. &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=6971435" width="1" height="1"&gt;</description></item></channel></rss>