Hi have the same problem, but I found the solution by modifying the QProxy.aspx:
string user = GetUserName();
HttpResponse response = Context.Response;
string proxyUrl = GetProxyUrl(Request, user);
if (proxyUrl == string.Empty) return;
HttpWebRequest request = (HttpWebRequest)WebRequest.Create(proxyUrl);
request.Method = Context.Request.HttpMethod;
request.PreAuthenticate = true;
string password = ConfigurationManager.AppSettings["password"];
NetworkCredential networkCredential = new NetworkCredential(user, password);
// Associate the 'NetworkCredential' object with the 'WebRequest' object.
request.Credentials = networkCredential;
//request.UseDefaultCredentials = true;
//request.Credentials = CredentialCache.DefaultCredentials;
I found the cause of my problem when I was reading about the tool for qlikview and share point, webparts. When using workbench on a site published on a web server there are problems with windows authentication. The client enter the web site which in turn gets the objects from qlikview. But this causes multi hop authentication, client computer -> web server -> qlikview. Which windows doesn't allow. So the qlikview server can't authenticate you. You could try to use something other than windows authentication on the qlikview server, but I did not have the time to test this. I just used iframes and singleobject.html. Not as responsive but good enough. Hope you find the answer to your problem!