SQL Remote Connection for SQL Server 2022 is not working

Thirthaprasad S G 26 Reputation points
2024-11-26T06:56:53.8666667+00:00

MS SQL Server 2022 Developer Edition. With local SSMS it is working fine.

  1. Network TCP connection with 1433 enabled (For Localhost and IP Address)
  2. Firewall incoming connections for 1433 port enabled on both systems
  3. "Allow Remote Connections" enabled for the SQL instance
  4. SQL Server and SQL Server Browser services are Running

But it doesn't allow Local / Remote Telnet or Remote connection to the instance with the usual error: Network related / instance specific (Below screenshot)

What else is required to enable Remote connections

Please note as mentioned above, even the telnet to localhost with 1433 port doesn't work.

User's image

Can the experts throw some light on this peculiar issue, anything specific to version 2022 missing...?!

Thanks

Thirthaprasad S G

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
14,165 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Thirthaprasad S G 26 Reputation points
    2024-11-27T06:05:55.6266667+00:00

    Thanks for your suggestions and inputs LiHongMSFT and Bruce (SqlWork.com).

    I forgot to mention that, even the LOCALHOST was unable to connect to port 1433 in the present scenario. In previous versions of SQL (2014) though it was connecting Remotely but wasn't happening with localhost.

    I have finally figured it out. It is the TCP/IP port for "IPAll" portion which was not specified to use 1433 leading to this connectivity issue with localhost as well as from Remote Hosts. Once I specified the port 1433 in IPAll settings and restarted the SQL Server service, both connections worked successfully.

    Thanks to All.

    Below is the screenshot of that particular setting which made all the trick possible...!

    User's image

    1 person found this answer helpful.

  2. LiHongMSFT-4306 29,276 Reputation points
    2024-11-26T08:54:22.6866667+00:00

    Hi @Thirthaprasad S G

    Regarding this connect issue, it is suggested to troubleshoot follow by this doc: A network-related or instance-specific error occurred while establishing a connection to SQL Server.

    Best regards,

    Cosmog


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".


  3. Bruce (SqlWork.com) 68,311 Reputation points
    2024-11-26T23:11:15.0433333+00:00

    you are probably using dynamic port assignment. you need to assign a particular port or open range: 49152–65535. with dynamic, the port changes every time the server starts. also you need UDP port 1434 for clients to find the named instance.

    for more info see:

    https://learn.microsoft.com/en-us/sql/sql-server/install/configure-the-windows-firewall-to-allow-sql-server-access?view=sql-server-ver16

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.