Unfortunately not, even http access via 8080 requires a session password and the corporate policy won't allow any exceptions.

I'm probably out of my depth, but if you access to the router or gateway you might be able to remap boinc ports to ones not blocked by the firewall. The firewall would see traffic on unblocked ports, but the packets would be remapped to boinc ports on the router. Don't know if communications coming in would be covered by the change or if you'd have to remap those too.

Most projects use http(post 80), but WCG is different since it uses https(port 443) as well.

So if you can not communicate with WCG using port 80 and port 443, likely you are out of luck. BOINC is not designed to pass a WU between systems.

Sincerely doubt it works, but port 443(https) is a must for outward traffic, therefore if you are able to put https over port 80, i saw the functionality in WinXPpro, you might get it to work. Not sure if WCG expects the handshake to forcefully come from a port 443 client.

It's been commented before on properly configured firewalls. Why is 443 outward blocked? It's the common Secure port for save transactions. I could bank in the office and up/download. But, we have to respect the IT meister and the corp.policies.... if they don't want that i/o it wont go. Not sure if they'd be so happy about AC@H jobs of 77mb in and 13mb up per pop to the outside world. 10 machines would be material if run 24/7. Conspiring here to work on re-routing past/thru the firewall throws up ethics questions!

A solution is, quite laborious, to set up a 10 sneakernet instalsl on 1 gateway machine for all the machines with a separate, call them BOINCA, BOINCB etc. Copy the whole install to a jump drive and walk to the machine designated to have BOINA, BOINCB etc. Copy it onto the cruncher with BOINC in off-line mode and when done, use the jump drive to carry it back to your gateway.