HUB is the web interface to administer, govern and mantain Qlik Sense. So the sentece "central node do not connect with the hub has no sense" I assume you talking about RIM node instead HUB. If your RIM node has Proxy and Scheduler basically has the same central node components (because scheduler requires Engine to run and both Scheduler and Engine require the Repository).
Did you go through the Node configuration after the re-installed the RIM node?
Thanks for replying back. I think I did not explain very clearly in the question. We have 1 central Node and 3 rim nodes. Out of 3 rim nodes, 1st Rim node is load balancing node of Central node(Engine, repository ) 2nd is a proxy node (Proxy, repository and Engine), 3rd Rim node is Scheduler( Repository, Scheduler and Engine Service). The proxy rim node is configured in such a way that, end users should be routed to either of the central node or RIM01 node to open the HUB and access the dashboards.We have a unique data link (similar to VIP address to access Access point in QlikView). The virtual proxy should send users to either central or RIM01. The issue was when users use the data link they get the HUB NOT FOUND error. But if they use individual Central Node server name or RIM01 Serer name, they were able to access the HUB.
PS: This issue was resolved. After re configuring to QMC,we faced the above issue. What really happened was The sync took 8 hours, to finally get this updated in Central repository.