Assistance Required for BigFix Endpoint Reflection Issue

1

Hi Team,

We need to add the BigFix Root Server hostname and IP address to the hosts file on every endpoint system for proper reflection in the BigFix Console.

So far, we have completed the following checks:

  • Verified that port 52311 is open.
  • Successfully performed a telnet test on port 52311 from the affected system.
  • Verified NSLookup, and the hostname is resolving correctly.

Despite the above validations, the endpoint is still not reflecting in the BigFix Console.

Could anyone please assist in troubleshooting this issue or suggest additional checks that need to be performed?

2

did you checked bigfix agent log from any client. it will be helpful if you can share logs by hiding sensitive data

3

I would not recommend (even not recommend by HCL) this approach unless you're working in a very small lab or test environment. In a production environment, clients should never communicate directly with the Root Server as part of normal operations.

Network configuration requirements

The recommended communication path is always:

Root Server ← Top-Level Relay ← Site/Regional Relay ← Clients

Clients should report to their assigned relay, and relays are responsible for forwarding reports upstream to the Root Server.

Since you've already confirmed:

  • Port 52311 is reachable.

  • DNS resolution is working correctly.

  • Network connectivity appears to be fine.

I would check the following:

  1. Review the BES Client logs on the affected endpoint and look for the most recent Report posted successfully entry.

    • If you do not see this message, is it able to connect the desired root/relay server (Relay Selected), any error msg?

    • Validate client is reporting to correct BigFix infra, check if it does have correct masthead.

    • If you do see it, then the client has successfully handed the report to its parent relay.

  2. Verify which relay the client is reporting to (Just in case if you any relay in between).

    • Ensure the client is assigned to the expected relay.

    • Check the relay logs to ensure client reports are being forwarded successfully.

    • Check the relay's FillDB

    • Ensure no antivirus, endpoint protection blocking report forwarding.

    • Confirm the relay is healthy and communicating with its upstream relay or Root Server.

  3. If the client reports directly to the Root Server (which is generally not recommended), then investigate the Root Server processing pipeline:

    • Check the FillDB service status.

    • Review the FillDB logs for errors.

Without reviewing the BES Client log and identifying where the reporting chain breaks (Client → Relay → Root → FillDB → Database → Console), it's difficult to determine the exact cause.

Note: In some cases, even though the client log shows "Report posted successfully", the report may later be discarded by FillDB. If that appears to be the case, I recommend opening a support case with HCL.

1 Like