How to remotely connect to the SQL Server2000 Database

Remote connection to SQL Server 2000 Server Solution
Check whether the IP address of the ping server can be pinged.

This is actually reading and remote SQL
Whether the physical connection of the server 2000 exists. If not, check the network and check the configuration. Make sure that the IP address of the Remote SQL Server 2000 Server is correctly spelled.

2. Enter the IP port of the Telnet server in DOS or command line to check whether the port can be connected.

For example, Telnet 202.114.100.100 1433

Generally, the port value is 1433, because 1433 is SQL Server.
The default listening port of 2000 for TCP/IP. If there is a problem, this step usually has a problem. The common prompt is "... Unable to open the connection, connection failed ".

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

1. Check whether the remote server has started the SQL Server 2000 Service. If not, start.

2. Check whether the TCP/IP protocol is enabled on the server. This Protocol is required for remote connection (over the Internet. The check method is to open
Start Menu->Program-> Microsoft SQL Server-> server network utility to check whether the enabled Protocol has the TCP/IP protocol. If not, enable it.

3
Check whether the TCP/IP Port of the server is configured as port 1433. Check the TCP/IP attribute in the enabled protocol in the server network utility to make sure that the default port is 1433 and the check box of the hidden server is not checked.

In fact, it is acceptable if the default port is modified. However, when the client performs a telnet test, the server port number must be consistent with the port number configured on the server. If the "Hide server" check box is selected, it means that the client cannot see this server by enumerating the server, which protects the server but does not affect the connection, however, the default port of TCP/IP protocol is implicitly modified to 2433, which must be changed when the client is connected.

4
If the operating system on the server has been patched with SP2, you must configure Windows Firewall and open port 1433 to it, you can usually turn off the Windows Firewall directly during testing (Other firewalls are also the best ).

5. Check whether the server listens on port 1433. If the server does not listen on port 1433 of the TCP connection, it cannot be connected. The check method is to input

Netstat-a-n or netstat-An. Check whether TCP 127.0.0.1 1433 listening is available in the result list.
. If not, you usually need to patch SQL Server 2000 with at least SP3. In fact, start the query analyzer on the server and enter select @ version
After the script is executed, you can see the version number. All Versions earlier than 8.0.2039 must be patched.

If there is no problem, then Telnet Server IP address 1433 again.
Test, you will see the screen flashing, the cursor in the upper left corner of the non-stop flashing. Congratulations, you can start to connect to the Enterprise Manager or query analyzer immediately.

3. Check client settings

Program> Microsoft SQL Server>
Client Network Tools. Make sure that the client TCP/IP protocol is enabled, as in the server network utility, and the default port is 1433 (or other ports, consistent with the server ).

4. query the analyzer connection test in the Enterprise Manager or

Enterprise Manager-> right-click sqlserver group-> Create sqlserver registration-> next-> Write Remote IP-> next-> select sqlserver login-> next-> write login name and password (SA, password)-> next-> finish

Query analyzer-> file-> connection-> Write Remote IP-> write login name and password (SA, password)-> OK

It is usually recommended to do this in the query analyzer, because by default, the timeout setting for registering another SQL server through the Enterprise Manager is 4 seconds, and the query analyzer is 15 seconds.

Modify the default connection timeout method:

Enterprise Manager> Tools> Options> SQL
In the "Server Enterprise Manager properties" window, click the "advanced" tab-> connection settings-> enter a large number in the box after logon timeout (seconds)

Query analyzer-> tool-> Option-> connection-> enter a large number in the box after logon timeout (seconds)

Generally, you can connect to IOT platform. If an error is prompted, proceed to the next step.

Five errors are usually caused by the use of "only
Windows "authentication method, so you cannot use the SQL Server login account (such as SA) to connect. The solution is as follows:

1
Use the enterprise manager on the server side and select "use Windows Authentication" to connect to SQL Server.

2. Expand SQL
Server group ", right-click the name of the SQL Server server, select" properties ", and then select the" Security "tab.

3. Under "authentication", select "SQL
Server and windows ".

4. Restart the SQL Server service. (Net stop under DOS or command line
MSSQLServer is a quick way to stop the service and start the service ).

Note: When connecting to the local server, the named pipe protocol is usually used (this is enabled in the server network utility). The default port is 445, therefore, local connectivity cannot be explained. connecting to a remote server is a completely different protocol)