Multi node with shared persistence setup - problem accessing shared folder from rim nodes

[Dago]

Hi everybody,

I set up a multi node Qlik Sense cluster with one central node and two rim nodes: the particularity is that the central node is located in a back end secured network for secuirty policies concerns (data can not be stored on server accessible via https protocol) and the two rim nodes are located in a front end DMZ where I activated two balanced Proxy Services to enable https access to the Qlik Sense Hub.

The installation process was fine and I succeeded in importing my first dashboard and all required extensions accessing the QMC directly from the localhost in the Central Node remote desktop, but when I tried t access the dashboard from the hub https url I see the dashboard but I can not access all its content receiving the following error

In the shared folder located in the central node the app is present (I checked for the ID), but it seems that there is no network connectivity between the two rim nodes and the central node because I tried to access the shared folder from the Windows Explorer using the network sharing path \\server\sharedFolder and windows fails to open the folder.

After this introduction I explain my problem and I ask for a question.

The problem is that across the two different networks there is a firewall and the following ports (used by windows to share data across the network) 139, 445 (TCP protocol) and 137, 138 (UDP protocol) are closed. I asked to open the ports, but I received a KO from the security team because these ports are associated to NETBIOS and SMB unsecure (for my security team) protocols.

My question is "can I change the ports for network data sharing both in windows or in the qlik sense?" because my security team told me that using different ports they will have no problem to open them (I know it is a nonsense )

[Daniele_Purrone]

Hi! You might be able to find a way to change the ports, but that wouldn't be supported.
https://support-cdn.qlik.com/articles/000047415

I'm not even sure there is a way to change port 445 in Windows without disabling smb3 and using previous, more insecure, versions of the protocol.

[Daniele_Purrone]

What you can probably should consider doing, instead, is setting up a reverse proxy in the DMZ.
Here is an example, though things will need to be tailored around your environment

https://support-cdn.qlik.com/articles/000043332

You'll find other suggestions in the community:
https://community.qlik.com/t5/forums/searchpage/tab/message?advanced=false&allow_punctuation=false&f...