Some times the users are not able to access the QlikView document in the IE via the AccessPoint through wireless connectivity. When the users are accessing the QlikView document through the laptop,the qlikview is prompting for the "Connect to the server"
When the user clicks on the connect button, they are getting the following error:
Connected server OK, negotiations timed out Switching to HTTP tunneling Connected to server OK, No reply received.
We have trid to decrease the accesspoint timeout settings. But nothing is working.
The users who are connected to the cable are able to access the QlikView document.
Any valuable suggestions on this. Iam using QlikView 8.5 on windows 2003 64 Bit.
The qlikview service is running under the publisher execution Service account.
is the QV server using the same domain of the user;s network?
we had the same problem of latency and was due to this cause. My QV server has his own domain and is different from our office domain but....i created the same USERID for both domains and this was causing the latency.
Hi, have you been able to solve this issue? Experiencing something similar... some users using the IE plugin get a connect to server window and after that the message connected to server ok, negotiations timed out.
jgeorge wrote: is the 4747 port opened on both client and server side? if it is not the case the first connection will fail and automatically switch to tunneling, which will also fail if it is not properly configured in the QlikView server<div></div>
Unfortunately, tunneling will usually fail even if it is configured correctly - I've yet to get it working properly from outside of my organizational LAN.
I just want share that copying the file Authenticate.aspx from C:\Program Files\QlikView\Server\QlikViewClients\QlikViewAjax to C:\Program Files\QlikView\Server\QlikViewClients\QlikViewPlugin did fix my issue.
I'm running QlikView 10 and I have all my server setup in my North America domain, which users can access and lease a license without an issue. However, the users from the Europe domain experienced the issue from the original post.