Proxy error message "401 unauthorized"

This is a request from the german forum. Internet related things seem to fail, as the update check. The error message "402 unauthorized" appears.

It was suspected, that maybe the auth header is not sent, for some reason. What could be the reason?

The version is 9.1.3.0.3449.x86.

Have they configured Opus to use their HTTP proxy? I'm not sure if Opus will pick up the IE settings automatically; they may have to be put into Opus manually.

In the English version it's done in Preferences - Miscellaneous - Internet Settings.

I will forward that tip, but here it obviously works (i use Opera & thus the settings in my IE must be ok, which would be the default settings, because i have no problems here sending mails or using FTP). Maybe they use some special settings in their firm.

The settings are ok, also in the preferences (HTTP proxy), but the problem still persists. Any more ideas?

Don't know what else to try, sorry. I don't know much about web proxies or how Opus uses them, though.

They might need to contact GPSoft to see if they can help, but I can see it being difficult without the particular (type of) proxy to test against.

They could test their suspicion about the auth header not being sent by seeing what Opus sends & gets back using Wireshark or a similar tool, then compare that to an app which can access the proxy okay and see if any of the packets are missing or different. Wireshark can be hard to understand if you don't know how to use it, though.

(I've used it once myself with the help of someone who is an expert on network stuff and Wireshark is a brilliant tool but I probably would've been lost without my friend's guidance on how to use it and what to look for.)

I think Microsoft brought out their own tool that's similar to Wireshark and was also meant to be good. Can't remember the name of it, though, and I don't know which is better. Both are free, FWIW.

Hmm, do they know the type of proxy involved? If it's a software proxy maybe myself or GPSoftware could set up a local instance and try to repro the problem. (More difficult if it's a hardware proxy!) I'd be happy to help if I can as I remember how annoying it was when web-connected apps didn't always function when my workstation was behind a proxy server.