Unable to add other clients to FAHControl

[FoldFoldFoldFold]

Hi folks, I'm tearing my hair out trying to solve a super simple task...I'm trying to add two other computers to my FAHControl so I can manage them from one system instead of circling around to them in the house.

I have port 36330 open on both TCP inbound/outbound on the Windows Firewall on all 3 systems. I can ping them by their DNS name and IP, and I have the same password set on all of them. However, FAHControl still cannot find them, it just sits at "connecting." I've tried restarting FAHClient on them but to no avail.

What am I missing here?

[Jesse_V]

Hi and welcome to the forum!

You may want to check whether your LAN subnet is whitelisted by those remote FAHClient instances. Under their FAHControl, go to Configure, then click the Remote Access tab. Put your LAN's subnet in second-to-last section called "IP Address Restriction". It should look like:

Allow: 127.0.0.1 192.168.0.0/16

Then restart the remote FAHClient instances, close FAHControl on your main machine, reopen it, and it should connect.

[PantherX]

Welcome to the F@H Forum FoldFoldFoldFold,

You need to modify the configuration via FAHControl on the 2 remote systems allowing your monitor system to connect to it.

Remote System
Open up FAHControl (Advanced Control)
Click Configure
Click Remote Access tab
Enter Password
Enter either the monitor system's IP or the IP Address range in the Allow field
Click Save
Restart the remote system

Monitor system
Open up FAHControl (Advanced Control)
Click Add
Under Name, enter the Remote system's name
Under the Address, enter either the Hostname or IP address of the Remote system
Under the password, enter the password used in the remote system.

[SeanPearce44]

I've also found that in Windows 10 you need to ensure the "Network Profile" is "Private" (Work or Home) not "Public" (as it defaults to for Wifi) on the destination machines, otherwise he connections are still blocked, despite being allowed in the Windows FW. Took me a while to suss that out - based on a machine which worked, and one which didn't!

[FoldFoldFoldFold]

Thanks, I figured it out after a bit of troubleshooting:

-Yeah there is a stupid setting in Windows 10 that designates a network as "Public" or "Private," and bafflingly, my computers were set to the more restricted "Public" one. I fixed this
-I didn't realize there were additional settings in the "remote access" section (scrolling down, lovely invention FoldFoldFoldFold...), once I set the IP ranges and passwords, that also worked out.

We can call this one closed, thanks!