SQL Server IP cannot log on issues resolved

Recent project project needs, to deploy the project on the WINDOWS2008R2 server, but the client side of the server is not installed on servers, all to solve their own, so I found a 2008 version, installation, installation process did not encounter any problems, everything is smooth, However, after the installation, open SQL Server Management Studio, with Windows authentication can pass, with SQL Server authentication, in the Server Name column, enter the default

127.0.0.1,1433 can not log in, but input <local> is suspicious log in,, Although the local and 127.0.0.1 are consistent, but the program's connection is written in the above IP and Port Ah, (later released the program test, IP can not log in, the program is unable to execute after the release) below the resolution process is posted for your reference.

ip:127.0.0.1 sure is no problem, ah, and then think of the port may be the problem, so the query port with the use of Windows authentication method to log in, the implementation of the discovery port is 1433 Ah,

--Query port number exec Sys.sp_readerrorlog 0, 1, ' Listening '

This is completely depressed the author. Later thought is not related to the IP service is not open, so go to the Configuration tool under the SQL Server Configuration Manager to view.

Open interface for SQL Server Configuration Manager:

Later found in the "SQL NativeClient10.0 Configuration", TCP/IP is disabled, the amount, this depressed, hurriedly start, again with the IP login is successful,

Here to clarify two questions,

1: Although experienced comrades can see that the environment you said before is windows2008r2, how can you not see it? This is mainly because the environment is the client side, unable to, so I am the problem solved on my native test.

2: Some comrades will find that in win8/win8.1, our program does not want to Win7 or XP as in the Start menu classification, find a such as the less commonly used "SQL Server Configuration Manager" is difficult to locate, here we suspect using Windws's own program search tool (win+ Q call up), you can also install "360 software Assistant", this gadget want to Win7 as suspicious to our program classification, more convenient.

I hope we can help you in the future.