Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
browneye
Starting Member
3 Posts |
Posted - 2007-08-29 : 03:15:41
|
Hi,I am having a very frustrating problem trying to connect to a remote SQL Server 2005 at my ISP. When I try to connect through Management Studio the ISP SQL Server returns an error of 'Login failed for user xxx (18456)'. According to the ISP they can see my connection attempt in their logs.However, I can access the same SQL Server through Visual Studio, and UDL files using exactly the same credentials.The ISP have given up, and this is driving me crazy!I will be very, very grateful for any help or suggestions.Thanks,Martin |
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-08-30 : 01:07:59
|
What's sql2k5 sp level in isp? Does your machine have same sp? |
 |
|
browneye
Starting Member
3 Posts |
Posted - 2007-08-30 : 09:09:58
|
Thanks for the reply!Both myself and the ISP are running Service Pack 2.Martin |
 |
|
browneye
Starting Member
3 Posts |
Posted - 2007-08-30 : 10:53:08
|
Hi,My ISP found the solution via a MSDN post. It is possibly the most bizarre fix I have ever encountered!# re: Understanding "login failed" (Error 18456) error messages in SQL Server 2005 Like every one else, I was frustrated by the strange 18456 error with State=8. I store my password in a textfile, and when I need it, I do a copy and paste into the password field. I use a password something like "Ity@1%6$9#g".I tried a number of "strangies", but this one worked on more than one occasion: using the direction arrow key pointing left, I moved the cursor back to the beginning of the password. It worked!Try this at home, folks, it does not hurt a bit, and perhaps it might give the Microsoft boys a hint about the nature of the problem if you report the results.http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx |
 |
|
|
|
|
|
|