Hosts file used by Microsoft TCP/IP for Windows

Windows 7 cannot save the changed hosts. The main reason is that the hosts file is not opened as an administrator.

First, open the text editor as an administrator by right-clicking the editor icon and selecting administrator, open the system32/Drivers/etc/hosts file in the Windows directory in the text editor, and save the modification.

 

After opening the file, you will see the following:

192.168.1.234 devserver

 

The machine name is bound to the IP address. If the IP address of the SQL Server can be connected to the server, but the server name cannot, you can use the above method.

 

If the network segment or remote server is not the same, add the corresponding relationship to the local system network configuration file. The file is located at % SystemRoot % \ system32 \ drivers \ etc \ hosts.

Configuration method: use NotePad to open the hosts file and add the ing between the IP address and the host name at the bottom of the file. :

 

 

Sometimes the client and server are not in the same LAN. At this time, the server name may not be used to identify the server directly.
You can use the hosts file for name resolution. The specific method is as follows:
1. Use notepad to open the hosts file (usually in c: \ winnt \ system32 \ drivers \ etc ).
2. Add a record corresponding to the IP address and server name, for example:
172.1610.24 myserver
You can also configure it in the SQL Server Client Network utility, which will be described in detail later.
Second, use the Telnet command to check the SQL server's working status:
Telnet <Server IP addresses> 1433
If the command is successfully executed, you can see that the cursor keeps flashing in the upper left corner after the screen flashes. This indicates that the SQL Server is working normally and
Listen to the TCP/IP connection of port 1433. If the command returns the error message "cannot open the connection", it indicates that the server has not started the SQL Server service.
Or, the TCP/IP protocol is not enabled on the server, or the server does not listen on the default port 1433 of SQL Server.

Detailed source reference: http://www.jb51.net/article/19937.htm