Configuring Bitdefender Firewall for ScreenBeam Conference and Miracast Connectivity

This article is applicable to the ScreenBeam 1100P product.

Organizations using ScreenBeam Conference with Bitdefender GravityZone may need to adjust firewall settings to ensure reliable Miracast connectivity, wireless conferencing, and communication between client devices and ScreenBeam receivers.

This guide walks through the recommended Bitdefender firewall configuration settings required to support ScreenBeam Conference deployments.

Why These Firewall Changes Are Needed

ScreenBeam Conference leverages Miracast and wireless conferencing technologies that rely on specific local network communication paths and TCP ports. In environments protected by Bitdefender GravityZone, firewall restrictions may block these connections unless appropriate exceptions and rules are configured.

The recommended configuration accomplishes the following:

• Allows Miracast peer-to-peer (P2P) communication
• Trusts the ScreenBeam Miracast subnet
• Opens required ScreenBeam Conference TCP ports
• Ensures localhost communication is permitted for ScreenBeam client services
• Prioritizes ScreenBeam rules above default firewall policies

Create a Trusted Network for Miracast Connections

Begin by creating a trusted network profile within Bitdefender GravityZone.

Step 1 – Access Firewall Settings

1. Log in to Bitdefender GravityZone
2. Navigate to Policies
3. Select the policy currently applied to your devices
4. Go to Firewall → Settings

Step 2 – Add a Network Rule

Create a new network rule with the following settings:

The 192.168.16.0/24 subnet is the default subnet used for ScreenBeam Miracast P2P connections. Trusted networks bypass the Bitdefender firewall, helping ensure reliable wireless display operation.

After entering the settings:

1. Click the + symbol to add the rule
2. Click Save

Add Firewall Rules for ScreenBeam Conference

Next, create firewall rules to allow the required ScreenBeam Conference communication ports.

Step 1 – Navigate to Firewall Rules

1. Go to Policies → Firewall → Rules
2. Click + Add to create a new firewall rule

Create a Localhost Rule

ScreenBeam Conference clients require localhost communication access.

Configure the following rule:

This rule allows local client communication necessary for ScreenBeam Conference functionality.

After configuring the rule:

1. Click Save

Create a Rule for ScreenBeam Conference Ports

Create another firewall rule to allow ScreenBeam Conference network traffic.

Use the following settings:

These ports are required for ScreenBeam Conference communication between the client device and the ScreenBeam receiver.

After configuring the rule:

1. Click Save

Prioritize the ScreenBeam Rules

Once both rules are created:

1. Move the ScreenBeam-related rules to the top of the firewall rule list
2. Position them above the default Bitdefender firewall rules
3. Click Save to apply the changes

Prioritizing these rules ensures ScreenBeam traffic is processed before more restrictive default firewall policies.

Best Practices and Additional Notes

When deploying ScreenBeam Conference in enterprise or education environments, consider the following recommendations:

• Ensure client devices can communicate with the ScreenBeam receiver over the local network
• Avoid blocking local peer-to-peer communication required for Miracast
• Verify endpoint security policies do not override local firewall exceptions
• Test ScreenBeam Conference functionality after policy deployment
• If issues persist, temporarily disable the Bitdefender firewall for troubleshooting validation

For large-scale deployments, administrators may also consider deploying these policies through centralized Bitdefender policy assignments.