I don't remember if 4.25 could switch the port from 1043 to 31416. At the end BOINC may be was quicker and get the port at first.
#BOINC DAEMON SOFTWARE#
Some firewalls may wrongly see the a connect to "localhost" as a not allowed access and block it.īut that it needs some restarts to get it working again feels like a software capturing the port problem. " with a empty host name or "localhost" as host name. Then I would try to connect to the BOINC Daemon with the open BOINC Manager again, by "select Computer. If a problem like this happens, I look at first with the task manager if the application (setiathome_4.xx) is still running and if the BOINC Daemon (boinc.exe) is still to see in taskmanger. There it may be possible that a problem happens and the application killed the BOINC Daemon in a error situation. On the other side the BOINC Daemon started and scheduled the project applications.
This may create a problem where the BOINC Manager loose the connection or can't create a connection to the BOINC daemon and all tabs are empty. The problem is, that there is software out there, that doesn't care about offical ports, i.e. This programs communicate over TCP socket 1043, or in newer releases optional try 31416 if the official port didn't work. BOINC client software > 4.19 is splitted in the "master control program", called the BOINC Daemon (boinc.exe) and the "graphic user interface", called BOINC Manager (boincmgr.exe).
0 kommentar(er)
