|
|
You're in the
sql server connect
group:Cant connect through Management Studio, Can connect Visual Studio
sql server connect:
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, DTS Wizard, 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,
One possibility - You mention DTS which is Integration Services in SQL
Server 2005. Since you called it DTS, that makes me think you are successfully connecting from SQL Server 2000, which would be using the SQL Server 2000 client network library. But SQL Server Management Studio is using the SQL Server Native Client. This introduces the possibility that the clients are not using the same protocols. For instance VS and DTS might be using TCP/IP and Management Studio might be using named pipes. So if the SQL Server 2000 client is installed on the client computer, check the client settings for both SQL Server 2000 and SQL Server 2005 and see if they are set to the same settings. Protocol, port number, anything. -- Rick Byham (MSFT) This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Burdock" <Burdock@discussions.microsoft.com> wrote in message
news:071A8879-BAE9-4731-8302-52B9AE26867A@microsoft.com... > 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, DTS > Wizard, > 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
Hi Rick,
Thanks for the response. The DTS program I referred to is an application called 'dtswizard.exe' which I found amongst (I believe) my SQL 2005 installation files. I have uninstalled SQL Server 2000 from my machine now. The only client is 2005 Standard Edition. I've had a few different configurations- 2000 and 2005 Express mostly. Recently I have uninstalled both of these and installed 2005 Standard. The protocol that Management Studio is TCP/IP, not sure about the port number. I am not sure how to check these settings for Visual Studio. What perplexes me is that both MS and VS can get through to the remote server, but the remote server reports invalid logon from MS only. Thanks again for your help! [quoted text, click to view] "Rick Byham, (MSFT)" wrote:
> One possibility - You mention DTS which is Integration Services in SQL > Server 2005. Since you called it DTS, that makes me think you are > successfully connecting from SQL Server 2000, which would be using the SQL > Server 2000 client network library. But SQL Server Management Studio is > using the SQL Server Native Client. This introduces the possibility that the > clients are not using the same protocols. For instance VS and DTS might be > using TCP/IP and Management Studio might be using named pipes. So if the SQL > Server 2000 client is installed on the client computer, check the client > settings for both SQL Server 2000 and SQL Server 2005 and see if they are > set to the same settings. Protocol, port number, anything. > -- > Rick Byham (MSFT) > This posting is provided "AS IS" with no warranties, and confers no rights. > > "Burdock" <Burdock@discussions.microsoft.com> wrote in message > news:071A8879-BAE9-4731-8302-52B9AE26867A@microsoft.com... > > 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, DTS > > Wizard, > > 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
Sorry I'm not helping much. Obviously the same login should work no matter
how you are connecting. Try connecting from your client using sqlcmd. If that works, then you know the problem is related to Management Studio. If that doesn't work, then it's a more general issue. C:\>sqlcmd -S computer\instancename -E (makes a Windows Authentication connection) C:\>sqlcmd -S computer\instancename -U login -P password (makes a SQL Server connection) -- Rick Byham (MSFT) This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Burdock" <Burdock@discussions.microsoft.com> wrote in message
news:EFE9C426-F4E5-4959-B738-7A79CA73FDFE@microsoft.com... > Hi Rick, > > Thanks for the response. The DTS program I referred to is an application > called 'dtswizard.exe' which I found amongst (I believe) my SQL 2005 > installation files. > > I have uninstalled SQL Server 2000 from my machine now. The only client is > 2005 Standard Edition. > > I've had a few different configurations- 2000 and 2005 Express mostly. > Recently I have uninstalled both of these and installed 2005 Standard. > > The protocol that Management Studio is TCP/IP, not sure about the port > number. I am not sure how to check these settings for Visual Studio. > > What perplexes me is that both MS and VS can get through to the remote > server, but the remote server reports invalid logon from MS only. > > Thanks again for your help! > > > "Rick Byham, (MSFT)" wrote: > >> One possibility - You mention DTS which is Integration Services in SQL >> Server 2005. Since you called it DTS, that makes me think you are >> successfully connecting from SQL Server 2000, which would be using the >> SQL >> Server 2000 client network library. But SQL Server Management Studio is >> using the SQL Server Native Client. This introduces the possibility that >> the >> clients are not using the same protocols. For instance VS and DTS might >> be >> using TCP/IP and Management Studio might be using named pipes. So if the >> SQL >> Server 2000 client is installed on the client computer, check the client >> settings for both SQL Server 2000 and SQL Server 2005 and see if they are >> set to the same settings. Protocol, port number, anything. >> -- >> Rick Byham (MSFT) >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> "Burdock" <Burdock@discussions.microsoft.com> wrote in message >> news:071A8879-BAE9-4731-8302-52B9AE26867A@microsoft.com... >> > 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, DTS >> > Wizard, >> > 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 >>
Hi Rick,
I can connect through sqlcmd, as per your instructions, it's just Management Studio that causes the 'invalid logon'. I really am stumped! Martin
Martin,
If your remote server is "Registered" in your SQL Server Management Studio, you probably registered a login and password when setting up the registration. Try deleting your registration and recreating it, re-entering your login and password, to see if that resolves the problem. An invalid password in 2005 now returns 'Login failed for user xxx (18456)'. This is a part of greater security, by not giving any hints as to what is actually wrong. RLF [quoted text, click to view] "Burdock" <Burdock@discussions.microsoft.com> wrote in message news:9725A895-00E4-4081-BE8C-64D2ECD67301@microsoft.com... > Hi Rick, > > I can connect through sqlcmd, as per your instructions, it's just > Management > Studio that causes the 'invalid logon'. > > I really am stumped! > > Martin >
Hi Russell,
Thanks for the reply. The remote server is not registered in my Management Studio- in fact my Object Explorer is completely empty. Every time I try and connect I select 'Connect > Database Engine' and re-enter the server name, login and password. I am beginning to wonder it is a problem with the configuration of the remote SQL Server. But the ISP are confident it is not a problem at their end. Thanks for your help, Martin [quoted text, click to view] "Russell Fields" wrote:
> Martin, > > If your remote server is "Registered" in your SQL Server Management Studio, > you probably registered a login and password when setting up the > registration. Try deleting your registration and recreating it, re-entering > your login and password, to see if that resolves the problem. > > An invalid password in 2005 now returns 'Login failed for user xxx (18456)'. > This is a part of greater security, by not giving any hints as to what is > actually wrong. > > RLF > > > "Burdock" <Burdock@discussions.microsoft.com> wrote in message > news:9725A895-00E4-4081-BE8C-64D2ECD67301@microsoft.com... > > Hi Rick, > > > > I can connect through sqlcmd, as per your instructions, it's just > > Management > > Studio that causes the 'invalid logon'. > > > > I really am stumped! > > > > Martin > > > >
Hi,
My ISP found the solution via a MSDN post. It is possibly the most bizarre fix I have ever encountered! [i]# 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.[/i]
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |