Hi all

I know there have been other posts regarding this issue and if I have understood things correctly this would appear to be a bug within the Proxy authentication routines within BOINC.

Symptoms are;

Downloads WU's no problem and crunches OK. When upload starts BOINC minimises itself to the system tray and then exits a few seconds later generating an error code. I'm running XP - dont know if this makes a difference.

I am currently attmepting the work around suggested in other threads using Python and APS. Hopefully that should work but my real question is will this bug be fixed and if so soon, later or sometime.

I believe that a bug of this type which effectivly renders any computer requiring a Proxy authentication useless to the project would be a very high priority.

Anybody know the answer or have any other work arounds for this bug

Regards

Neil

Hi

I’ve also had that problem and traced it down to the authentication. I think I have found a quite simple workaround.

I previously used the free Program “Proxomitron” (www.proxomitron.info) to apply proxy authentication to programs that do not have an authentication feature (or have some bug in it ;-).

The program is normally used as an Add Filter. It is installed on the local machine and can be configured to connect to a remote Proxy. It is possible to set a username and password sent to the remote Proxy. Clients (like a Browser or BOINC) use the Proxomitron as Proxy. If the program is set to “bypass” mode, it supplies a transparent internet connection but without an authentication needed.

The installation & configuration don't need much time and require no special user rights on the computer.

I have installed it and attached successfully to the project. Download and everything works fine for now. I’m waiting for the first WU to complete (not the fastest machine here...). If everything works fine, I’ll post an detailed description to solve the Problem (around Monday I think).

Hope it works,

Sven

Another solution is to use APS. Look at this thread:


http://setiweb.ssl.berkeley.edu/forum_thread.php?id=25

> Another solution is to use APS. Look at this thread:
>
>
> http://setiweb.ssl.berkeley.edu/forum_thread.php?id=25
>
>

I've been trying this today. I have downloaded and installed the APS and Python software and configured it however I still cant get things working. BOINC does not crash now when it attempts to upload however the client seems to be unable to locate the server.

Its driving me mad at the moment as I have quite a few units completed that I cant upload.

I think I will try Svens suggestion as well.

BOINC team if this is a bug please get it fixed!!!

Neil

I have now finished several work units and the connection works fine using the Proxomitron. I’ve posted a step-by-step instruction to install and configure the Proxomitron to use with BOINC.

http://www.osiris-network.de/seti/

Hope it works everywhere.

By the way:
I agree that this connection bug should be fixed as soon as possible. Many users could get frustrated and abandon the project. Some of the fastest computers are behind secured Proxies.

Sven

> I have now finished several work units and the connection works fine using the
> Proxomitron. I’ve posted a step-by-step instruction to install and configure
> the Proxomitron to use with BOINC.
>
> http://www.osiris-network.de/seti/


Sven

Thanks for that detailed work around. I have just implemented it on my system and all is now well with the world.

Many thanks

Neil