hi all!

Need ya help please :)

I wanted to put all my BOINC Machines witch are spread over the city into my BOINCTasks Program at home. I had no problems with that except 4 machines behind an verryyy easy router witch cant do portToport forwarding. So i can only define straight rules like the standart boinc port to one machine behind the router. The other three are no reachable with this methode. So i wanted to change the BOINC remote listen port on these three machines. Then i would add the additional straight rules as forward onto the router. The recommend command for that is boinccmd.exe --gui_rpc_port N. So i set the port i wanted as N but it looks like he does not understand this option. Whats going wrong there?

Thanks for any helps :)

---

DSKAG Austria Research Team: http://www.research.dskag.at



Crunching for my dead Dog who had "good" Braincancer..

The --gui_rpc_port N is a command you use on boinc.exe, not on boinccmd.exe

So you start the client with boinc.exe --gui_rpc_port 31418 if you want that client to communicate with a BOINC Manager (boincmgr.exe) on TCP port 31418.

---

Great :) I read it twice with boinccmd and thought that would be correct and didnt tested it with boinc.exe itself. It works perfect now. THX!!!



The only problem i hope to solve is, to get the local Boincmgr on eatch machine back running on the new port. I tried it over the gui with a connect to localhost:31418 but seems not to work, perhaps i have to use a commandline here too with the boincmgr.exe. i will see the next days :)

BOINC Manager can be told to use a specific port at its startup as well.
I've dealt with this before, and Fred of BOINC Tasks posted in that thread as well. So why not start with this thread, post 50100 and further down, then let us know if that helped you?

---

Oh thanks for the fast working solution :) POEM needs some babysit sometimes so a local+remote manager is important there ^^

Great. Glad to have been of help.
The bill's in the post. :-)

---