2/7/2018 11:09:46 AM
When you try to connect to an instance of Microsoft SQL Server 2012 Express from a remote computer, you might receive an error message.
Named SQL instances listen on dynamic ports. This is the function of the Sql Server Browser Service to inform the clients of the actual port. The Sql Browser listens on UDP 1434 and answers all client request with the port number the current instance is using. Sql Server Browser service is required for both TCP and named pipes protocols. SQL Server Browser is used by clients transparently and there is no need for special configuration.
To configure SQL Server 2012 Express to allow remote connections, you must complete these steps:
Update 2015.05.11
If you want to use GPO to configure SQL server Standard or Enterprise to accept remote connections see my new post: How to use GPO to allow SQL 2012 accept remote connections
1. Open SQL Management Studio and right-click server name in the left pane and select Properties
2. In the center pane, is a column that lists the Process ID for each running service. Look for the PID in the row for SQL Server. Identify the port that that PID is listening on by typing this into a command prompt:
netstat -ano | find /i “PID-Number-Of-SQL-Server”. Based on the details shown in Figure 3 syntax is the following: netstat -ano | find /i “116”. The results are shown in Figure 4.
6. In SQL Server Configuration Manager and click on SQL Server Network Configuration in the left pane and right-click TCP/IP protocol and select option Properties. Goto IP Address tab and scroll-down to APAll section. Remove value for TCP Dynamic Ports (do not enter Zero 0 !!!) and enter the port 1433 for TCP Port.
Four exceptions must be configured in Windows Firewall to allow access to SQL Server:
Source: https://blog.citrix24.com/configure-sql-express-to-accept-remote-connections/
Administrator
2/7/2018 11:09:46 AM
1/1/0001 12:00:00 AM
https://yoong.vn/