Client Port used, v 7.6.21 [FAHControl Remote Connect]

[BrianJB]

How can I tell what port a remote client is using to set up remote control from my main PC? I tried sticking with the default 36330, I have the proper client IP address, but the remote control on the main PC indicates only that it is "connecting" and the remote client is shown as inactive - but it is folding. I tried running netstat -tulpn on the client. The only indication I got was that the port 36330 was in LISTEN state, no PID or program name, I don't see the client app listed anywhere there, or if I just run netstat by itself. Thanks.

Main PC W10pro
Client Ubuntu 20.04

[Joe_H]

Have you restarted the FAHClient process after setting up the connection parameters such as password, etc.? That is necessary to get the client to do connections between the main FAHControl and remote clients.

Easiest way to restart FAHClient is through a reboot. Otherwise pause folding and stop and restart FAHClient.

[BrianJB]

Thanks for the reply. I did restart, even powered down both systems after the modifications. The control sees the client as inactive. The IP address is correct - I viewed it on the gateway and set both systems to static addresses. I tried with and without passwords. I'm obviously missing something. I'l keep looking.

[PantherX]

Welcome to the F@H Forum BrianJB

If you want, you can have a look at post "9 - Generic Troubleshooting Tips" in this thread (viewtopic.php?f=108&t=26036) which has the most common reasons to help you troubleshoot

[bruce]

Either you have to match the password on both systems (in Configure+Connection+ and in Configure+Clients+[select] or +Add) or you have to configure the client for passwordless connections from your LAN in Configure+Remote_Access+Passwordless+aLLOW. ... as 127.0.0.1,192.168.0.0/24 or whatever your LAN actually uses). (and restart after making changes.)

[BrianJB]

If I add a remote client to FAHcontrol on my main W10 PC and select "configure", I only have the connection tab, no others including the remote access tab.

[BrianJB]

I tried a mod of the config.xml on the client. Here are the lines I tried, not sure if they're correct or not, but I rebooted and still cannot connect.

<allow v="127.0.0.1 192.168.1.11"/>

<allow-no-pass v="192.168.1.11"/>

[bruce]

If I add a remote client to FAHcontrol on my main W10 PC and select "configure", I only have the connection tab, no others including the remote access tab.

The remote client, itself can be configured with a password set in the configure + Remote_access screen tab and if you do, it must match the password entered twice when you add that connection to the Clients list on the left side of the local machine's monitoring screen. Then both machines should be restarted.

if you want to make the connection without passwords, the allow and allow-no-pass settings can be used.

Since the data will only traverce your local network, these security features are not particularly important except that connections must be allowed.

[PantherX]

Since you have 192.168.1.11 in both lists, it might be confusing for the client. Maybe remove it from "allow" if you would like to have passwordless access to it and see what happens after a reboot.

[Joe_H]

Linus Tech Tips did a write up on how to configure for using FAHControl remotely here - https://linustechtips.com/topic/990176- ... ahcontrol/. Perhaps that will give you some ideas for things to check in the setup.

There have been some posts here on this as well, just don't have a link to a good one at the moment. Will modify your subject a bit so it might attract people more familiar with setup problems for remote monitoring and control of client using FAHControl.