Skip to main content

How To Configure Antivirus Firewalls for a Network Environment

Configure SQL Server and your firewall (Windows Firewall, AVG, Kaspersky, McAfee, or Norton) so client computers can connect to your server computer on ports 1433 and 1434.

Written by Kate Biel

📝 Overview

When you use the software in a network environment, client computers need to connect to the SQL Server instance on your server computer, and firewalls can block that connection. This article walks you through configuring SQL Server, then adding the rules and exceptions your firewall needs to allow connections on ports 1433 and 1434.

These instructions cover Windows Firewall, AVG Internet Security, Kaspersky, McAfee, and Norton Security. They don't extend to any other antivirus firewalls that may also be installed on your workstations. For help with those, refer to vendor-specific support literature or a local computer technician.

💡 Where to complete each section: Configure SQL Server on the server computer only. Configure your firewall on all the computers in your network.

🗄️ Configure SQL Server

To connect client computers in a network environment, the SQL Server instance you'll be using needs to be configured to allow client computer connections.

  1. On the Server computer, navigate to SQL Server Configuration Manager. Click Windows Start > All Programs > Microsoft SQL Server 2012 > Configuration Tools > SQL Server Configuration Manager. If you can't find it under that path, open File Explorer, navigate to C:\Windows\SysWOW64, and click SQLServerManager.
    ​

  2. In the left pane, double-click SQL Server Network Configuration and click Protocols for CMJ.

  3. In the right pane, right-click TCP/IP and click Enable if it's not already enabled. You should get a warning window to restart SQL Server. Click OK. Right-click TCP/IP again and click Properties.

  4. In the TCP/IP Properties window, click the IP Addresses tab. Scroll to the bottom and, in the IP All section, delete whatever is in the TCP Dynamic Ports row and enter 1433 in the TCP Port row. Click Apply.

  5. You should get a warning to restart SQL Server. Click OK.
    ​

  6. Click OK to close the TCP/IP Properties window, then click SQL Server Services in the left pane.
    ​

  7. Right-click SQL Server (CMJ) and click Restart.

  8. Close SQL Server Configuration Manager. SQL Server is now configured to allow client connections to the server computer.

🛡️ Configure Your Firewall

To connect a client to a server in a network environment, your firewall will likely need added rules or exceptions. If you can't connect your client to the server with your firewall enabled, follow the steps for your firewall below on all the computers in your network.

🪟 Windows Firewall

Add inbound and outbound rules for ports 1433 and 1434, and enable the Echo Request rules.

  1. Go to Control Panel and click Windows Firewall. If Control Panel is set to Category view, click System and Security, then Windows Firewall.
    ​

  2. Verify that Windows Firewall is set to On (recommended). If it's not, click Turn Windows Firewall on or off in the left panel and set the radio buttons to Turn on Windows Firewall for both Home or work (private) and Public network settings. Click OK to accept the changes.
    ​

  3. Click Advanced Settings in the left panel, click Inbound Rules in the left pane, and then click New Rule in the Actions panel on the right.

  4. In the New Inbound Rule Wizard, click Port, then click Next.

  5. Click the TCP and Specific local ports radio buttons. Enter 1433, 1434 and click Next.

  6. Click Allow the connection, then click Next.

  7. Apply the rule to Domain, Private, and Public by checking all three boxes, then click Next.

  8. Name the rule SQL TCP (1433,1434) and click Finish.

  9. Click New Rule in the Actions panel again.
    ​

  10. This time, click the UDP and Specific local ports radio buttons. Enter 1433, 1434 again and click Next.

  11. Click Allow the connection, then click Next.

  12. Apply the rule to Domain, Private, and Public by checking all three boxes, then click Next.

  13. Name the rule SQL UDP (1433,1434) and click Finish.

  14. Scroll down the list of Inbound Rules until you find File and Printer Sharing (Echo Request - ICMPv4-In). There are multiple copies of this rule. If they don't already have a green circle with a check mark, right-click each rule individually and click Enable Rule.

  15. Click Outbound Rules in the left pane, then click New Rule in the Actions panel on the right.

  16. In the New Outbound Rule Wizard, click Port, then click Next.

  17. Click the TCP and Specific local ports radio buttons. Enter 1433, 1434 and click Next.

  18. Click Allow the connection, then click Next.

  19. Apply the rule to Domain, Private, and Public by checking all three boxes, then click Next.

  20. Name the rule SQL Server (TCP) and click Finish.

  21. Click New Rule in the Actions panel again.
    ​

  22. This time, click the UDP and Specific local ports radio buttons. Enter 1433, 1434 again and click Next.

  23. Click Allow the connection, then click Next.
    ​

  24. Apply the rule to Domain, Private, and Public by checking all three boxes, then click Next.

  25. Name the rule SQL UDP (1433,1434) and click Finish. All the Outbound Rules you need are now created.

  26. Scroll down the list of Outbound Rules until you find File and Printer Sharing (Echo Request - ICMPv4-Out). There are multiple copies of this rule. If they don't already have a green circle with a check mark, right-click each rule individually and click Enable Rule.

🦠 AVG Internet Security

