Hi, i am a newbie boinc user and i can't connect to the scheduler. I always get the message "Scheduler RPC to...failed. Deferring communication..." Now it's a week i have this messages and haven't any wu to crunch. I know that recently there were trouble in the campus but now the situation seems normalizing...I am also crunching for cpdn and it works fine, even the scheduler.
Thanks and sorry for my poor english...

---

You either have 5 computers or you have connected 5 times and detached 4 times, your acct shows you have about 40 WUs.....

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

I switched to boinc when they started having troubles so to get new work i tried to disconnect from project and riconnect to it...but i don't think this is the reason i can't connect to scheduler, right??? Yes, i have about 50 wu in the ready to report status, near the deadline.
Thanks...

---

Server appears to be up, so first you need to go to view computers and merge all your boxes, then do an update, just for reference, try not to do a reset or detach unless all others options have been used.....

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

you could look up your error message in the Wiki. click the link above my signature.

tony

---

Failure to connect to the scheudler is a symptom of a communications problem between your computer and the project servers. It can be anything from a mis-configured personal firewall to the servers at the project being down.

---

BOINC WIKI

Your account shows 545 WUs, mostly completed and credited dating back to early July...well over a week ago.

Not sure I understand what the problem is....

---

I tried to uninstall the antivirus and firewall software and the result is the same...


24/07/2005 10.07.17|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
24/07/2005 10.07.17|SETI@home|Requesting 0 seconds of work, returning 42 results
24/07/2005 10.08.01|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
24/07/2005 10.08.01|SETI@home|No schedulers responded
24/07/2005 10.08.02|SETI@home|Deferring communication with project for 58 seconds
24/07/2005 10.08.52||request_reschedule_cpus: project op
24/07/2005 10.08.53|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
24/07/2005 10.08.53|climateprediction.net|Requesting 0 seconds of work, returning 0 results
24/07/2005 10.09.03|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded


I can reach the cpdn scheduler but S@H is still hanging...

Thanks

---

I can reach the cpdn scheduler but S@H is still hanging...

Thanks

If your firewall is back on, make sure that ports 80, 1043, and 31416 are open. Also make sure that Boincmgr.exe and Boinc.exe have full access.

After that, search thread titles (using keyword search) for Europe. There is a thread with a title like "Connection problems to Europe" or something like that, that contains Proxy settings for getting connected. I'm not a network guru.

Maybe you could open up a command prompt window and type

tracert setiboinc.ssl.berkeley.edu

and see if it gets through.

---

I found an old example from an old thread of what one should look like.
**************************************
You should get something like below.
Try it on both systems and see if they following the same route - or at least ending-up at the same place.
The final IP address [66.28.250.124] is the critical bit.

Command Prompt:
tracert setiboinc.ssl.berkeley.edu

Tracing route to setiboinc.ssl.berkeley.edu [66.28.250.124]
over a maximum of 30 hops:


7 19 ms 18 ms 17 ms gfd-bb-a-ae0-0.inet.ntl.com [213.105.172.5]
8 18 ms 18 ms 18 ms tele-ic-1-so-110-0.inet.ntl.com [62.253.185.78]
9 19 ms 18 ms 18 ms 212.250.14.62
10 91 ms 90 ms 91 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0.46]
11 108 ms 110 ms 109 ms p5-0.core01.ord01.atlas.cogentco.com [66.28.4.110]
12 159 ms 157 ms 157 ms p5-0.core01.sfo01.atlas.cogentco.com [66.28.4.185]
13 160 ms 160 ms 160 ms uc-berkeley.demarc.cogentco.com [66.250.4.74]
14 171 ms 167 ms 171 ms 66.28.250.124

Trace complete.
____________

---

Hi
The web page I did for European connection problems is still available. You may want to try one of the proxies on that page which are known to work. Do the tracert as suggested earlier just to see if you can reach the server. If not try a proxy from the page.

Try here for help There is some French and German translation if that helps.

Hope that helps.

Amities et bon courage de l'Angleterre!

Ian

---

Does anybody know if the Berkeley scheduler actually stops some machines from getting through. Are some machine Blacklisted?. And if so how do you find this out.
I now have 6 machines that will not contact the scheduler. All they get is no reply. The others are still fine.
I reinstalled boinc on one machine and then it connected fine. Lost 3 days work on the machine to find this out.

Thanks

Nairb

---

Nairb --

You might want to do a PING trace from the machines in question, to see where/if the path to Berkeley is blocked

---

I don't know what to do now, the tracert setiboinc.ssl.berkeley.edu works fine even if slowly and so the ping command. I tried changing the scheduler address in the client_state.xml file with its ip address and it's the same, i have seen that with ip 66.28.250.125 i got an answer from the scheduler (No work, project is down) but now the right ip is 66.28.250.124. I have also tried several proxy servers (trasparent and anonymous) but it doesn't work too. Before the last outage i could connect only via proxy servers and even the proxies i used don't work now...i start thinking they have "banned" my pc...
Now i would to reinstall the boinc client but i'd like not to loose the finished wu, have i only to save the project folder or even other files are needed?

Thanks

---

Barbablu - I wonder if we have the same problem. I have 20 machines on a network. All talk thro a proxyserver fine. For three days 6 of the machines have just stopped connecting to the scheduler. They UPLOAD completed wu OK but cannot REPORT or Download any workunits.
All I get is
7/24/05 4:58:56 PM|SETI@home|No schedulers responded
No error at all. I can tracert ok.
I have had this before and the only way to fix it was to detach and start again.
In my case I have 6*3 days of wu to report.

Does anybody know if the berkeley scheduler can decide to block some machines?.
A reboot etc dosent help. I even changed the proxyserver for a while to see if that helped - Nop

Thanks

Nairb

---

Yes, i think it's the same problem. I can upload result, tracert and ping but i can't report the result and get the new ones. I have exactly 42 wu to report, the first deadline is 28/07, hope to solve before that....

---

I see you're using BOINC 4.27
Ever thought of trying a newer version?

---

Now i'm using boinc 4.45 and it's the same...thanks

---

This really seems like the same problem Paul (the gas giant) and a couple others were having while back. They didn't find a cure, but did manage to get them working using a proxy (with some success). I'm at a loss

---