Unable to add Windows FAHClients remote into FAHControl?

[bumbel123]

Hi,

I did setup several machines with FAH, Ubuntu & Windows 10, for a team. I mainly work with a Windows Desktop and want to control all machines with FAHControl on that. I can add Ubuntu based FAH services with ease and also control them perfectly.

But I cannot add the Windows based machines. If I add them to FAHControl, they stick in status "Connecting". It is even impossible to add my local Windows Desktop using it's normal IP address, just with 127.0.0.1 does work with FAHControl

On all clients I allowed my subnet for remote access and one specific IP for password less access. Since all Ubuntu machines can be added and controlled, settings should be fine.

No issues with network connection, RDP access does work, network backup and restore also. Windows firewall on each client does allow all incoming and outcoming port, UDP && TCP, on my local subnet. That has been done while installing that FAHClient software.

There's also no difference if I install FAHClient as windows service or as autorun application on user logon.

What's the secret for the Windows FAHClient to be remote accessed?

Cheers

[bumbel123]

Hmm, it did work on 2 of the WINDOWS clients after 1 resp. 2 reboots, strange behavior ....

[Joe_H]

After adding the settings and if used a password to allow this, the FAHClient process needs to be restarted on each system. Your reboot accomplished that on the 2 clients. On Windows you should be able to restart FAHClient by pausing folding, and then just stopping and restarting the background FAHClient process. I am not a Windows user, hopefully one familiar with doing this will come along with directions for avoiding a reboot.

[bumbel123]

Well, no password access, allowed for exact one IP adress ... since Windows 10 reboot rates decreased dramatically. This FAHClient behaviour is the first real issue since a very long time.