I'm running BOINC 4.13 / SETI 4.08. On my two home computers (only intermittent internet connection via ISDN) I now had the following problem six (!) times over the last couple of weeks:

Client runs smoothly, dl/ul of wus is okay; credit is granted. Then at one time, I can't dl additional wus with the following three message lines

"Sending request to scheduler: ..."
"Scheduler RPC to ... failed"
"No servers responded"

Even though I know the scheduler *is* running (other machines are able to connect at the same time). The client continues to crunch wus and submits them (and states "transmission okay". However, no credit is granted for these wus -- they simply seem to vanish. Internet connection *is* working all the time (other programs work fine) and I didn't change any firewall rules in the meantime.

I tried the "Reset project" option. This leads to a complete new download of all software; that time I get the resonse "Scheduler RPC to ... succeeded". However, some time later (days, sometimes weeks), the same happens again.

This problem occured only on my machines with ISDN dialup; never on computers with a permanent network connection. Anybody having the same/similar proglem? Any ideas or suggestions? After not getting credit for a total of several weeks of cpu time, I'm considering to give up.

---

Sounds like it is NOT a Boinc issue if it works for a while and then stops and ONLY on your ISDN machines.
Sounds more like a configuration issue with the ISDN stuff, or the way those computers are setup under them.

---

First, thanks for your reply!

> Sounds like it is NOT a Boinc issue if it works for a while and then stops and
> ONLY on your ISDN machines.

Hmmm. However, the curious thing is that all other net-based application continue to work: Even BOINC continues to connect and upload WUs to the server (but the server does not count them). For a problem with ISDN I would expect problems with other programs as well. The other machines have a static IP and 24/7 network access.

> Sounds more like a configuration issue with the ISDN stuff, or the way those
> computers are setup under them.

Might be, but I doubt it since everything else seems to work. Can it be the different IPs assigned to my computer each time I dial? Anything which leaves BOINC in an "unclean" state after it fails to connect to a server (sometimes I forget to set the "Disable BOINC network access" switch in the client)?

I really don't have any ideas how to solve it right now. Of course, if nobody else has similar problems, its very likely that it's really my particular combination of hardware/software ... I'll post again if I get additional clues.

---

I have the same problem. One of 7 comuters crunches all the time, downloads WUs and keeps them in the state Ready to report. The funny thing is it downloads new WUs but does not update the project stats.
All of the comoputers are connected to our LAN, all have the same system.
Weird.

---