FAHControl cannot connect to other clients on same network

[aram535]

I'm running F@H client and control on my main desktop (Windows 10).

FAHControl connects and works fine connecting locally. However when I try to connect to a Linux FAHClient instance on the same network it cannot connect.

In the client-Add window I have: <hostname>,<ip address>,36330,no password.
From the desktop, I can connect to <ip address>:36330 via TELNET, (firewall and iptables have been checked, all connections are allowed on the 192.168.1.0/24 network.

Welcome to the FAHClient command server.
>

In FAHControl on desktop, when I click on the client it says: "Client: <hostname> Connecting inactive" (inactive is in orange)

Any ideas on why I cannot connect?

EDIT: Desktop (WIN10 version): 7.6.9, Linux (CentOS 8): fahclient-7.6.9-1.x86_64

[pachydermus]

Check your host config has all the necessary settings. When I did mine via the client it missed one of them and I wasted loads of time looking for connectivity issues before I gave up and started googling and found a post that showed what config should look like:


<!-- HTTP Server -->
<allow v='127.0.0.1,192.168.1.0/24'/>
<!-- Network -->
<proxy v=':8080'/>
<!-- Remote Command Server -->
<command-allow-no-pass v='127.0.0.1,192.168.1.0/24'/>
<password v='pass'/>
<!-- Slot Control -->
<power v='full'/>
<!-- User Information -->
<passkey v=your passkey/>
<user v=your name/>

<!-- Web Server -->
<web-allow v='127.0.0.1,192.168.1.0/24'/>

[Joe_H]

Also, the FAHClient process on each machine needs to be restarted after making any network configuration changes through FAHControl for them to take effect. Easiest way is through a reboot.

[aram535]

Code: Select all

<command-allow-no-pass v='127.0.0.1,192.168.1.0/24'/>

was the right config.xml entry.

[HaloJones]

not a fan of passwordless access. It's trivial to use the same network strings to allow access but also have a password set. It's just the section above the passwordless section of Advanced Control.

[aram535]

Overall I'd agree with you.
In this case, they're on an internally routed network and behind 2 firewalls.

[pachydermus]

not a fan of passwordless access.

if someone has managed to get into my network then I have a little more to worry about than them changing my FAH settings.