Unable to access SQL server from public network

Pradeep Sahoo 21 Reputation points
2021-07-05T07:26:01.18+00:00

We have setup a SQL server within our windows virtual machine. However, it is not accessible from the public network.

We have opened the TCP ports 1433 and 1434 by creating the firewall rule
RDP is accessible. And we are able to use the SQL Management studio from within the VM but not from the public network.

Are we missing any configuration?

Any help would be much appreciated.
Thanks in advance

SQL Server | Other
0 comments No comments
{count} votes

Accepted answer
  1. Erland Sommarskog 121.9K Reputation points MVP Volunteer Moderator
    2021-07-05T07:37:56.197+00:00
    1 person found this answer helpful.
    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Seeya Xi-MSFT 16,586 Reputation points
    2021-07-05T09:06:31.91+00:00

    Hi @Pradeep Sahoo ,

    Please refer to this: https://learn.microsoft.com/en-us/troubleshoot/sql/connect/resolving-connectivity-errors, which can handle regular connection issues.
    This blog is about Making SQL Server Accessible Over Internet. Among these steps, have you completed the fourth step?
    And if your server is SQL Server Express - make sure it is configured to accept remote connections (this is disabled by default in SQL Express, it listens local connections only).
    See here for example how to enable SQL Express to accept remote connections.
    Could you provide the error message which will be helpful for solving the problem?

    Best regards,
    Seeya


    If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar queries.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments No comments

  2. Pradeep Sahoo 21 Reputation points
    2021-07-05T09:10:48.963+00:00

    Thank you @Erland Sommarskog for your prompt help.
    It worked! The firewall configuration had to be modified to allow port 1433. Unfortunately this rule was setup incorrectly earlier.

    Thank you @Seeya Xi-MSFT for your input as well.

    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.