Cant connect to host with Asus transformer

[GoogleCodeExporter]

What steps will reproduce the problem?

I have an Boinc host running (my pc) on 10.0.0.150. My Router (draytek Vigor 
2920) is on 10.0.0.138. My Accesspoint is only configured as hotspot on 
10.0.0.160. It has no security. My Asus Transformer has 10.0.0.160. 

I installed Androboinc on my tablet and added an host into androboinc with the 
following information:

Name: Blablabla_not_important
IP: 10.0.0.150
password: onlymeknow

What is the expected output? What do you see instead?
It tries connecting to my host. Nothing more, nothing less. No message's that 
it cant connect. Just "connecting" until the rotating connecting thingy 
disapears.

What version of the product are you using?
Boinc Manager 6.12.34 (service mode)
Your latest AndroBOINC 6.10.17.beta3

What is the vendor/model of the device? What is the Android version?

Asus Transformer with Android Honeycomb 3.2

Please provide any additional information below.

None.

Original issue reported on code.google.com by Oxi...@gmail.com on 27 Sep 2011 at 8:08

[GoogleCodeExporter]

Correction: My Asus transformer has ip 10.0.0.163.

Original comment by Oxi...@gmail.com on 27 Sep 2011 at 8:09

[GoogleCodeExporter]

There are no other securities online at my computer. It should work as supposed 
to be. If i use an Boinc Client on my big pc (10.0.0.150) and i connect to 
10.0.0.150, it works ok.

Somehow Androboinc cant connect to my pc. I dont need to open ports if i use 
this on local network only. If i want to check/control my boinc stats somewhere 
else then my home, yes then i need to open ports. 

So i dont know how to fix this. I am missing something?

Original comment by Oxi...@gmail.com on 27 Sep 2011 at 8:13

[GoogleCodeExporter]

25-9-2011 22:08:27 |  | Starting BOINC client version 6.12.34 for windows_x86_64
25-9-2011 22:08:27 |  | Config: GUI RPC allowed from any host
25-9-2011 22:08:27 |  | Config: GUI RPC allowed from:
25-9-2011 22:08:27 |  | Config:   10.0.0.150

Original comment by Oxi...@gmail.com on 27 Sep 2011 at 8:19

[GoogleCodeExporter]

Please try to do following checks:

1. Check firewall in your system and make sure that BOINC port (31416 by 
default) is accessible from network (e.g. accessible from 
10.0.0.0/255.255.255.0 if you want to connect from your home network only)

2. If possible, try to connect with standard BOINC manager from some other 
machine (via network, not from the same machine), e.g. from some notebook via 
WiFi.
If you do not have notebook available, but you are technically skilled, you can 
alternatively use terminal emulator (Android application); Use "telnet 
10.0.0.150 31416" - and hit enter few times, to see whether you can make raw 
connection from your Android device (you should see some <boinc_gui_rpc_reply> 
if you can connect successfully) 

3. Please make sure your password is correct (or temporarily disable password 
on client and AndroBOINC).

4. If all above seems fine, then you can also try to debug GUI-RPC. In 
cc_config.xml turn on log flag <gui_rpc_debug> (see more details in 
http://boinc.berkeley.edu/wiki/Client_configuration) and check content of 
stdoutdae.txt (to avoid flooding of logs, please exit BOINC manager on the 
desktop machine, so you do not see there GUI-RPC from your desktop BOINC 
manager). 
If you do not see any GUI-RPC activity in log, then something (like firewall) 
is blocking the connection to your BOINC-client... And if you see some GUI-RPC 
activity from AndroBOINC, then log can give some hints about connection failure 
(e.g. which stage of connection failed).

Original comment by pavol.michalec@gmail.com on 28 Sep 2011 at 1:19

• Changed state: Queried

[GoogleCodeExporter]

Ok i found the problem. 

My standard Microsucks Firewall is the problem. If i disable it, i can connect 
with my tablet. Do you know which boinc executables i need to make an entry 
for? Only boincmgr.exe doesnt work. Hope to hear from you soon.

Original comment by Oxi...@gmail.com on 28 Sep 2011 at 4:21

[GoogleCodeExporter]

Making an entry for Boinc.exe and boincmgr.ext did the trick. Thanks for you 
help anyway. Working now!

Original comment by Oxi...@gmail.com on 28 Sep 2011 at 4:26

[GoogleCodeExporter]

The boinc.exe is BOINC-client and only this one needs incoming connections.

Original comment by pavol.michalec@gmail.com on 28 Sep 2011 at 4:54

• Changed state: Done
• Added labels: Type-Other
• Removed labels: Type-Defect