Not able to access server on the same Domain RRS feed

  • Question

  • Hi ,

    I have 2 different SQL server setups (say setup1 and setup2) in 2 separate locations, but in the same domain say (xxdomain)

    When I give access to a user from setup1 to setup2 I get the below error message.

    Cannot connect to xxx.xx.xx.xx.


    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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

    Am I missing something..

    Saturday, August 30, 2014 4:03 PM


All replies

  • Hi

    In SQL configuration enable Named Pipes and TCP/IP, restart your sql services and it should work.

    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Saturday, August 30, 2014 4:22 PM
  • In addition to Ed's suggestion, make sure the SQL Server port is reachable from the client machine (e.g. not blocked by firewall).

    Dan Guzman, SQL Server MVP, http://www.dbdelta.com

    Saturday, August 30, 2014 5:23 PM
  • Hello

    Please see my answer on this one


    Javier Villegas | @javier_villhttp://sql-javier-villegas.blogspot.com/

    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

    Saturday, August 30, 2014 9:13 PM
  • Hi,

     TCP/IP is enabled and Firewall is disabled (so I guess port 1433 would not be blocked)..right?

    Still issue persist.

    Sunday, August 31, 2014 6:44 AM
  • Is the server a named instance or the default instance?  If you are attempting to connect to a named instance of SQL Server then you'll need to find out which port the instance is listening on and confirm that port isn't blocked by a firewall.

    And just because a software firewall isn't blocking a port doesn't mean a hardware firewall isn't blocking the port.

    Use ping to test connectivity between the client PC and server.

    Are both client and server on the same subnet?  If not then there's a router between the two machines and possibly a firewall.

    Sunday, August 31, 2014 6:50 AM
  • its a default instances.
    Sunday, August 31, 2014 6:57 AM
  • Hi Sudhakar Vallamsetty,

    According to your error message , the error 53 means the client stack cannot find the target machine. We need to verify if you type the right server name, and make sure if your SQL Server instance is allowed to connect remotely. Since you disable the firewall, we need to verify if you configure the firewall to allow connections to the TCP port (1433) and UDP port (1434) , which are used by the Database Engine. Also check if the firewall is blocking the named pipes port, which usually is 445.

    For more information, see: Configure a Windows Firewall for Database Engine Access


    There is an article about how to troubleshoot connecting to the SQL Server database Engine.


    Sofiya Li

    Sofiya Li
    TechNet Community Support

    • Marked as answer by Sofiya Li Tuesday, September 9, 2014 5:30 AM
    Monday, September 1, 2014 9:02 AM
  • See my detailed troubleshooting steps on the SQL Server TechNet wiki at How to Troubleshoot Connecting to the SQL Server Database Engine   

    Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

    Tuesday, September 2, 2014 3:29 PM