Steps to troubleshoot SQL connectivity issues
Question
Wednesday, April 30, 2008 4:40 PM | 4 votes
Please follow this blog to troubleshoot SQL connectivity issue and post question here.
Steps to troubleshoot SQL connectivity issues
Lot of blogs related to SQL connectivity issue are available sql_protocols blog.
http://blogs.msdn.com/sql_protocols
(Update: Please search your error message in this forum before you post your question, there are probably already answers in previous posts. If your scenario is different, please start a new thread rather than appending to old ones. Please reply this thread if this searching step solves your issue. We would like to hear from you. Thanks).
All replies (7)
Thursday, January 5, 2012 5:36 AM
Thanks for your good information.
I followed your step to step2, the log file showed "error :9003, severity: 20, state:1".
Could you teach me how to solve this problem or could you provide the URL for how to uninstall SQL Server 2008 and reinstall"
thank you very much
I have uninstall and reinstall the SQL Server 2008 already.
Thanks for your read.
Thursday, August 2, 2012 9:04 PM
The SQL Server connection tool pointed me at the problem- my connection string user and password were being ignored in favor of the windows login I happened to be using.
Monday, March 4, 2013 3:50 AM | 1 vote
In lieu of TELNET, one can check port connectivity with the PowerShell command below. Specify the desired port number instead of the default instance port 1433 as needed.
1433 | % { echo ((new-object Net.Sockets.TcpClient).Connect("YourServerName",$_)) "server listening on TCP port $_" }
Dan Guzman, SQL Server MVP, http://www.dbdelta.com
Saturday, March 16, 2013 9:51 PM
I have done the tests recommended in you post by going through the steps in "Steps to troubleshoot SQL connectivity issues" Turning off the Firewall solved the problem, but naturally, I don't want to leave it turned off.
Here are the settings I have changed and the results:
Firewall off: Instant connection.
Domain Profile: Inbound connections changed from Block to Allow. (No results) Time Out at 15 seconds
Private Profile: Inbound connections changed from Block to Allow. (No results) Time Out at 15 seconds
Public Profile: Inbound connections changed from Block to Allow. (No results) Time Out at 15 seconds
All three of the above set to Allow (No Results) Time Out at 15 seconds
IPSec Settings: All computers on the domain added to Only Allow Exceptions. (No results) Time Out at 15 seconds
IPSec Settings: Added Domain Admins to Only Allow Authorized list.
Are there any other firewall settings I can try resetting?
Tom Childers, Radio Amateur N5GE, Licensed since 1976, QCWA Member 35102, ARRL Life Member
Friday, February 3, 2017 6:38 AM | 3 votes
You can now use the following troubleshooter to solve majority of connectivity issues when working with SQL Server.
Solving connectivity issues to SQL Server
Please check and share any additional feedback for improvements using the Feedback button at the bottom of the troubleshooter or through comments section in the following blog post on PSSSQL
Guided walkthrough just got published..
Thanks.
Ramu.
Friday, February 3, 2017 11:39 AM | 1 vote
This is great, Ramu! I'll be sharing like this in answers for those that missed your post.
Dan Guzman, Data Platform MVP, http://www.dbdelta.com
Saturday, February 4, 2017 2:47 AM
Thank you Dan. Truly appreciate your help in extending the reach of this doc. If you can think of any additional scenarios or improvements that can be added to this, please do let me know and I can work on the same.
Regards.
Ramu.