sql server connect: The incident involves two Windows Server 2003 based computers S and C. They
are hosted by two different hosting companies in two different countries.
They both have SQL Server 2000 SP3 installed and running.
The development is done on an XP Professional SP2 based desktop.

The objective is to make a SQL instance on C act as client of an instance on
S which listens on port TCP 1433. The registration of the S instance in SQL
Server Enterprise Manager on C has been successful. However the connection
fails.
Consequently I tried to use various diagnostic tools and hints given in
various KB articles.
PING works OK. FTP connection also works fine.

PortQry from C to S gives the following result:
==========================================
Starting portqry.exe -n <IPaddress of S>-e 1433 -p TCP ...
Querying target system called:
<IPaddress of S>-
Attempting to resolve IP address to a name...
IP address resolved to <correct computer name of S>
querying...
Error opening socket: 10065
No route to host.
portqry.exe -n <IPaddress of S>- -e 1433 -p TCP exits with return code
0x00000063.
===========================================
The same query from the development computer gives the result LISTENING.

Questions:
1. What exactly means Error opening socket: 10065? How should I fix the
problem?
2. Why does the result depend on the computer which makes the query?

Thanks, Dan

10065 equates to a Winsock Error, Host Unreachable.
This sounds like a tcp routing issue.

Try using tracert to the same host /IP address.


Thanks,

Kevin McDonnell
Microsoft Corporation

This posting is provided AS IS with no warranties, and confers no rights.