You can find this in the Server Ref. Manual
QVP: 4747; QVP (tunneling): 4774; Broadcast: 14747; SNMP: 161
QDS, QMS, QVWS, QlikView Desktop/Internet Explorer plugin/OCX
I think 4747 is enaugh, how the tunnelprotocol differ from qvp i dont know. If you get no connection to the qvs it try to use the http tunnel from the webserver to reach the server endpoint. The time to connect over http is longer because it falls back after the server connection timed out. Ping and bandwich woud be better with direct qvp but this matters only if the ressources at the limit.
Thanks - I did read that, but it is still not clear to me, if 4774 must be opened even if 4747 already is opened.
As I understand the 4774 tunneling bit in the text, the PlugIn is not using 4774 unless it has to tunnel the session. And it only needs to tunnel the session when 4747 is not available. And therefor I guess that the answer is: that port 4774 is not demanded to be opened for the setup to work for a Plugin user if 4747 is opened.
So the question is: Is that correct?
If all QlikView services are in the same computer, we only need to open outbound and inbound ports 4747 for Desktop licenses and Plugin, and port 80 for Ajax connections.
If not, this is the relation of QlikView Services and ports:
QlikView Distribucion Service
QlikView Web Server
QlikView Management Service
QlikView Directory Service Connector