Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

r3iuk
Contributor

Problem with remote user access and tunelling

We have a remote user, whom I believe is connecting onto our network using VPN. We are trying to set him up with access to QlikView. He has been able to get to the AccessPoint and install the IE-Plugin. When he tries to access a report he gets the following error:

qvp://SERVERNAME/Category/ReportName.qvw?iis_authenticate=<long hex number>&tunneler=http%3A//SERVERNAME/scripts/QVSTunnel.dll%3Fhost%3DSERVERNAME could not be opened

Am I right in thinking that QlikView is trying to use tunnelling, which it looks like we do not have installed? We are currently using the QlikView web server - am I also right in thinking that you need to use the IIS in order support tunnelling?

1 Solution

Accepted Solutions
Employee
Employee

Problem with remote user access and tunelling

No, the QlikView web server supports Tunnelling and it is enable by default. I might have to do with DNS. When I VPN into my companies network, I have to use the FQN of the server. So if I want to connect to a server name test, I have to use test.companyname.com

4 Replies
Not applicable

Problem with remote user access and tunelling

I'm currently facing the same issue. We are not using IIS.

Any suggestions on what to do?

Thanks!

r3iuk
Contributor

Problem with remote user access and tunelling

If I recall correctly, our problem was caused by name resolution. We put the SERVERNAME and the IP address into the host file on the remote client computers and they were then able to get at the QlikView documents OK.

Not applicable

Problem with remote user access and tunelling

Thanks!

Employee
Employee

Problem with remote user access and tunelling

No, the QlikView web server supports Tunnelling and it is enable by default. I might have to do with DNS. When I VPN into my companies network, I have to use the FQN of the server. So if I want to connect to a server name test, I have to use test.companyname.com