Hi Johnlod,

Yes, reads like you got another classic. Probably your security software, most probably a software firewall did not like the RPC comms over localhost (127.0.0.1) port 31416. Fought long battles, set permission and anytime a new science version comes along, have to grant it access too. In the end permitted also port range 1038-5000 as localhost also uses a random port.

Anyway, if the BOINCmgr is unresponsive, but the WCG science is still running up CPU time 2 things can be done to alleviate:

1. Close the firewall. Usually the BOINCmgr re-establishes contact.

2. Terminate BOINCmgr.exe and restart and it will should make contact again with the Daemon and the Science. In the Tasks tab, the job should show progressing time as if nothing ever happened.

Try that and see what happens.

In the "Start Here" forum there is a post of all the BOINC and WCG client processes, "Agents, Projects Versions and Processes", that one time or the other have walked into security walls. Exceptions for those should do away with the problems.

cheers

Added: Avoid to kill BOINC.exe or the WCGxxxxxxxxxxxxx process. Often it damages the job beyond repair or causes it to restart at zero percent.

Great,

There was a disk crash on a server this morning and suspension of some processes there that may have had baring. There is an odd bug in the network side of things that somehow effects local comms as well. They are working in the present alpha series of development to get this bug resolved.

cheers