ALWAYS On Setup problem

  • interest

    SSC Rookie

    Points: 33

    While configuring N1 and N2  Nodes connected to DC  Domain Controller working fine.

    Establishing connection through Registering  Server  from SSMS  on Server (N2) is able to accessing  N1.

    When trying to establish on N1 for N2 gives an error.

    TITLE: Edit Server Registration Properties


    Testing the registered server failed. Verify the server name, login credentials, and database, and then click Test again.



    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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

    But REGISTER SERVER from SSMS on N1 is NOT CONFIGURING for N2 for which IP Address (1433) is added on TCP/IP under Configuration Manager.

    N2 could show N1  (entry) but N1 is denied N2 (Server) in the Registering Server from SSMS on N1 Node.

    Any Suggestions. Thanks

  • John Mitchell-245523

    SSC Guru

    Points: 148745

    Is N2 set up to record failed logins in the errorlog?  Are there any such messages in the errorlog?

    By the way, I would not recommend installing SSMS on the database server itself.  It uses resources that should be dedicated to the databases, it means you have to grant users permission to log on to the server interactively, and it uses up one of the two RDP connections to the server, which may be needed by someone doing proper admin work.


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

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