FMC User Agent for AD - AD server status Unknown

[Looi Siew Key]

Hi All,

Currently we have an issue that FMC User Agent for AD that couldn't check "Real Time Status" and "Last Real Time status". But AD server still can poll to FMC, and on RDP server .167 FMC user agent can see all 3 AD server is actually in sync and poll time is correct.

Not sure why other 2 server FMC user agent shown server .167 is in unknown state, but other 2 AD server is showing good result.

* All 3 AD server poll with no issue, i believe it is comestic issue.

FMC User Agent version : v2.3 build 10

[yogdhanu]

Hello there,

It could be a communication issue or firewall on the .167 server which is blocking real-time comm from user agent.

You can export the logs from user agent after enabling the "debug" option and then search for error or exception in those to get more details.

Rate if helps.

Yogesh

[Looi Siew Key]

Hi,

We couldn't find particular AD server agent IP segment is block, the ACL rules is permit and we can see the traffic go through in FW logging. 

Based on debug FMC agent, we found error message below, not sure related to our issue currently;

10/17/2017 3:59:35 PM

error

[2317] - Unable to attach event listener to xxx.xxx.x.167. Check firewall settings on AD Server. The RPC server is unavailable

[yogdhanu]

Hello,

You can try to install the agent on the AD itself and use "localhost" as the AD server name/address. This would eliminate the communication issue.

Thanks

Yogesh

[sistematico]

Was this resolve?, I have the issue and im running version 6.2.2, also I have a tac case but they havent be able to figure it out yet.

[Looi Siew Key]

Hi Sistematico,

We don't have solution yet on this case. Even generated debug logs but still unable to check where is the issue comes from. 

We checked on firewall on every side which doesn't block any port for sync.

Please let us know if you tac engineer have solution on this. Thanks!