Sql server 2008 firewall setup

STEP 5: The next step is misleading. STEP 6: Another rule check. Click Next. You need to select new installation , NOT add features. I know totally weird. Improve this question. Add a comment. Active Oldest Votes. Improve this answer.

Wayne Evans Wayne Evans 11 11 bronze badges. I've re-read your message again. It should just be UDP that's causing the issue. GL anyhow, just documenting what worked for me. Oleg Dok Oleg Dok But no result. I had exactly the same problem. Open "Windows Firewall with Advanced Security". On the actions menu on the right click "New Rule". Select Specific local ports , and then type the port number of the instance of the Database Engine, such as for the default instance.

Select Next. In the Action dialog box, select Allow the connection , and then select Next. In the Profile dialog box, select any profiles that describe the computer connection environment when you want to connect to the Database Engine, and then select Next.

In the Name dialog box, type a name and description for this rule, and then select Finish. In the Rule Type dialog box, select Program , and then select Next. In the Program dialog box, select This program path. Select Browse , and navigate to the instance of SQL Server that you want to access through the firewall, and then select Open.

Skip to main content. This browser is no longer supported. The content you requested has been removed. Ask a question. Quick access. Search related threads. Remove From My Forums.

Answered by:. Archived Forums. SQL Server Setup. Sign in to vote. I followed the instructions and added the following ports as Exceptions in the Windows Firewall configuration: TCP: 80, , , , , , , UDP: , , I am still getting the warning. Please advise.

Friday, August 8, PM.