FIREWALL Using Eve On A Network

There are 2 steps you need to perform on the computer where the database is located to allow other computers to use the EVE server.

Step 1 - SQL Server Configuration Manager

Open SQL Server Configuration Manager. You can do this as follows:

Windows 10:  type SQLServerManager12.msc into your Windows Search box.  If no results are found, either SQL Server is not installed or you have an earlier version so type SQLServerManager10.msc instead.  Click SQL Server Configuration Manager in the results list.  

Windows 8 and 8.1 you can do this by typing SQL Server Config on the Start screen and then clicking on SQL Server Configuration Manager in the results list.

Earlier versions of Windows:  click Start | All Programs | Microsoft SQL Server 2008 R2 | Configuration Tools | SQL Server Configuration Manager

Expand the SQL Server Network Configuration (3bit) section and click on Protocols for EVE
Right click on TCP/IP and click Properties
Click on the IP Addresses tab and scroll down the list to the bottom
In the IPAll section, remove the value from TCP Dynamic Port and enter 1433 in the TCP Port
Click OK



Click on the SQL Server Services entry in the list on the left.  Right click on SQL Server (EVE) and then Restart Restart Services


Step 2 - Configure Firewall

Two Inbound rules need to be configured in the Firewall on the server computer:
1/ Port 1433  . Type = TCP
2/ Port 1434.  Type = UDP
Here are instructions on how to do that in Windows Firewall:
In Windows Control Panel open Windows Firewall.
Click Advanced Settings - see screenshot below.


Select Inbound Rules and click New Rule

 Firewall 2

 Select "Port"

 Firewall 3

 Choose UDP and enter 1434 for the Port number

 Firewall 4

 Click Allow the Connection

 Firewall 5

 Choose which level of access you want to open by putting ticks in the appropriate boxes.

 Firewall 6

Call the new rule "SQL Server Browser"

 Firewall 7

 Then create a 2nd rule in the same way called "SQL Server" for Port 1433 and choose the TCP option rather than UDP.

Click here for more detailed information from Microsoft