Distributed Engine on Linux showing disconnected on FME FLOW

It’s not a situation I’m particularly familiar with, but my first thought would be firewalls and networking issues.

I’d also ask the question of is a remote engine better in this scenario than a distributed engine? 

They’re both similar, but interface back to the core in different ways. There’s some additional detail here:

A Guide to Choosing Your FME Flow Deployment Architecture – FME Support Center

I checked FME Core can communicate with distributed FME Engine. From FME Engine I can able to ping FME CORE. 

This is what is looks like now
 

Engine is registered with core but it is “Disconnected”

I wouldn’t trust pinging the machine at that uses a seperate protocol (IMCP) to what FME uses (TCP).

It’s better to use the following in powershell (if windows)

Test-NetConnection <ip> -Port <port>

or (in linux)

nc -vz <ip> <port>

With that being said, because the core can see it, it suggests that (some of) the ports are open. I’d suggest checking that all ports listed here (FME Flow Ports) are open between both machines. Note that a port range is also required (specified in fmeFlowConfig)

Thank you for response. I found the cause. My FME Linux distribution has firewall active and it was blocking incoming traffic.