My computer is a new machine running Windows 7 professional 64 bit. It has an Intel i5 processor, 8 Meg of RAM, with a 2 TB hard drive. I am running BOINC Manager 7.0.64

I downloaded BOINC and signed up with SETI@home a few days ago. It worked great. No problem, at first. I was very happy. Therefore, I know that this computer, its drivers, software, etc., are compatible with BONIC.

Then, after a few hours of working great, it lost its connection to the server and stopped working. It never was able to connect again, even though it keeps trying. I deleted the BOINC software and reinstalled it several times. This did not help. When I restall, it doesn't even give the chance to select a project. It never asks me to select one. In the BOINC manager advanced view, under projects, all command boxes are grayed out. The tasks tab shows no tasks. The disk tab shows "no projects: 0 bytes used". The event log is blank. I keep getting a pop up box which says "The BOINC client has exited unexpectedly 3 times within the last 3 minutes". Then it asks me if I would like to try to reconnect. But it can't. It is as if I am not connect to the internet.

Please note that my internet connection works fine. I can go to any website, download anything I want, etc. without any problem. I disabled the Windows firewall. It didn't help. The simplest way to describe the BOINC client is that it is just dead. It runs, but can not connect to a server, even though it keeps trying. But it did work very well with SETI@home for a few hours, before it died. Deleting and downloading the software again does not help.

Any help would be appreciated. Thank you. I don't know if I'm supposed to give my email address in this message, but here it is: [email protected]

Are you sure it can't connect to a server?
Isn't the message "Cannot connect to a client"?

As when it is a message alike that, it means that BOINC Manager (which is just a graphical user interface, to make it easier to give commands to the client) can't make contact with the client (which does all the work). And THAT usually happens because:
1. You didn't allow boinc.exe and boincmgr.exe through your firewall.
2. You didn't set the BOINC Data directory up as an exclusion in your firewall/anti virus programs.

Now, if it IS that BOINC can't connect to a server, it is ALSO because of firewall problems. Don't disable the firewall, we never ask you to do that, as it's dangerous. Enough bad stuff on the internet that'll get onto your system when you do something like that.

No, just add:
boinc.exe and boincmgr.exe to the firewall exclusion zone, if possible tell them to use TCP port 31416.
Separately, boinc.exe requires access to the internet, on TCP ports 80 and 443 (HTTP and HTTPS).

---