Post reply

Frustration on remote connection to SQL Server

  • November 26, 2009 at 2:36 am

    #214256

    Hello gents

    Here is the problem. On server *.*.*.20 there is a SQL Server installed with a default instance MSSQLSERVER ruuning. The port 1433 has been added to the exception list in the windows firewall. But I tried to connect to the SQL Server by its IP address through SSMS using windows authentication from *.*.*.18 but the typical connection error (which you've probably seen before) is reported:

    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.

    From .18 I can successfully ping .20 and I also tried to shut down the firewall completely on .20 but the above error persists.

    For now, I can't think of anything else that I can do to fix this. Could anybody offer a hand?

    Thanks in advance!

    Bazinga!

  • November 26, 2009 at 2:46 am

    #1084494

    run sp_configure 'show advanced options', 1

    reconfigure with override

    Then sp_configure will display the settings, what is set for the value of 'remote access' is it set to 1

    Facts are stubborn things, but statistics are more pliable - Mark Twain
    Carolyn
    SQLServerSpecialists[/url]

  • November 26, 2009 at 2:55 am

    #1084499

    Just did the sp_configure, it is set to 1.

    remote access(name)0(minimum)1(maximum)1(config_value)1(run_value)

    Bazinga!

  • November 26, 2009 at 3:15 am

    #1084510

    You could try adding an alias to the server in SQL Server configuration manager, that sometimes works. Another thing that I've seen work is to have an actual mapping to the remote server.

    Facts are stubborn things, but statistics are more pliable - Mark Twain
    Carolyn
    SQLServerSpecialists[/url]

  • November 26, 2009 at 3:26 am

    #1084512

    Thanks very much for your advice, Carolyn.

    I've just located the cause of the problem, it is that in SQL Server Configuration Manager, TCP/IP protocol for SQL Server Network Configuration was not enabled. And now I just enabled it and all works fine.

    I probably overlooked this setting during the installation process of SQL Server.

    Bazinga!

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

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