
Originally Posted by
NOTORIOUS GZD
Did some snooping around, results narrow down to your network communication protocol.
"The Server and the Client must both be using the same network communication protocol. For example if the client is talking Named Pipes, the server must be listening on named pipes. To verify this use the Server Network Utility on the SQL Server machine and the Client network utility on the client computer.
Typicaly the server will list Named Pipes and then TCP/IP and the client will list TCP/IP and named pipes. However their are other protocols that the client and server can use as well.
Another possibility is that the Security context of the MS SQL Server process does not have Administration privilideges on the server or it does not have permission to open a tcp/ip socket."