How to Configure Windows Firewall to Allow BACnet Communications

If you are using Events2HVAC with the BACnet Device Interface driver or you are using the stand-alone BACnet Explorer tool for troubleshooting, you want to make sure your PC or server is not blocking BACnet traffic.  BACnet/IP communicates over UDP port 47808 (0xBAC0).  Windows firewall will block this traffic if it is enabled.

1.  Verify if the firewall is blocking the connection (Server 2008)

Turn off the firewall to verify if it is blocking remote BACnet traffic from other devices.

Open the firewall dialog, right-click to show properties.

Turn off the firewall and hit Apply.  Test your BACnet Explorer again (rescan devices) to see if other network devices show up.

If the connection was successful and you want the firewall enabled (recommended), you'll need to add a firewall rule on inbound connections.

2.  Allow Remote Events2HVAC Connection Rule in Windows Firewall (Server 2008)

Type: Inbound Rule
Name: BACnet (UDP Ports 47808)
Protocol: UDP
Port: 47808

(Note: default BACnet port is UDP 47808, but you may want to verify if this is the case for your network)

Open the Windows firewall dialog again, and add a new inbound rule.  Select port as the type.

Select UDP as the protocol and ports 47808 in this example.   Use your actual port numbers here.

Select Allow The Connection

Select the appropriate profile for your organization.


Provide a sufficiently detailed name and description, as below.

Using the steps at the beginning of this article, turn the firewall back on.

Test your BACnet Explorer again (rescan devices) to verify all remote devices are showing up.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.