Post reply

Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

  • July 16, 2010 at 12:36 pm

    #224860

    Hi,

    We have SQL Server 2000 with SP4 and getting the below error:

    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)

    Please advice where to check whether remote connections are enabled ot not in SQL Server 2000?

  • July 16, 2010 at 1:22 pm

    #1194325

    Check to make sure that TCP port 1433 is not being blocked by a firewall; use Server Network Utility to make sure TCP/IP is enabled.

    _________________________________
    seth delconte
    http://sqlkeys.com

  • July 16, 2010 at 1:24 pm

    #1194327

    On SQL Server 200 box, Is the remote connections need to enable on MSDTC? (Go to Start->All Programs->Component Services->Computers->My Computer->Right Click->MSDTC->Security Configuration)

    In which case, we need to enable Network DTC access (and check all the 4 options under Network DTC)?

    and in which case, its NOT required to enable Network DTC access?

    please see the attachment

    Please advice

  • July 16, 2010 at 1:25 pm

    #1194329

    Thanks Seth,

    Check to make sure that TCP port 1433 is not being blocked by a firewall; use Server Network Utility to make sure TCP/IP is enabled

    TCP Port 1433 is Open...

    please advice

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply