SQL Instance Firewall Issue

[bigdogchris]

I am running a named instance on SQL Server 2008 R2 Express and attempting to configure my Windows Firewall to be enabled on the server.

When attempting to connect to the database through the application, if the firewall is disabled I am able to connect to the server, with the firewall is enabled I am unable to connect to the server, so it is narrowed down to a firewall issue. When the firewall is enabled, the firewall log shows that it is dropping connections to my workstation on ports in the high 50,000 to low 60,000 range. I understand this is due to the named instance being handed off to dynamic ports after establishing the connection on port 1433 and 1434, correct?

To remedy this I have verified on my server that TCP port 1433 and UDP port 1434 are allowing inbound connections. I have also used the network configuration manager to change TCP/IP for the instance to a static port by removing the 0 from Dynamic and assigning a static port, I then add that static port to the firewall rule. The connections still drop as this did nothing for me, apparently I misunderstand this setting.

For testing purposes I created a firewall rule to allow all connections, specifying the source workstation IP. The connection succeeds, but that is not a solution as the workstations are numerous and are using dynamic IP configurations.

Also, the application requires Named Pipes to be enabled, which requires File Sharing open, but does it require it open on the workstation or just the server?

Thanks.

 

[renixinq]

First google result will get you going. http://msdn.microsoft.com/en-us/library/cc646023.aspx. Instead of doing it by port you can just grant access to inbound connections on the sqlservr.exe and call it good too. Don't overthink it too much it should be straight forward and fairly simple.

 

[bigdogchris]

First google result will get you going. http://msdn.microsoft.com/en-us/library/cc646023.aspx. Instead of doing it by port you can just grant access to inbound connections on the sqlservr.exe and call it good too. Don't overthink it too much it should be straight forward and fairly simple.

I saw that before posting but there is so much there I am unsure what needs to be actually opened, I don't want to open up everything.

Since posting this I have added 1433/34 in, and allowed sqlservr.exe for the instance through. Still waiting to check on it.