Have you verified the default Trex RFC in the ECP system?
Tx se38 > ESH_ADM_SET_TREX_DESTINATION
I assume this is valid as the rest of your indexes would break without it.
Perhaps a user filtered trace on ECP to see what the connector is attempting to access, as the system user ID may be having an auth issue?