This solution applies to the Barracuda Web Filter when using the DC Agent.
When the DC agent fails to connect to the Barracuda Web Filter, it is likely that port 5049 access is blocked by Windows Firewall. Windows Firewall does not allow port 5049 access by default.
To allow connections on port 5049 for the DC agent, you need to create a new policy for the DC agent program in the Windows Firewall ACL.
To allow port 5049 in Windows Firewall, perform the following steps:
- Open Windows Firewall by clicking Start button > Control Panel > Security > Windows Firewall
- In the left pane, click Allow a program or feature through Windows Firewall.
- Click on add program and browse to the DC agent executable, then click Add when finished
- Check the range to allow the connection through Domain/Home or Private/Public
- Windows Server 2003 will allow all connections by default if the Windows Firewall is turned off.
- Windows Server 2008 will deny all connections by default if the Windows Firewall is turned off EXCEPT for connections explicitly allowed via Windows Firewall ACL.
Depending on the configuration, the above procedure may not be enough to open the port on Windows Server 2008. If this is the case, try the following steps:
- Open the Windows Firewall settings by clicking Start button > Control Panel > Windows Firewall.
- In the left pane, click Advanced Settings.
- In the left pane, click Inbound Rules.
- In the right pane, under Actions, click New Rule.
- Under Rule Type, click Port, then Next.
- Under "Does this rule apply to TCP or UDP?", select TCP.
- Under "Does this rule apply to all local ports or specific local ports?", click "specific local ports:" and enter 5049. Click Next.
- Under "What action should be taken?", make sure this is set to Allow the connection. Click Next.
- Under "When does this rule apply?", leave all options checked, and click Next.
- Finally, name the rule and click Finish.