Questions and Answers :
Windows :
Had to do a system restore and have a problem
Message board moderation
Author | Message |
---|---|
lainofthenet Send message Joined: 28 Nov 02 Posts: 8 Credit: 1,748,517 RAC: 0 |
I had a bit of a bug which was demanding money for a problem on the computer that did not exist. I have since deleted it and since the virus was nasty I had to do a system restore. Before I did that I could tell that Boinc was having problems and literally downloading and uploading corrupted files at an incredible rate. I suspended its' operation and did a reset of the project since all the files were now reading as corrupted. I had to uninstall Boinc and re-install it. I am now getting a message saying it is communicating with the client. It has been doing that for hours now. I cannot do anything with the manager without that message coming up. I have re-installed Boinc again with the same result. Any advice? |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Make sure BOINC is allowed to pass through your firewall again. Copying an old post of mine: Normally this happens automatically, but sometimes you have to help by hand. And from another post of mine: Please check in Windows Firewall, Exceptions, if boinc.exe and boincmgr.exe are showing there. If they aren't, add them |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
Unfortunately, uninstalling BOINC does NOT delete all of the executables and data files that have been downloaded, but the reset should have taken care of that. The BOINC Manager (BOINCMgr.exe) not being able to communicate with the BOINC daemon (BOINC.exe) is caused by an inability to use http port 31416 on the local host. This can be caused either by a firewall setting being incorrect, or by more malware that is using port 31416 for something. Check to make certain that BOINC.exe is allowed to act as a server on port 31416 and that BOINCMgr.exe (and BOINCcmd.exe) are allowed out on port 31416. This is done for the local host only for local control or the LAN for remote control from other computers on the LAN. If BOINC looks like it should be allowed through, you may have more viruses on your computer (possibly a root kit that needs to be removed by MalwareBytes). BOINC WIKI |
lainofthenet Send message Joined: 28 Nov 02 Posts: 8 Credit: 1,748,517 RAC: 0 |
Thank you for the help! Ran some more scans on the system and while I did not anymore virus I did find what was blocking the communication. I am (rather the computer is) happily crunching away again. Part of the problem is there are so many programs that seem to be all to willing to assist a user (for our own protection ...lol) that it all gets out of hand at times. I am once again in charge of the machine ...or am I? |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.