I had to running for more than a day. This morning I noticed the PC had re-started (at least I think it did, Bionic was not running). So I go and start it back up and it gives me the \"bionic cant connect to the client\" error again. This time I can seem to get around it. The last time all I had to do was add the manager to the \"windows firewall allowed list\" then it worked. Now its not. Probably the only thing left is to un-install it and start over.

I\'ve seen the \"cannot connect\" problem twice now, although I am running a spinup model and not the normal CPDN application. I _think_ it might be related to Windows Defender but I haven\'t chased it at all.

It\'s probably not worth it for you, with one days running it would be easier to completely restart, but the following has allowed me to recover my spinup model (93% completed after 2550 hours) twice now.

Stop BOINC.
Copy the complete BOINC folder to a safe location.
Uninstall BOINC.
Delete the BOINC folder.
Reboot the machine (this appears to be an important step).
Install BOINC and allow it to start - but don\'t allow it to attach to a project.
Close BOINC.
Delete _all_ the contents of the BOINC folder and copy back all of the contents of the saved folder.
Restart BOINC.

It should now connect and restart your original project from where it stopped.

Note that this is just one way I have got around the \"cannot connect\" problem. There may be an easier technique - but with 2550 hours at stake I didn\'t want to play around too much!

Ian

---

This happened to my spinup in the early hours of this morning. I got woken up by a BOINC sound, (appropriate!), and found the \'Can\'t connect ...\'
This is the 3rd time in 3.5 months, and my cure is a simple reboot. It may not work for everyone.

I dont know how long I will be doing it anyway (IF I can get it to work with some stability). I have been running Seti@Home the past day just to get a feel for my new system. I just put this new Asus mobo and AMD 64bit 3200+ CPU in. Just for some scale reference, when i started doing SAH back in 1999 (I think) it took my PC then about 30-40 DAYS to do one data unit to 100%. This rig takes about 2.5-3 HRS

One issue the app may be having is my RAM. I only have 768MB of RAM and one stick is PC2100, the other is PC2700. I guess I should be happy the machine boots at all :D

I did not upgrade my memory when I made this \"new\" system. Just swapped out the motherboard and CPU. Being on a budget sucks :)

---

This happened to my spinup in the early hours of this morning. I got woken up by a BOINC sound, (appropriate!), and found the \'Can\'t connect ...\'
This is the 3rd time in 3.5 months, and my cure is a simple reboot. It may not work for everyone.

It happend again last night so I tried rebooting first. I didn\'t solve the problem - I still couldn\'t connect to the host. I went through the procedure I detailed earlier and, thankfully, it worked.

I am _not_ going to do anything for the next 6 and a half days that might cause a reboot on this machine. Once the spinup is finished I might experiment...

Ian

---