Remotely connect to the SQL Server2000 Database

I used SQL server2000in the student information management system. Although I had been strongly recommended to use SQL server2008 or SQL server2012 before, I didn't feel any inconvenience at the beginning, so I didn't change it. Besides, I spent a lot of effort to install it, and I felt quite fulfilled. After the system is finished, a major problem occurs during the release, that is, my system can only be installed and run on my local machine. Once I leave this ontology, it cannot run at all. The reason should be remote connection to the database, rather than local connection.
1. ModifyCode: Local Connection Mode: connectstring = "filedsn = studentinfo. DSN; uid = sa; Pwd = ***"
Remote connection method: 1.

 


Connectstring = "provider = sqloledb.1; persist Security info = false; user id = sa; Password = 00000000; initial catalog = 'student '; Data Source = **. **. **. **"

2.

 


Connectstring = "filedsn = studentinfo. DSN; uid = sa; Pwd = 123; server = **. **; persist securityinfo = false"

2. Database settings. (I checked a lot of information and felt that this solution was good and executable)
1. Check whether the IP address of the ping server can be pinged.
This operation is to check whether the physical connection with the remote SQL Server server exists. If not, check the network and view the configuration.
2. Enter the telnet server IP port (eg: Telent 202.114.100.100 1433) in the doscommand line)
(Appendix: Open the telnet service connection link connection understanding connection link http://blog.csdn.net/guolimin1992/article/details/9949503

1433 is the default listening port of SQL Server2000 for TCP/IP. If there is a problem, the common prompt is "... Unable to open 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 Server2000 service. If not, start the server.
2. Check whether the TCP/IP protocol is enabled for the weapon segment because the Protocol is required for remote connection. Method: "START" --"Program"-- Microsoft SQL Server -- server network utility -- check whether the Enable Protocol has the TCP/IP protocol. If not, enable the protocol.
3. Check whether the server's TCP/IP Port is set to 1433 (still in the server network utility) and hide the Server check box not checked
4. If the operating system on the server has been patched with SP2, you must configure Windows Firewall. To open port 1433 to it, I will drop the firewall directly here (including port , if you have other, it is best to handle the same)
5. Check whether the server is listening on port 1433. If the server does not listen on port 1433 of the TCP connection, it cannot be connected. Method: Enter the command line "dos", and run" netstat-a-n "to check whether there are items similar to TCP 127.0.0.1 1433 listening in the result list. If not, you usually need to patch SQL Server with SP3 and view the version number. Method: In the SQL Server2000 query analyzer, input, select @ version for execution, and the result is displayed. patches are required for versions 8.0.2039. Sorry, it is not enough after I patch it !!

3. A series of settings ......

I tried it step by step, even though the last version was the same as before. In the end, I had to share my classmates and remotely connect to his database to complete the system acceptance.
Although it was strongly recommended to use a later version of the database from the very beginning, it seems that there are advantages and disadvantages. Although it takes a lot of time and energy, it also learns a lot of knowledge, if version 12 is used, it may be smooth, but many will be missed, right? Throughout the process, I learned a lot and learned a lot. I will share it with you.

Note:

1. Source Document,Http://wenku.baidu.com/view/c0a1531eff00bed5b9f31d7b.html

2. Enable the telnet service,
Http://blog.csdn.net/guolimin1992/article/details/9949503