Ways to remotely connect to a SQL Server 2000 Server

Requirements are as follows: you need to remotely connect to a foreign SQL Server 2000 Server.

Test condition: A public network IP, two static IP.

Specific steps:

A, ping server IP can ping pass

Observe whether the physical connection exists for the remote SQL Server 2000 Server. If not, check the network to see the configuration, and, of course, make sure that the remote SQL Server 2000 server has the correct IP spelling.

Second, in the DOS or command line to enter Telnet server IP port, see whether connectivity

such as Telnet 202.114.100.100 1433

Typically, the port value is 1433 because 1433 is the default listening port for TCP/IP for SQL Server 2000. If there is a problem, usually this step will go wrong. The usual hint is "... Unable to open connection, connection failed.

If there is a problem with this step, you should check the following options.

1, check whether the remote server has started the SQL Server 2000 service. If not, start.

2, check the server side has not enabled the TCP/IP protocol, because remote connection (via the Internet) need to rely on this protocol. The check method is to open the Start menu on the server-> program->microsoft SQL server-> Server Network Utility to see if there is a TCP/IP protocol in the enabled Protocol, and if not, enable it.

3, check the server's TCP/IP port is configured to 1433 ports. Still in the Server Network Utility, view the properties of the TCP/IP enabled in the protocol, ensure that the default port is 1433, and that the Hide Server checkbox is not checked.

In fact, if the default port is modified, it is OK, but when the client does a Telnet test, the port number of the write server must be the same as the server-configured port number. If the Hidden server checkbox is checked, it means that the client cannot see the server by enumerating the servers, and that it protects, but does not affect the connection, but the default port for the TCP/IP protocol is implicitly modified to 2433 and must be changed when the client connects.

4, if the server-side operating system has played a SP2 patch, the Windows Firewall must be configured, to open 1433 ports to it, usually in the test can be directly turned off Windows Firewall (other firewalls are also turned off the best).

5, check whether the server is listening on the 1433 port. If the server is not listening on the 1433 port of the TCP connection, it is not connected. The check method is to enter Netstat-a-N or Netstat-an below the server's DOS or command line, and see if there are any items similar to the TCP 127.0.0.1 1433 listening in the results list. If not, you typically need to have at least SP3 patches on SQL Server 2000. In fact, start Query Analyzer on the server side, enter the SELECT @ @version can see the version number, version number under 8.0.2039 needs to be patched.

If the above is all right, then you do telnet server IP 1433 test, you will see the screen after a flash of the cursor in the upper left corner flashing. Congratulations, you can start the connection in Enterprise Manager or Query Analyzer immediately.