Enable Windows file and printer sharing, remove two blocking packet rules, and add a packet rule for SQL Server.

  1. Right-click the AVG icon, typically located in the system tray in the bottom right of the screen, and click Open in the Internet Security section.
    ​

  2. Click Menu in the top right.

  3. Click Settings.
    ​

  4. Click Full Protection, then click Enhanced Firewall.

  5. Scroll down and click System rules.

  6. For Allow Windows File and Printer sharing, switch the status to Enabled.

  7. Scroll down and click OK.
    ​

  8. Click Packet rules.

  9. Click the Public Icmp Echo In Block rule once and click Remove at the bottom.

  10. Click the Public Tcp/Udp In Block rule once and click Remove at the bottom.

  11. Scroll to the bottom of the window and click Add.
    ​

  12. In the Name field, enter SQL Server (TCP and UDP).
    ​

  13. Set the Action to Allow.
    ​

  14. Set the Protocol to TCP/UDP.
    ​

  15. Set the Direction to In/Out.
    ​

  16. In the Local Ports field, enter 1433,1434.
    ​

  17. If the rule you added looks like the one below, click OK to save your changes.

  18. Click OK again. You can now close the AVG window.

🔒 Kaspersky

Edit three packet rules to allow SQL Server traffic. Kaspersky has a few different levels of protection, but the process should be similar across versions.

  1. Right-click the Kaspersky icon, typically located in the system tray in the bottom right of the screen, and click Kaspersky Security.
    ​

  2. Click the gear icon in the bottom left of the window.

  3. Click Protection, then click Firewall.

  4. Click Configure Packet Rules.
    ​

  5. Click Local Services (TCP) and click Edit.
    ​

  6. In the Action drop-down menu, make sure Allow is set.
    ​

  7. In the Local Ports field, enter 1433, 1434. Your settings should now match the image below. If they don't, adjust your settings to match.

  8. Click Save and close the window.
    ​

  9. Click Local Services (UDP) and click Edit.
    ​

  10. In the Action drop-down menu, make sure Allow is set.
    ​

  11. In the Local Ports field, enter 1433, 1434. Your settings should now match the image below. If they don't, adjust your settings to match.

  12. Click Save and close the window.
    ​

  13. Click Any Incoming ICMP and click Edit.
    ​

  14. Match the settings with the image below.

  15. Click Save and close the window.

🔐 McAfee

Allow ICMP ping requests and make sure the SQL Server port is enabled with both ports entered.

  1. Right-click the McAfee icon, typically located in the system tray in the bottom right of the screen, and click Open McAfee LiveSafe.
    ​

  2. Click Manage Security.
    ​

  3. Click View firewall and anti-spam settings.
    ​

  4. Click Firewall.
    ​

  5. Expand the Smart Advice and Advanced Settings section, enable Allow ICMP Ping requests, and click Apply.

  6. Scroll down until you find the Ports and System Services section and click it to expand.
    ​

  7. Within Ports and System Services, scroll down until you find Microsoft SQL Server (MSFT SQL) Port 1433. Make sure this item is enabled.

  8. Click Microsoft SQL Server (MSFT SQL) Port 1433 once and click Edit.
    ​

  9. Scroll down until you find Local TCP/IP Ports and Local UDP Ports. Make sure 1433, 1434 is entered in both fields.
    ​

  10. Click Save in the bottom right. You can then close the window.

🔏 Norton Security

Disable two default blocking rules and add a new traffic rule for SQL Server.

  1. Right-click the Norton Security icon, typically located in the system tray in the bottom right of the screen, and click Open Norton Security.
    ​

  2. Click Settings in the top right corner.

  3. Click Firewall.
    ​

  4. Click the Traffic Rules tab.
    ​

  5. Scroll down the list until you find Default Block Inbound and Outbound ICMP. Uncheck the box to disable the rule.

  6. Scroll down the list until you find Default Block All Inbound Windows Services (Public Networks). Uncheck the box to disable the rule.

  7. Click Add.
    ​

  8. In the new window, click Allow, then click Next.
    ​

  9. Click Connects to and from other Computers, then click Next.
    ​

  10. Click Any Computer, then click Next.
    ​

  11. Select TCP and UDP from the drop-down list. Then click The rule will apply only if it matches all of the ports listed below.
    ​

  12. Click Add.
    ​

  13. In the Specify ports window, click Known port from list for the Filter by option and Remote for the Locality option. Scroll down the list to find ports 1433 and 1434. Check both boxes and click OK.

  14. The window you have open should match the image below. If everything matches, click Next.

  15. Verify that Create a Security History log entry is unchecked and If Explicitly requested is enabled. Click Next.
    ​

  16. When asked what to call the rule, enter SQL Server (TCP and UDP). Click Next.
    ​

  17. Verify that the settings on screen match the image below. If they don't, go back and follow the previous steps for creating this rule. Once everything matches, click Finish.

  18. Click Apply to save all of these changes. You can then close all the Norton Security windows.

🧱 Other Firewalls

If you still can't connect with your firewall disabled and you're certain your network is functioning properly, you'll likely need to create exceptions in other antivirus or hardware firewalls installed on your workstations. Open the same ports, 1433 and 1434, on those firewalls. For help, refer to vendor-specific support literature or a local computer technician.

Related Articles
Did this answer your question?