I don't know enough about how BOINC works to have an idea of where to look for this problem.

I have a computer that "view computers" shows has not connected since June 13.

In the last fifteen hours:

I have installed the new Lunatics app.
I have an internet connection.
I have taken-down the firewall.(it was working fine with the firewall up, I was just being sure)
I have seen "uploading" in the task list.
I get nothing but back-offs.
I have told it to "do communication"
I have told it to run benchmarks (it did)
I have stopped and restarted the manager.
The icon shows the client is "connected".
I have hard booted twice.
It HAS work and is crunching-away.
Two other computers on the same router reported-in yesterday.
I have flushed DNS.
I have forced a new DHCP connection (which seemed silly since I have an internet connection, but I did it anyway).

What else could be "broken?"

I'm NOT concerned with the inability to upload, I'm concerned that BOINC doesn't seem to know the computer is out here, or at least is not registering a "contact".

I don't want to waste work by starting over, especially since work is hard to come-by, but I'm at a loss what to try next. This computer has been very reliable for a long time.

EDIT: Both DC Stats and BOINC stats are showing a very small amount of work reported each day since June 13.

Bret

When you tell BOINC to update do you get any response? Something along the lines of this is what I would expect in the messages tab.
6/17/2011 4:07:58 PM SETI@home update requested by user
6/17/2011 4:08:00 PM SETI@home Sending scheduler request: Requested by user.
6/17/2011 4:08:00 PM SETI@home Not reporting or requesting tasks
6/17/2011 4:08:03 PM SETI@home Scheduler request completed
If there is no response of any kind then you may need to enable the HTTP debugging flags to do further investigation.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Put your firewall back up, as you are unprotected. Just wait as the servers are trying to catch up. The jams should clear in the next few hours. The problems are not from your end.

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

I know this might sound wierd and maybe its just coincidence but i run 3 computers all connected to the same router. Sometimes the i7 will not connect at all. Id do reboots and nothing. So when that happens I turn off the computer and then hit the power switch on my strip and wait a few minutes. On power up I get a connection. like I said its weird but it works for me.

Edit- My router is on the same power strip as the computer.

---

[/quote]

Old James

Thanks Steve.

I did put the firewall back up. It was just an "experiment" while I was sitting there.

I thought I was being patient waiting four days since the current trouble didn't start four days ago.

I'm not panicking.

As I've said before, it's the inconsistencies that make me second-guess. "Four can, one can't? For four days?"

It has connected. I didn't touch it.

False anxiety.

Bret

I know this might sound wierd and maybe its just coincidence but i run 3 computers all connected to the same router. Sometimes the i7 will not connect at all. Id do reboots and nothing. So when that happens I turn off the computer and then hit the power switch on my strip and wait a few minutes. On power up I get a connection. like I said its weird but it works for me.

Edit- My router is on the same power strip as the computer.

My router does the same, sometimes it just drops the wireless, but the wired works just fine. After powering down everything, letting it sit for about a minute, power it back on, everything is fine.

@tbret, don't know if you've tried what we've posted above, but power cycling your router/modem might help, it never hurts either. But as Steve said, its more than likely on the SETI end, gotta remember there's quite a few computers trying to connect, get work, upload work, report work, etc. Its like a million people trying to squeeze into a Mcdonalds on lunch break. LOL

---

i can not connect scheduler by 15.6.11
i have all resets done, no connect
it is by the Berkeley site

tracert 208.68.240.20

Routenverfolgung zu setiboinc.ssl.berkeley.edu [208.68.240.20] über maximal 30
Abschnitte:

1 19 ms 19 ms 16 ms lo1.br08.ber.de.hansenet.net [xxx.xxx.xx.xx]
2 17 ms 17 ms 18 ms ae0-101.cr01.ber.de.hansenet.net [xxx.xxx.xx.xx]

3 35 ms 35 ms 35 ms so-0-1-0-0.cr01.fra.de.hansenet.net [xxx.xxx.xx.xx]
242]
4 37 ms 37 ms 37 ms ae0-0.xd02.fra.de.hansenet.net [xxx.xxx.xx.xx]
5 37 ms 36 ms 35 ms ae1-0.pr03.decix.de.hansenet.net [xxx.xxx.xx.xx]
]
6 37 ms 35 ms 37 ms 20gigabitethernet4-3.core1.fra1.he.net [80.81.19
2.172]
7 62 ms 51 ms 51 ms 10gigabitethernet1-2.core1.par1.he.net [72.52.92
.89]
8 44 ms 45 ms 45 ms 10gigabitethernet1-1.core1.par2.he.net [184.105.
213.90]
9 132 ms 125 ms 125 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.
213.93]
10 198 ms 225 ms 199 ms 10gigabitethernet1-4.core1.pao1.he.net [72.52.92
.29]
11 * * * Zeitüberschreitung der Anforderung.
12 * * * Zeitüberschreitung der Anforderung.
13 * * * Zeitüberschreitung der Anforderung.
14 * * * Zeitüberschreitung der Anforderung.

---

I have no problems connecting.
My DOS-tracert gives another route:

I enter he.net on core1 in stead of 20gigabitethernet:

8 core1.nyc4.he.net [198.32.118.57]
9 10gigabitethernet3-1.core1.sjc2.he.net [72.52.92.25]
10 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
11 64.71.140.42
12 208.68.243.254
13 setiboinc.ssl.berkeley.edu [208.68.240.20]

