On my computer (WinXP En Prof SP2) I have installed SQL Express 2005 with instance name "SQL2005". Mixed Mode.

I allowed Remote connection to this DB server, enabling TCP/IP protocol on port 1433.
Also SQL Browser is set to autostart.
My firewall is off.

When I try to connect to this server through the CMDline, I use:
sqlcmd -S testpc\sql2005 -U sa -P test

I only get: "Sqlcmd: Error: Microsoft SQL Native Client: Client unable to establish connection due to prelogin failure"

If I use:
sqlcmd -S testpc\sql2005 -U sa -P asdfghjkl (or any password)
the result will be the same.

If I try to connect to the server through the Management Studio, I just get:
"A connection was succesfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error:0 - An existing connection was forcibly closed by the remote host.)(Microsoft SQL Server, Error: 10054)"
or
"A connection was succesfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error:0 - An established connection was aborted byt the software in your machine.)(Microsoft SQL Server, Error: 10053)"


Next I have installed the new DB on new computer (WinXP En Prof SP2) with the same options (using unattended installation in CMD line) and on this computer it works. It means, that I can establish remote connections to that server with any problems.


I have search on internet to solve this problem bud a I didn't find the solution. I found, that this error relates to winsock layer - WSAECONNABORTED(10053) and WSAECONNRESET(10054) error codes.

But I still don't know, how to solve this and remotely connect to my DB Server...

Thanks for your answers.


Edit 1:
I have tried to uninstall MS Net Framework 2.0, Microsoft SQL Native Client, Microsoft Support Files.

When I try localy connect - it doesn't work, of course.
When I try remotely connect:
"sqlcmd -L" shows, that exists "testpc\sql2005"
"sqlcmd -S testpc\sql2005 -U sa -P asdfghjkl" (or any password) generate the same Error as before - nothing changed


Is it problem of MS SQL Server or MS Windows? How to solve this?

Check out the following blog, it contains a lot of information about connection issues.

WesleyB

Visit my SQL Server weblog @ http://dis4ea.blogspot.com

Below links will be helpful,

http://social.msdn.microsoft.com/Forums/en-US/9e738425-8c6e-45fc-ae0c-a63675e67506/sql-server-remote-access-through-ssms-error-10054-error-64?forum=sqldataaccess

http://dba.stackexchange.com/questions/45631/error-10053-connecting-with-management-studio