We have SQL Server 2008 installed on 64Bit Windows Server 2003. When we try connect to the local SQL Server using SQL Server Management Studio at the console, we get the error:

A connection was successfully established with the server, but then an error occurred during the login process. provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.

When we try TCP from same local SSMS to local server, we get the same error but intead of the pipe message its something like

"connection forcibly closed".

Now, here is the strange part - we CAN connect to this SQL Server from any other machine on the network using SSMS. - AND - WE CAN'T connect to ANY SQL Server from the problem server.

So it seems the SQL Server instance is fine and accepting remote connections. However, the SSMS on that machine will not connect to any SQL Server even remotely.

When we try an ADO.NET connection from C# remotely we can connect, run that same code on the console of the trouble server and we get the same errors.

How can this be solved?