Recently my one computer has been having connection issues.

I get the pop up that BOINC can't connect to the Internet. Opening BOINC shows a backog of transfers. Try to Retry them, gets a message that BOINC can't connect to the Internet. There will typically be a Message stating a problem with the Interent connection or proxy set (no proxy).

If I reboot, it will connect and I can do all the transfers, but the next time BOINC tries to do a transfer, again, no connection.

Sometimes I get a message that the servers may be down, but I understand that one. It is the no Internet connection that is strange. Especially as all other programs accessing the Internet are fine.

And this in only happening on ONE computer, out of 5 doing BOINC.

I Dl'd and installed 6.10.18 and same thing.

Running WinXP SP2, i7 920, 6GB RAM.

Any ideas?

Running WinXP SP2

One thing BOINC depends on is that you update your Windows regularly. Tried Service Pack 3 and further updates already?

Another thing that BOINC (boinc.exe) needs is to be able to pass through your firewall, on ports 80 and 443.

---

Updated recently.

Same router/firewall for all 5 computers.

Same router/firewall for all 5 computers.

I meant the firewall software on your computer. TCP ports 80 and 443 are usually already open, yet hidden on hardware firewalls, else you can't internet. And while this is true for the software firewalls as well, it is better to add an exception for boinc.exe in the software. Be it Windows firewall, or a 3rd party option.

---

It's also possible that your network card is allowed to go to sleep. Check that it isn't. I had that happen to me not too long ago.

---

Interesting idea.

But today, I was on teh computer, using borwser the entire time, so it shoulnd't have gone tosleep.

And shouldn
't BOINC be able to connect once I start running a browser?

Another data point, if I Exit BOINC and restart it, sometimes it will access the Internet.

OK, please make a file called cc_config.xml in your BOINC Data directory. Use Notepad or another clear text editor (not Wordpad or MS Word with XML file save option. The XML we write isn't true XML)

The Data directory is the directory in which client_state.xml resides. It may be hidden. Its path can be found in the BOINC start-up messages, third to 6th line from the top. By default, if you didn't change its path, it's at c:\documents and settings\all users\application data\BOINC\

Add into cc_config.xml (copy from below):

<cc_config>
   <log_flags>
       <http_debug>1</http_debug>
       <http_xfer_debug>1</http_xfer_debug>
       <network_status_debug>1</network_status_debug>
   </log_flags>
   <options>
       <http_1_0>0</http_1_0>
   </options>
</cc_config>

Save the file, make sure it gets the .XML extension, not something else (such as .TXT when using Notepad), else rename it so it only has the .XML extension.

Then go BOINC Manager->Advanced view->Advanced->Read config file, or maybe easier, exit and restart BOINC.

Update on any of the projects you're attached to, then switch to the Messages tab and copy the portion of text you see on the communications. Post all of that here.

By default BOINC uses HTTP 1.1 for communications, but on some systems this just doesn't work. In that case you can try to switch on the <http_1_0>0</http_1_0> line, by changing it to <http_1_0>1</http_1_0> (that's a one), saving the file and reading it again, or restarting BOINC and then contacting a project again.

---

Thanks. Of course, now I am getting messages that the project is shutdown for maintenance.

And it seems that it has been communicating fine. :)

But here is what it said other than the down for maintenance. I removed multiple duplicates of the same message every few seconds.

