SQL Server Error 1225 RRS feed

  • Question

  • I encountered a problem with my SQL Server 2014 Standard edition. It is denying me access to the Management Studio and I cannot access the SQL Server from Visual Studio. The error message reads,

    "Cannot connect to SQL. Additional information: A network-related or instance-specific error occurred while establishing a connection to SQL Server.  The server was not found or was not accessible.  Verify that the instance name is correct and that SQL Server is configured to allow remote connections (provider: TCP Provider, error: 0 - the remote computer refused the network connection.) (Microsoft SQL Server, Error: 1225).  The remote computer refused the network connection."

    My SQL Server is a stand-alone installation and I have all the permissions.  I would be grateful if anyone could help me with tips on how to solve this problem.

    Thank you.



    Monday, May 16, 2016 5:07 AM

All replies

  • 1. Make sure SQL Server Service is running
    2. If a named instance, make sure SQL Server browser service is running
    3. Make sure SQL Server is configured to allow remote connections
    4. Examine the SQL Server error log for messages confirming that SQL is listening on the expected network interfaces and ports
    5. Test server connectivity with PING from the client machine
    6. Test port connectivity using TELNET or PowerShell to the server and port (from step 4) from the client machine.  For example
    a. TELNET <server-name> 1433
    b. PowerShell: 1433 | % { echo ((new-object Net.Sockets.TcpClient).Connect("YourServerName",$_)) "server listening on TCP port $_" }
    7. Check firewall settings if step 5 or 6 connectivity test fails

    Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/

    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting: Large scale of database and data cleansing
    Remote DBA Services: Improves MS SQL Database Performance
    SQL Server Integration Services: Business Intelligence

    Monday, May 16, 2016 5:08 AM
  • Please follow below Technet Article

    How to Troubleshoot Connecting to the SQL Server Database Engine



    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles


    Monday, May 16, 2016 7:06 AM
  • Hi Uri & Shashank,

    Thanks very much for the assistance provided.  My system was down for several days, just had it cleaned up, that is why the delay in responding.

    I have tried the steps above but didn't get it solved.  I'm not saying those are not what should be done, but I think I have been unable to locate the real problem.  I'll re-install the SQL Server and see what happens.

    Thank you very much.



    Monday, May 23, 2016 1:59 PM
  • can you reply inline what is your comment on above points...


    Make sure SQL Server Service is running--yes running

    so as to get it resolve faster.

    Vinay Thakur http://rdbmsexperts.com/Blogs http://thakurvinay.wordpress.com/ https://twitter.com/#!/ThakurVinay http://vinay-thakur.spaces.live.com/ http://twitter.com/ThakurVinay

    Tuesday, May 24, 2016 1:35 PM
  • For me it was a password issue [a password change] that didn't flow from windows authentication to SQL server.

    I had to go into the services mentioned above and update the password.

    I was then able to start the services.

    I'm now able to get into my localdb.

    Thursday, January 5, 2017 8:29 PM