BOINC client "communication deferred", hardware firewall problems

Message boards : BOINC Manager : BOINC client "communication deferred", hardware firewall problems
Message board moderation

To post messages, you must log in.

AuthorMessage
Cykranosh

Send message
Joined: 16 Jun 06
Posts: 1
Message 4740 - Posted: 16 Jun 2006, 18:38:32 UTC

I installed BOINC and get "communication deferred" all the time; I suspect my hardware firewall is to blame. What port does BOINC use for communication? If it is standard HTTP port 80, there should be no problem there and the cause is something else.

There are selections for HTTP and UTP traffic in my router, all disabled by default (a Good Thing), but some software (maybe BOINC?) demand I open a port for them manually, so I suspect that's the case here.
ID: 4740 · Report as offensive
Aurora Borealis
Avatar

Send message
Joined: 8 Jan 06
Posts: 448
Canada
Message 4749 - Posted: 17 Jun 2006, 17:31:14 UTC - in response to Message 4740.  
Last modified: 17 Jun 2006, 17:31:49 UTC

I installed BOINC and get "communication deferred" all the time; I suspect my hardware firewall is to blame. What port does BOINC use for communication? If it is standard HTTP port 80, there should be no problem there and the cause is something else.

There are selections for HTTP and UTP traffic in my router, all disabled by default (a Good Thing), but some software (maybe BOINC?) demand I open a port for them manually, so I suspect that's the case here.

Ports for V5.4.9

boinc.exe needs internet access on ports 80 and 443 and local access (127.0.0.1) on ports 31416.
boincmgr.exe, boinccmd.exe and boinc.scr need local access on ports 31416.

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470
ID: 4749 · Report as offensive
Michael Gmirkin

Send message
Joined: 14 Jun 06
Posts: 8
United States
Message 4970 - Posted: 11 Jul 2006, 20:36:12 UTC - in response to Message 4740.  
Last modified: 11 Jul 2006, 20:37:37 UTC

I installed BOINC and get "communication deferred" all the time; I suspect my hardware firewall is to blame. What port does BOINC use for communication? If it is standard HTTP port 80, there should be no problem there and the cause is something else.

There are selections for HTTP and UTP traffic in my router, all disabled by default (a Good Thing), but some software (maybe BOINC?) demand I open a port for them manually, so I suspect that's the case here.


Yeah, why is it that basically every time I hit update it comes back with "communication deferred" (I just hit retry communications, and sometimes it works sometimes it doesn't).

Am I supposed to be getting "communication deferred" (I mean are the servers THAT busy that they always tell my machine to back off for 10 minutes), or does that signal a communication problem with the server?

It happens on my home machine, my work machine, etc. They're mostly XP SP 2 (home & pro). Probably have windows firewall turned on, but I've never gotten a pop-up asking whether or not to allow traffic or whatever. So, I assume all is working?

Like I said, I just hit retry communications and more often than not it works the second time?
BOINC Seti@Home Stats:

Classic Seti@Home Stats:
ID: 4970 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15478
Netherlands
Message 4978 - Posted: 11 Jul 2006, 22:40:56 UTC - in response to Message 4970.  

Yeah, why is it that basically every time I hit update it comes back with "communication deferred" (I just hit retry communications, and sometimes it works sometimes it doesn't).

It's a built in safety precaution into BOINC, so you can't "SPAM" or DDoS the project servers. Else each time you hit Update you contact the scheduler server. Now think of you and 9 other people doing this constantly for an hour. No one else would be able to get through.

So there is a deferral time built in in BOINC. If you hit Update again within 10 minutes, you are deferred until the countdown timer is at zero.
ID: 4978 · Report as offensive

Message boards : BOINC Manager : BOINC client "communication deferred", hardware firewall problems

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.