But if I try via tracert.org I am getting nowhere:

2 te1-4.dsr01.hstntx1.networklayer.com (207.218.223.5) 0.574 ms 0.555 ms 0.627 ms
3 e4-2.ibr02.hstntx1.networklayer.com (207.218.245.29) 0.525 ms e4-1.ibr02.hstntx1.networklayer.com (207.218.245.25) 0.583 ms 0.594 ms
4 e3-4.ibr04.dllstx3.networklayer.com (70.87.253.53) 5.374 ms 5.392 ms 5.353 ms
5 * * *
6 10gigabitethernet1-2.core1.phx1.he.net (72.52.92.253) 26.705 ms 26.915 ms 26.916 ms
7 10gigabitethernet2-2.core1.lax1.he.net (72.52.92.249) 36.619 ms 42.632 ms 36.138 ms
8 10gigabitethernet1-3.core1.pao1.he.net (72.52.92.21) 44.667 ms 44.823 ms 44.660 ms
9 64.71.140.42 (64.71.140.42) 61.915 ms 45.096 ms 44.913 ms
10 208.68.243.254 (208.68.243.254) 87.105 ms 87.360 ms 86.092 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

---

Goodbye Seti Classic

i have the same

2 te1-4.dsr01.hstntx1.networklayer.com (207.218.223.5) 0.571 ms 1.199 ms 0.544 ms
3 e4-1.ibr02.hstntx1.networklayer.com (207.218.245.25) 0.579 ms 0.522 ms 0.898 ms
4 e3-4.ibr04.dllstx3.networklayer.com (70.87.253.53) 5.355 ms 5.299 ms 5.355 ms
5 * * *
6 10gigabitethernet1-2.core1.phx1.he.net (72.52.92.253) 26.776 ms 26.932 ms 26.854 ms
7 10gigabitethernet2-2.core1.lax1.he.net (72.52.92.249) 36.630 ms 36.344 ms 36.929 ms
8 10gigabitethernet1-3.core1.pao1.he.net (72.52.92.21) 44.851 ms 53.818 ms 49.617 ms
9 64.71.140.42 (64.71.140.42) 44.904 ms 45.092 ms 45.368 ms
10 208.68.243.254 (208.68.243.254) 87.858 ms 87.330 ms 85.854 ms
11 * * *
12 * * *
13 * * *

---

Tried tracert to setiboinc.ssl.berkeley.edu, which gives:

Busy tracing route to setiboinc.ssl.berkeley.edu [208.68.240.20]
via maximaal 30 hops:

1 1 ms 2 ms 1 ms 192.168.2.1
2 251 ms 269 ms 273 ms 195.190.249.32
3 319 ms 379 ms 339 ms nl-asd-dc2-isp-bb21-ge-2-0-0.320.wxs.nl [213.75.1.17]
4 382 ms 374 ms 400 ms 20gigabitethernet1-3.core1.ams1.he.net [195.69.145.150]
5 500 ms 456 ms 539 ms 10gigabitethernet2-1.core1.par2.he.net [184.105.213.102]
6 571 ms 590 ms 637 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.213.93]
7 754 ms 818 ms 469 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
8 480 ms 486 ms 494 ms 64.71.140.42
9 669 ms 716 ms 716 ms 208.68.243.254
10 497 ms 495 ms 589 ms setiboinc.ssl.berkeley.edu [208.68.240.20]

Trace completed. This is the last attempt from my LT, using WLAN.

18-6-2011 15:33:31 | SETI@home | Sending scheduler request: To fetch work.
18-6-2011 15:33:31 | SETI@home | Reporting 1 completed tasks, requesting new tasks for CPU
18-6-2011 15:33:35 | SETI@home | Scheduler request completed: got 1 new tasks
18-6-2011 15:33:38 | SETI@home | Started download of 28ap11ad.11266.20517.11.10.226.vlar
18-6-2011 15:34:20 | SETI@home | Temporarily failed download of 28ap11ad.11266.20517.11.10.226.vlar: HTTP error
18-6-2011 15:34:20 | SETI@home | Backing off 14 min 7 sec on download of 28ap11ad.11266.20517.11.10.226.vlar
18-6-2011 15:34:34 | | Project communication failed: attempting access to reference site
18-6-2011 15:34:35 | | Internet access OK - project servers may be temporarily down.
18-6-2011 15:48:28 | SETI@home | Started download of 28ap11ad.11266.20517.11.10.226.vlar
18-6-2011 15:48:43 | SETI@home | Finished download of 28ap11ad.11266.20517.11.10.226.vlar

Atleast 1 WU on my LT, other hosts, still have some work and can contact
SETI@home or SETI Bêta.
Maybe because (too) much shorties, i.e. ~5 minutes, my XP64 box had
hundreds of them, also my i7-2600(WIN 7 x64)which causes a lot of traffic.
(And 'spare-CPU cycles')!

---

mystery: after i set a proxy server in, i could connect scheduler and up / download Wu´s.... i was complete empty at this point

when i kill the proxy, no connection will done again

---

Strange indeed, I don't use a proxy, maybe something to do with static or
dynamic IP adress?

Could IPv6, have something to do with this? This month many IP Providers
will test their IPv6 capabillity, also 'yours'?

And maybe some 'older' MODEM/ROUTERs can't handle IPv6, properly?

Well just guessing, I lack the time to figure this out, atm.

---

For IPv6 try this.....

IPv6 Test

---