title: Sql server authentication fails using SSMS but works when using sqlcmd
body: <p>I have my <strong>SQLServer 2005 Standard</strong> instance configured for mixed mode fine. When using SSMS, none of the sql server logins seem to work. Just "Login failed for user '..'" message. But when I use SQLCMD, it works fine. The behavior is not just for one specific login account. All sql server logins including 'sa' fail when tried via SSMS. Windows logins work fine.</p>
  
  <p>Any ideas?</p>
  
  <p><strong>EDIT1:</strong>
  When connecting via SQLCMD, I do not specify the -S option. Just the -U and -P
  Whereas in SSMS, Server name defaults to the machine name.
  In SSMS the server seems to be registered as say xxxxN. When I connect using windows authentication, my @@servername returns xxxx_N. 
  When I try to use the xxxx_N in SSMS it fails to connect altogether.</p>
  
  <p><strong>Edit2:</strong>
  When trying via SQLCMD if I give the -S option as xxxxN, it works fine too.</p>
  
  <p><strong>Edit3:</strong></p>
  
  <p>My SQLCMD:</p>
  
  <p>C:...>SQLCMD -U sa -P Password   (works)</p>
  
  <p>C:...>SQLCMD -S xxxxN -U sa -P Password   (works)</p>
  
  <p>C:...>SQLCMD -U test -P Password   (works)</p>
  
  <p>C:...>SQLCMD -S xxxxN -U test -P Password   (works)</p>
  
  <p>in SSMS:</p>
  
  <p>ServerType: Database Engine</p>
  
  <p>ServerName: xxxxN</p>
  
  <p>AUthentication: Windows Authentication          (works)</p>
  
  <p>ServerType: Database Engine</p>
  
  <p>ServerName: xxxxN</p>
  
  <p>AUthentication: Sql Server Authentication        </p>
  
  <p>Login: sa</p>
  
  <p>Password: Password                       (fail)</p>
  
  <p>ServerType: Database Engine</p>
  
  <p>ServerName: xxxxN</p>
  
  <p>AUthentication: Sql Server Authentication        </p>
  
  <p>Login: test</p>
  
  <p>Password: Password                       (fail)</p>
  
  <p><strong>EDIT 4(Answer)</strong></p>
  
  <p>ODBC connections using sql accounts seem to work fine.
  SSMS connections from remote machines work fine also. 
  This HAS TO BE an issue with local SSMS install. I believe a reinstall would fix this..</p>