Knowledgebase:
SQL Server 2016 - Remote Client or SSMS Cannot Connect
Posted by Skip Munk on 30 October 2017 04:58 PM

Since the server is running on a remote VMWare ESXi instance, the subnets are completely different from what we might expect on physical topology. A standard “Physical Box” Win Firewall config might look something like this:

netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = localsubnet profile = DOMAIN

Change this to:

netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = any profile = DOMAIN

And everything should start working.

I pirated this solution from dbStackExchange.

(0 vote(s))
Helpful
Not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).