Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

QV11 ports need to open in firewall

Hello,

I plan to install QV11 server. The firewall for qlikview server was enabled.

May I know list of ports I need to open in firewall?

Like

Acess Point - 80

Management console - 4780

ODBC ?

Any other ports?

Thanks.

5 Replies
disqr_rm
Partner - Specialist III
Partner - Specialist III

Hope this helps you.

NameProtocolPort
QV ServerTCP4747
QVS Server  TunnelTCP4774
AccespointTCP80
AccespointTCP443
QMC / QEMCTCP4780
Comand Center  *TCP4710
Distribution  ServiceTCP4720
Directory  Service ConnectorTCP4730
WebServerTCP4750
Remote QMSTCP4799
Qvs.exeUDP 14747
Comand Center  *UDP4711
Management  ServiceUDP4781
QlikView  ServerUDP4748
Distribution  ServiceUDP4721
DirectoryServiceConnectorUDP4731
Not applicable
Author

Hi,

Recently we have upgraded qv11 with IIS not webserver and facing qvs tunnel error for some of  the users.

We have configured qvstunnel.dll as per server reference manual but facing issue.

I have checked one thing that firewall QVS Server Tunnel 4774 is not opened any user system (checked with telnet qvserver 4774 in all user system) but it opened 80 and 4747.

My question is that QVS Server Tunnel 4774 is not opened then everyuser has to face this tunnelling issue why it is happnenig for 2 users only.

So if I will open the firewall the error will not come or need to do anyother thing.

Env- IE7 and qlikview server 11 SR1.

I will appreciate your advise.

Thanks in advance

Arunesh

Bill_Britt
Former Employee
Former Employee

Hi Arunesh,

Port 4774 is used by the Tunnel.dll local on the machine and I don't think you will be able to telnet to it. So, if you are using tunneling the only port you need open in the fire wall is 80.

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.
maksim_senin
Partner - Creator III
Partner - Creator III

Hi,

In my case it happened due to firewall on server side, the issue gone once I added exclusion for inbound port 4747.

Best regards,

Maxim

Not applicable
Author

was this the issue you were facing? getting message the connection was refused