Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 23
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
You don't need a password. Just type localhost and it will fill in the password for you.
|
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Didactylos:
No success. I put in "localhost" without the quotes and it does "not" fill in the password and it tells me the "Connection Failed" Al |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well, if you have a real problem, the most likely culprit is the firewall. RPC is a common virus vector, so firewalls usually clamp down tight. The normal RPC port is 135, and you shouldn't have any problems with RPC to localhost. Assuming the RPC service is working properly, you should check your firewall logs and settings.
----------------------------------------The BOINC Manager uses ports 1043 or 31416. If gui_rpc_auth.cfg does not exist, you should have no trouble connection with a blank password. [Edit 1 times, last edit by Former Member at Mar 3, 2006 11:15:51 PM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
My firewall is open for all ports outbound. It is also working fine on the Mac version of BOINC and the PC version of UD.
Not sure what the issue is? Al |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This has nothing to do with external communications.
The BOINC Manager is a separate program, that needs to talk to BOINC. It does this using RPC. A tightly controlled security policy may restrict or disable RPC. It's unlikely, though. I suspect you screwed something up when you were messing around earlier. Why not try reinstalling BOINC? |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Didactylos:
Already uninstalled and reinstalled the BOINC. I uninstalled it via the Add/Remove programs. I then removed the BOINC folder/directory from f:\Program Files. I then recreated the F:\ProgramFiles\BOINC\ folder I then reinstalled it and get the same error. ???? Al |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
OK here is what I just did:
1 - I uninstalled the BOINC applications via Start > Settings > Control Panel > Add/Remove Programs BOINC. 2 - I then delete the BOINC folder from the F:\Program Files\ folder. 3 - I then deleted the previously download boinc_5.2.13_windows_intelx86.exe 4 - I then went to the worldcommunitygrid.org site and dowloaded a fresh version of boinc_5.2.13_windows_intelx86.exe 5 - I then installed this in my F:\Program Files\BOINC target folder 6 - I then started the BOINC Manager and still get the same error "BOINC Manager is not able to connected to a BOINC client" 7 - I tried to set the "Select Computer" Host name to "localhost" with the quotes removed, same error 8 - There is no gui_ .cfg password file in my F:\Program Files\BOINC target folder. Any ideas anyone? TIA, Al |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
My Grid" Device Manager shows two devices:
1 is the UD client on my system DELLPRODUCTION. 2 is a BOINC device is my Mac which I tried unsucessfully of the PC Server. What I want is for DELLPRODUCTION to be my BOINC device. Obviously I cannot use my Mac for WCG. It is being used for rosetta@home Any and all guidance is appriciated. After I get this running, I may take my 15 PIII blades and config them to run. Will have to install an OS and probably add memory (only 128 MB - so sad). TIA Al |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi ahoover,
I do not have any answers, but it looks to me as though you are discussing 2 separate problems. First, you have to get your BOINC Manager connected to your BOINC client on your computer. Once that is done, you have to tell BOINC Manager to connect your BOINC client to your account on WCG, which will automatically install a new device on the server. So the problem is to connect BOINC Manager to your BOINC client. Then it should be easy to connect to the project. What could be preventing Manager from connecting to localhost? Ideas, anybody? Lawrence |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Perhaps I should use a list:
|
||
|
|
![]() |