Thanks for the reply. I'm using ISA 2000 (so its a little older than the article) however the problem is simply that BOINC doesn't do NTLM authentication, and I have ISA configured to demand NTLM authentication for outbound access. To get around this problem, I'm using SOCKSPuppet SOCKS5 proxy on a different server simply for the BOINC clients to connect to and get through the firewall, and it works perfectly fine in 5.8.16. It does not work at all if I upgrade any of these machines from 5.8.16 to any 5.10.x series builds. Reverting back to 5.8.16 and communications immediately begin to work once more.

Following the mailing list today it seems they have a more pressing issue to resolve (which I myself have not experienced).

The setup is actually more simple than it sounds. We've got an ISA Server 2000 sitting up front between the network and the internet, all traffic must pass through it. All workstations are so called "web proxy" clients, their HTTP/HTTPS traffic must pass through the web proxy service of the ISA Server to access the internet. Since we use Internet Explorer exclusively, and since this is an Active Directory domain, it all works seemlessly, and we have site/content/access rules setup based on user ID/groups, and since the web proxy service demands NTLM authentication and IE sends it transparently, all is bliss. For our servers, they are what is referred to as Secure NAT clients, we specify the ISA Server IP as the default gateway, and traffic flows between the two without authentication needed, the only thing that is required is that the ports/protocols are allowed on the ISA server. We have several server programs that utilize this just fine (POS-Partner for credit card processing, BlackBerry Enterprise Server, and several others).

Enter BOINC. It couldn't do NTLM (thanks for the explanation on that, btw). Following a tip on some other forum I found searching Google, I downloaded SOCKSPuppet and installed it on one of the servers. Loaded up BOINC, pointed it to that server as SOCKS proxy, and bingo, I was in business. It isn't really a double proxy per se because the server SOCKSPuppet resides on is not going through the web proxy service, but directly throgh the firewall. It appears to me that something must have been changed with the libCurl they use in 5.10 (newer version?), but using a packet capture program to see what exactly BOINC is doing might be quite useful, and I will try that as soon as I can. According to what I can see on the SOCKSPuppet side, BOINC never makes an attempt to connect with 5.10.

Hi Sekerob

Does WCG recommend switching back to 5.8.16, I switched to 5.10.7 about 2 days ago.
12 returns - 3665 points with No problems at all, currently 2 work units going 4 scheduled.
In fact I like the new updated 5.10.7

dseto

Thanks for the reply Sekerob.
I will stick with 5.10.7 until I get any problems.
Do you know if there is any testing on actual different computer setups, for example I have NO problems but my setup is very Basic - one computer no network to speak off.

dseto

I've been using the 5.10.x builds for the x64 support (running Vista x64 here) and because they seem to work better with Vista. I haven't had any of the troubles that seem to be aflicting a lot of people on the Boinc Alpha list (thankfully), its just that it appears SOCKS communication is broken in the 5.10 releases and I can't use it at work on the corporate network. However after seeing some of the issues 5.10 is having, I'm in no rush to change to it anyway on the corp machines. Will be waiting this out for some much more extensive testing first.