Windows Firewall Rules For Sql Management Studio

The purpose of this post is to find out why I cannot log into a remote SQL Server instance from a Windows 10 system. My Windows 10 system connects just fine, and has fire wall rule

Solution 1:

First the easy part: the client doesn't needs any inbound connection, as it doesn't receive any connection (it makes them), so you can safely block everything inboud.

Now for the outgoing ones. The server itself only needs TCP access in the port it's listening to, so if you have a fixed port, you just open it (by default 1433 for a default instance) and you're good to go.

But since you're using dynamic ports, setup is a bit harder. Basically, "dynamic port" means that the server listen on a "random" port each time it starts, and the SQL Browser service tells clients on which port is listening each instance (this is the default setup for named instances).

So for this, first you need to allow outgoing connections to the SQL Browser, which listens on UDP 1434. Now you'll also need the normal server connection as before, which is still at TCP, but this time the port is unknown (since it's random). So, at most the most restrictive rule you can make is to allow all TCP ports, maybe also filtered by client program (ssms.exe for example) or by any other parameter that your firewall supports.

Solution 2:

i think you have to create an inbound rule in the SQL Server permiting port 1433/ 1433 . The dynamic port its not important for this configuration.