3. In the details panel on the right side, right click TCP/IP and click on Enable. This will issue a warning that the changes will only come into effect once the database engine service is restarted. Click OK:

4. Follow the same steps to enable Named Pipes Protocol This will issue a warning that the changes will only come into effect once the database engine service is restarted:

5. On the Surface Area Configuration for Services and page, expand MSSQLSERVER, expand Database Engine Node and click services. On the right panel the details related to MSSQLSERVER services will be shown. click Stop and wait until the MSSQLSERVER service stops, and then click Start to restart the MSSQLSERVER service to bring change into effect.

Conclusion
Configuring the Windows Firewall Exception for the SQL Server Database Engine will allow users to connect to SQL Server Instances when the Windows Firewall is enabled to secure the SQL Server. Once the exception is created then the Database Administrators can avoid database connectivity issues on SQL Server Developer and SQL Express Editions by proactively enabling the SQL Server Remote Connections, so that SQL Server Users who wanted to connect remotely can connect without any issues.