Page 1 of 1

FAHControl and remote clients

Posted: Sun Jul 01, 2012 6:54 pm
by csvanefalk
I am having problems connecting to a remote client on my home network. FAHControl runs on my laptop (running Fedora 17), and the client runs on my desktop (also running Fedora 17). Firewall is configured to allow connections to port 36330.

The error I get is: [Errno 113] No route to host

What could be wrong here? I have no problem pinging or ssh:ing into the desktop from my laptop, so I am not entirely sure what to make of it.

Re: FAHControl and remote clients

Posted: Sun Jul 01, 2012 8:38 pm
by bruce
"No route to host" sounds like a networking issue.

First, be sure V7 has been restarted since the last change to the settings on the Connection tab or the Remote Access tab.

Second, confirm you can contact the laptop from the desktop machine. Using the Hostname or IP (xxx) shown in the Address segment of the Client panel, try ping and if that works, move to [/b]telnet[/b] or [/b]ssh and see if you can establish contact to that host on that port.

(The laptop's hostname might not be known to the desktop).

If those work but FAH still does not, it's FAH's password and/or other FAH restrictions in the Connection tab associated with the Clients entry or the security settings on the Remote Access tab.

Re: FAHControl and remote clients

Posted: Sun Jul 01, 2012 9:00 pm
by csvanefalk
Thanks Bruce, the issue has been resolved - I poked around and realized I had messed up my firewall configuration. After setting up remote access on the client as well, things are working great now.

Re: FAHControl and remote clients

Posted: Sun Jul 01, 2012 10:22 pm
by Ivoshiee
It may be a networking issue this time, but I tend to get some strange not connecting issues with the FAHControl what can not be explained by networking. There are times when FAHControl is showing the remote client as running, but attempt to download a log from it will fail. The FAHControl keeps on reading it but nothing will show up. At the same time I can SSH into the box and I see the FAHClient and cores running. It is hard to say what it is wrong here because usually some time later it will be able to load it just fine.