SQL Server *stil* does not allow remote connections

  • Hi,

    Attempting to open a new database engine from a Windows 2003 R2 server (x64) which is

    running SQL Server 2005 to my desktop PC (XP Pro) which is running SQL 2005 developer edition.

    I’ve opened up TCP/IP and named pipes and enabled all protocols within surface area configuration and server

    configuration manager but get this…

    An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)

    Is this a red-herring type message? I ask because the text states “this failure may be caused” and as far as I can see I’ve open up my

    PC to all connections.

    Thanks in advance

    Dave

  • Neglected to see that I've also tried this with the firewall off

  • Check first if you enabled the SAC settings for database engine from the Windows 2003 R2 server (x64) and not for your local installation;

    Then if the sql server runs on different port than the default one then you have to define an alias for the remote instance using SQL Server Configuration Manager from your Client Tools installation.

     

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

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