Any update on the Proxy issue/407 errors as of yet?

[Honsy]

I've used the v5 clients fine for more than 3 years in my business environment, but running the new WinSMP v6 client just gives me "Got status 407" which seems to indicate a proxy error. I've searched the forums and found that similar issues had occurred to those on the GPU2 beta, but they were seeing their proxy data disappear from their config file. I've checked my config file and all the information is there and appears to be correct. What would be different from the v5 to the v6 clients that would cause proxy authentication issues like this? Any ideas are welcome.

[hmmblah]

I am having the same issue. I've configured, double, triple, quad checked everything. My proxy user name and password are correct. I still get status 407 returned in the client.

I checked my squid cache logs and it looks like the SMP client isn't even passing the user name information to squid. It's trying to authenticate without a user name and password even though it is set to do it.

I copied a config from another computer running an older version of the client, but the same error exists.

It looks like proxy auth is broke on this release of the client.

[7im]

I've logged the issue with the developers.

[Xilikon]

Did you try to delete the config file and redo it manually with the new client ?

[7im]

Good idea! I had a minor problem carry over in my SMP client when upgraded from v5.91 to v6.22. Renaming the client.cfg file to force the client to make a new one avoided the minor problem that I found.

[Honsy]

Did you try to delete the config file and redo it manually with the new client ?

This is on a brand new image, so there is no previous setup to interfere with the new v6 install.

[hmmblah]

Did you try to delete the config file and redo it manually with the new client ?

This is on a brand new image, so there is no previous setup to interfere with the new v6 install.

Same here. I did try recreating the config multiple times though.

[Honsy]

Did you try to delete the config file and redo it manually with the new client ?

This is on a brand new image, so there is no previous setup to interfere with the new v6 install.

Same here. I did try recreating the config multiple times though.

As did I. The only thing I noticed that was different between the config files is the proxy password. In v5, its what appears to be, random characters. In v6, it's the password, unmodified.

[hmmblah]

Yeah, I noticed that too. Even if it is just a proxy password, I don't like passwords stored clear text in a text file.

[7im]

Yeah, I noticed that too. Even if it is just a proxy password, I don't like passwords stored clear text in a text file.

I added that to the developers log as well.

[hmmblah]

Thanks, it's greatly appreciated.

[BrokenWolf]

I am getting the 407 error on the SMP 6.22. Any chance of putting this in the known issues listing?

Thanks,

BrokenWolf

[7im]

Good idea. As I mentioned above, Pande Group has visibility of the problem. They are looking at options and work arounds, or so I hear...

[AmB]

How's the developer group going with this bug?
Got lots of idle boxes here because of this issue

[VijayPande]

Thanks for the report. For now, could you switch back to the 5.92 client while we look at this one? Right now, we have clients testing our fixes for the EUE and ACK issues. We'll start looking into this one too.