Go to the remote machine to see whether it returned the correct ipaddress. Ping (if your remote server has ipv6 enabled, it might return ipv6 address). You'd better go through the following checklist to fix the "connection refused" problem.ġ) Are you connecting to the right server? Check out whether your target machine name is valid.Ģ) Whether the you specified in your connection string resolve to the correct ipaddress? do: Secondly, this error is winsock error "WSAECONNREFUSED - 10061". " or your client protocol setting ask for first try Named Pipe connection, if fails, then fallback to TCP connection. For eg, in "Client NetworkUtility", you see the protocol order is "np on top of tcp".
xx", which indicates that either your connection string explicitly use 'tcp:" prefix, say "Server=tcp. In this post, I am trying to list out potential cause and general solution to this specific error when you are making connection to SQL Server 2005.įirst, It is due to TCP connection fail, since you can tell from the title, "TCP Provider.
0 kommentar(er)