12/1/2009 4:25:51 PM Re-reading cc_config.xml
12/1/2009 4:25:51 PM Re-read config file
12/1/2009 4:25:51 PM log flags: file_xfer, sched_ops, task, http_debug, http_xfer_debug, network_status_debug
12/1/2009 4:25:55 PM [network_status_debug] status: don't need connection
1.
.
12/1/2009 4:26:07 PM [network_status_debug] status: don't need connection
12/1/2009 4:26:07 PM SETI@home update requested by user
12/1/2009 4:26:07 PM [network_status_debug] status: don't need connection
.
12/1/2009 4:26:09 PM [network_status_debug] status: don't need connection
12/1/2009 4:26:09 PM SETI@home Sending scheduler request: Requested by user.
12/1/2009 4:26:10 PM SETI@home Reporting 8 completed tasks, not requesting new tasks
12/1/2009 4:26:10 PM [http_debug] HTTP_OP::init_post(): http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
12/1/2009 4:26:10 PM [http_debug] HTTP_OP::libcurl_exec(): ca-bundle 'C:\Program Files\BOINC\ca-bundle.crt'
12/1/2009 4:26:10 PM [http_debug] HTTP_OP::libcurl_exec(): ca-bundle set
12/1/2009 4:26:10 PM [http_debug] [ID#0] info: timeout on name lookup is not supported
12/1/2009 4:26:10 PM [http_debug] [ID#0] info: About to connect() to setiboinc.ssl.berkeley.edu port 80 (#0)
12/1/2009 4:26:10 PM [http_debug] [ID#0] info: Trying 208.68.240.20...
12/1/2009 4:26:10 PM [network_status_debug] status: online
12/1/2009 4:26:10 PM [http_debug] [ID#0] info: Connected to setiboinc.ssl.berkeley.edu (208.68.240.20) port 80 (#0)
12/1/2009 4:26:10 PM [http_debug] [ID#0] Sent header to server: POST /sah_cgi/cgi HTTP/1.1
User-Agent: BOINC client (windows_intelx86 6.10.18)
Host: setiboinc.ssl.berkeley.edu
Accept: */*
Accept-Encoding: deflate, gzip
Content-Type: application/x-www-form-urlencoded
Content-Length: 129589
Expect: 100-continue


12/1/2009 4:26:10 PM [network_status_debug] status: online
12/1/2009 4:26:10 PM [http_debug] [ID#0] Received header from server: HTTP/1.1 100 Continue

12/1/2009 4:26:11 PM [network_status_debug] status: online
12/1/2009 4:26:12 PM [network_status_debug] status: online
12/1/2009 4:26:13 PM [http_debug] [ID#0] Received header from server: HTTP/1.1 200 OK

12/1/2009 4:26:13 PM [http_debug] [ID#0] Received header from server: Date: Tue, 01 Dec 2009 21:26:13 GMT

12/1/2009 4:26:13 PM [http_debug] [ID#0] Received header from server: Server: Apache/2.2.9 (Fedora)

12/1/2009 4:26:13 PM [http_debug] [ID#0] Received header from server: Connection: close

12/1/2009 4:26:13 PM [http_debug] [ID#0] Received header from server: Transfer-Encoding: chunked

12/1/2009 4:26:13 PM [http_debug] [ID#0] Received header from server: Content-Type: text/plain; charset=UTF-8

12/1/2009 4:26:13 PM [http_debug] [ID#0] Received header from server:

12/1/2009 4:26:13 PM [http_xfer_debug] HTTP: wrote 187 bytes
12/1/2009 4:26:13 PM [http_debug] [ID#0] info: Expire cleared
12/1/2009 4:26:13 PM [http_debug] [ID#0] info: Closing connection #0
12/1/2009 4:26:13 PM [network_status_debug] status: online
12/1/2009 4:26:14 PM [network_status_debug] status: online
12/1/2009 4:26:15 PM SETI@home Scheduler request completed
12/1/2009 4:26:15 PM SETI@home Message from server: Project is temporarily shut down for maintenance
12/1/2009 4:26:15 PM [network_status_debug] status: online
.
.
.
12/1/2009 4:26:24 PM [network_status_debug] status: don't need connection
.
.
.
12/1/2009 4:26:44 PM SETI@home update requested by user
12/1/2009 4:26:44 PM [network_status_debug] status: don't need connection
12/1/2009 4:26:45 PM SETI@home Sending scheduler request: Requested by user.
12/1/2009 4:26:45 PM SETI@home Reporting 8 completed tasks, not requesting new tasks
12/1/2009 4:26:45 PM [http_debug] HTTP_OP::init_post(): http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
12/1/2009 4:26:45 PM [http_debug] HTTP_OP::libcurl_exec(): ca-bundle set
12/1/2009 4:26:45 PM [http_debug] [ID#1] info: timeout on name lookup is not supported
12/1/2009 4:26:45 PM [http_debug] [ID#1] info: About to connect() to setiboinc.ssl.berkeley.edu port 80 (#0)
12/1/2009 4:26:45 PM [http_debug] [ID#1] info: Trying 208.68.240.20...
12/1/2009 4:26:45 PM [network_status_debug] status: online
12/1/2009 4:26:45 PM [http_debug] [ID#1] info: Connected to setiboinc.ssl.berkeley.edu (208.68.240.20) port 80 (#0)
12/1/2009 4:26:45 PM [http_debug] [ID#1] Sent header to server: POST /sah_cgi/cgi HTTP/1.1
User-Agent: BOINC client (windows_intelx86 6.10.18)
Host: setiboinc.ssl.berkeley.edu
Accept: */*
Accept-Encoding: deflate, gzip
Content-Type: application/x-www-form-urlencoded
Content-Length: 129589
Expect: 100-continue


12/1/2009 4:26:46 PM [network_status_debug] status: online
12/1/2009 4:26:47 PM [http_debug] [ID#1] info: Done waiting for 100-continue
12/1/2009 4:26:47 PM [network_status_debug] status: online
12/1/2009 4:26:48 PM [network_status_debug] status: online
12/1/2009 4:26:48 PM [http_debug] [ID#1] Received header from server: HTTP/1.1 100 Continue

12/1/2009 4:26:49 PM [network_status_debug] status: online
12/1/2009 4:26:49 PM [http_debug] [ID#1] Received header from server: HTTP/1.1 200 OK

12/1/2009 4:26:49 PM [http_debug] [ID#1] Received header from server: Date: Tue, 01 Dec 2009 21:26:48 GMT

12/1/2009 4:26:49 PM [http_debug] [ID#1] Received header from server: Server: Apache/2.2.9 (Fedora)

12/1/2009 4:26:49 PM [http_debug] [ID#1] Received header from server: Connection: close

12/1/2009 4:26:49 PM [http_debug] [ID#1] Received header from server: Transfer-Encoding: chunked

12/1/2009 4:26:49 PM [http_debug] [ID#1] Received header from server: Content-Type: text/plain; charset=UTF-8

12/1/2009 4:26:49 PM [http_debug] [ID#1] Received header from server:

12/1/2009 4:26:49 PM [http_xfer_debug] HTTP: wrote 187 bytes
12/1/2009 4:26:49 PM [http_debug] [ID#1] info: Expire cleared
12/1/2009 4:26:49 PM [http_debug] [ID#1] info: Closing connection #0
12/1/2009 4:26:50 PM SETI@home Scheduler request completed
12/1/2009 4:26:50 PM SETI@home Message from server: Project is temporarily shut down for maintenance
12/1/2009 4:26:50 PM [network_status_debug] status: online
.
.
.
12/1/2009 4:27:00 PM [network_status_debug] status: don't need connection

Seti did have problems with its download servers over the weekend. Yet that won't make your BOINC not be able to use the internet at all.

So just leave BOINC running with these extra flags for now, then when you encounter the same problem, please post the part of the log that matters (not all of it, please. :-))

---

Will do, thanks for the help.

Actually I turned off the new configuration, but will use it if I run into problems again.