I try make boinc- server as described here http://boinc.berkeley.edu/trac/wiki/VmServer but when I try to connect boinc manager to project, I can't connect. WWW of this project works. I try connect from windows and from UBNT but same result :-(

event log and config are below. Many thanks

event log from boinc-manager:
10/02/2013 12:42:58 | gplan | Sending scheduler request: To fetch work.
10/02/2013 12:42:58 | gplan | Requesting new tasks for CPU
10/02/2013 12:42:59 | gplan | Scheduler request failed: Couldn't resolve host name
10/02/2013 12:43:05 | | Project communication failed: attempting access to reference site
10/02/2013 12:43:06 | | Internet access OK - project servers may be temporarily down.

config.xml of the project:
<?xml version="1.0" ?>
<boinc>
<config>
<upload_dir>
/home/boincadm/projects/gplan/upload
</upload_dir>
<send_result_abort>
1
</send_result_abort>
<long_name>
gplan
</long_name>
<cgi_url>
http://192.168.0.12/gplan_cgi/
</cgi_url>
<sched_debug_level>
3
</sched_debug_level>
<upload_url>
http://192.168.0.12/gplan_cgi/file_upload_handler
</upload_url>
<disable_account_creation>
0
</disable_account_creation>
<uldl_dir_fanout>
1024
</uldl_dir_fanout>
<download_url>
http://192.168.0.12/gplan/download
</download_url>
<db_user>
boincadm
</db_user>
<log_dir>
/home/boincadm/projects/gplan/log_debian6
</log_dir>
<app_dir>
/home/boincadm/projects/gplan/apps
</app_dir>
<download_dir>
/home/boincadm/projects/gplan/download
</download_dir>
<fuh_debug_level>
3
</fuh_debug_level>
<master_url>
http://192.168.0.12/gplan/
</master_url>
<host>
debian6
</host>
<db_name>
gplan
</db_name>
<shmem_key>
0x11112d4c
</shmem_key>
<show_results>
1
</show_results>
<key_dir>
/home/boincadm/projects/gplan/keys/
</key_dir>
<dont_generate_upload_certificates>
1
</dont_generate_upload_certificates>
<ignore_upload_certificates>
1
</ignore_upload_certificates>
<db_passwd>





</db_passwd>
<min_sendwork_interval>
6
</min_sendwork_interval>
<db_host>





</db_host>
<daily_result_quota>
500
</daily_result_quota>
<one_result_per_user_per_wu>
0
</one_result_per_user_per_wu>
<max_wus_to_send>
50
</max_wus_to_send>
</config>
<tasks>
<task>
<cmd>
antique_file_deleter -d 2
</cmd>
<period>
24 hours
</period>
<disabled>
0
</disabled>
<output>
antique_file_deleter.out
</output>
</task>
<task>
<cmd>
db_dump -d 2 --dump_spec ../db_dump_spec.xml
</cmd>
<period>
24 hours
</period>
<disabled>
1
</disabled>
<output>
db_dump.out
</output>
</task>
<task>
<cmd>
run_in_ops ./update_uotd.php
</cmd>
<period>
1 days
</period>
<disabled>
1
</disabled>
<output>
update_uotd.out
</output>
</task>
<task>
<cmd>
run_in_ops ./update_forum_activities.php
</cmd>
<period>
1 hour
</period>
<disabled>
1
</disabled>
<output>
update_forum_activities.out
</output>
</task>
<task>
<cmd>
update_stats
</cmd>
<period>
1 days
</period>
<disabled>
0
</disabled>
<output>
update_stats.out
</output>
</task>
<task>
<cmd>
run_in_ops ./update_profile_pages.php
</cmd>
<period>
24 hours
</period>
<disabled>
1
</disabled>
<output>
update_profile_pages.out
</output>
</task>
<task>
<cmd>
run_in_ops ./team_import.php
</cmd>
<period>
24 hours
</period>
<disabled>
1
</disabled>
<output>
team_import.out
</output>
</task>
<task>
<cmd>
run_in_ops ./notify.php
</cmd>
<period>
24 hours
</period>
<disabled>
1
</disabled>
<output>
notify.out
</output>
</task>
</tasks>
<daemons>
<daemon>
<cmd>
feeder -d 3
</cmd>
</daemon>
<daemon>
<cmd>
transitioner -d 3
</cmd>
</daemon>
<daemon>
<cmd>
file_deleter -d 3
</cmd>
</daemon>
<daemon>
<cmd>
sample_work_generator -d 3
</cmd>
</daemon>
<daemon>
<cmd>
sample_bitwise_validator -d 3 --app example_app
</cmd>
</daemon>
<daemon>
<cmd>
sample_assimilator -d 3 --app example_app
</cmd>
</daemon>
</daemons>
</boinc>

You're trying to run the client on the same machine that the server runs on. I don't think that's possible. But not sure. So please, follow the advice in this thread.

---

192.168.0.12 is a private, non-routable IP address.

You don't say anything about two important factors:

1) Whether the Windows/UBNT clients are trying to contact your server by name (I guess so, because BOINC is trying to resolve a hostname in a url) or by IP address. What <scheduler_url> appears in the client_state.xml file of your clients?

2) Whether your test clients are on the same physical 192.168.0.xyz local subnet, or whether they are attempting to connect to the server over a wider intranet or even the public internet.

To address (1): if the clients are trying to contact the server by name, you will have to be using a local DNS server on the private network (which the client machines will have to use as their primary DNS server - use a forwarder to resolve external names outside the local scope).

To address (2): if you are expecting to allow access to the server beyond the local subnet, you will have to register a public url with the global DNS server network, and configure it to resolve to a public (routeable) IP address on your internet connection. Then, configure your peripheral firewall/router to forward BOINC traffic to your server's private IP address.

If you are working within an organisation that has a system administrator / network manager, consult them.

I trying run client on another PC, but same part of LAN network.

Many thanks,

problem solved. In client_state.xml was..
<scheduler_url>http://debian6.localdomain/gplan_cgi/cgi</scheduler_url>


thak you again :-)