Folder data and error 417

Message boards : Questions and problems : Folder data and error 417
Message board moderation

To post messages, you must log in.

AuthorMessage
PGRID

Send message
Joined: 31 Jan 11
Posts: 20
Venezuela
Message 46037 - Posted: 18 Oct 2012, 14:28:54 UTC

where is the data folder of BOIN? i need find the file cc_config.xml...

I try to connect some machines using the boinc manager and I get the error 417

Thanks!
ID: 46037 · Report as offensive
Profile Gundolf Jahn

Send message
Joined: 20 Dec 07
Posts: 1069
Germany
Message 46038 - Posted: 18 Oct 2012, 15:34:40 UTC - in response to Message 46037.  

There is no cc_config.xml by default. Look for client_state.xml; with windows, the data directory is hidden.

The path to the BOINC data directory is also listed in the BOINC event log after a restart.

Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
ID: 46038 · Report as offensive
PGRID

Send message
Joined: 31 Jan 11
Posts: 20
Venezuela
Message 46048 - Posted: 19 Oct 2012, 13:19:06 UTC - in response to Message 46038.  

Greetings, thanks for your reply and found the file. xml you mention, ...

Try connecting machines that have private ip and I get an error -417 I have done many tests with machines that have public IPs and has given me no problems, the BOINC server does some preference as to the type of network you are are the machines?

Any idea how to work with a machine whose ip is 192 without me throw this kind of error?

Thanks
ID: 46048 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5082
United Kingdom
Message 46053 - Posted: 19 Oct 2012, 17:37:47 UTC - in response to Message 46048.  

Re-posting a reply I gave to a very similar question on the boinc_projects mailing list this afternoon:

IP addresses starting 192 are typically part of the private 192.168.0.0 IP address space which cannot be routed over the internet. See

http://en.wikipedia.org/wiki/IP_address#IPv4_private_addresses

Machines with addresses like this would only be able to contact a BOINC server if that server had a private IP address in the same address space, and were connected via a direct-wired private network, not routed over the public internet. The same would apply to attempts to contact any other kind of server - this is a networking restriction, not a BOINC restriction.

The commonest way round this problem - used almost without being noticed by the majority of home-based volunteers contributing to BOINC projects - is to connect a small NAT (Network Address Translation) router to the private network, and - using that as a 'gateway' - allow the private machines to connect to the public internet, and from there to the public IP address on the server. Of course, the same result can be achieved by using a private router, or gateway PC configured as a router, without allowing public internet access from the BOINC client machines.
ID: 46053 · Report as offensive

Message boards : Questions and problems : Folder data and error 417

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.