Solve the problem of one SQL connection failure

A long time out of environment, a newly installed Windows Server 2008 R2 environment, foundProgramCannot connect to SQL Server.

 

1. Failed to connect with test. udl.

 

2. Capture the Network Package and check that the three handshakes are successful. The reason why SQL server returns the network package.

458 7:53:48 am 7/12/2012 33.3707944 system 10.4.2.5 10.4.2.7 smb2 smb2: R-nt status: System-error, code = (22) status_more_processing_required Session Setup (0x1 ), sessionflags = 0x0 {smbovertcp: 12, TCP: 11, IPv4: 9}

3. Therefore, add the Telnet client to the feature of Windows Server 2008 R2 and find that port 1433 of SQL Server is disconnected.

 

4. Remotely connect to the SQL Server and run the netstat-ano command to check whether port 1433 is being monitored by the SQL server.

The process for listening to 4288 is sqlservr.exe, and the process ID is.

 

5. Open the configuration of Windows Firewall and click Advanced Settings.

Choose inbound rules-> new rules-> port-> TCP: 1433-> allow the connection-> domain, private, public-> name: SQL 1433

Save.

 

6. Return to the client machine and telnet the SQL again. The SQL connection is successful.

 

Summary

==============================

In this troubleshooting, we used the Telnet and netstat commands.

The udl file is also used to test the connection to the SQL service.

To solve the problem, we created a Windows Firewall rule that allows other machines to connect to the SQL service.

 

This is a typical troubleshooting of SQL connection. I hope you will be helpful.

 

Thank you

============================

Thank you for your help.