Remote Access not working properly

[Jertzuu]

It sounds like a firewall or some other problem on PC2. To be sure, you can try the same from another PC/laptop (on the network). If you have the same error, the problem IS on PC2.

EDIT: You can ascertain that the problem doesn't come from a bad command by typing (on PC1 or any PC that is running FAH):

Code: Select all

telnet
open 127.0.0.1 36330

You should have a connection (message "Welcome to...") with the FAHClient of the PC you are then using.

It could be doing with the firewall on PC2, since it has McAfee. I know for sure that my PC should be able to establish the connection.

Are one/both bits of kit windows? … If either/both are connected to your home network as if it is a public network (I do this a home with my "work" kit) then you may find that changing those connections to the on a private network settings (which allows much more sharing between devices on the network) helps.

Obviously ask permission before you do this to your Dad's kit … and there are more technical ways to resolve this specific issue (if this is what is causing it) that doesn't involved a blanket change of networking level - but I'll let one of the more technical folders talk you through those.

Yes, both systems are running Windows 10 Pro. My dad is fine with the fact that I tinker around with the systems, bu he is as stunned as me as to why the 2 systems won't cooperate with each other

[ajm]

In McAfee All Access, chose PC Security, then Firewall.
You can choose to monitor the blocks (Firewall history) to see if McAfee is preventing the connection, or directly open a port for FAHControl (Ports and System Services -> Add).
For the latter, there are instructions here: https://service.mcafee.com/webcenter/po ... oz6k20_228

You also can just turn the firewall off for a moment and see if it then works.

[HaloJones]

We need to see the config.xml of PC2. it will be in the %APPDATA%\FAHClient directory.

If you can post it on here (but do not include the passkey)?

[Jertzuu]

In McAfee All Access, chose PC Security, then Firewall.
You can choose to monitor the blocks (Firewall history) to see if McAfee is preventing the connection, or directly open a port for FAHControl (Ports and System Services -> Add).
For the latter, there are instructions here: https://service.mcafee.com/webcenter/po ... oz6k20_228

You also can just turn the firewall off for a moment and see if it then works.

We need to see the config.xml of PC2. it will be in the %APPDATA%\FAHClient directory.

If you can post it on here (but do not include the passkey)?

Thanks for the tips, I'll look into it tomorrow

[ajm]

Just a note re McAfee: a standard installation of the complete McAfee package doesn't prevent FAH's Remote Access. I have it on my Windows folding PCs and don't have any such issue.

[Jertzuu]

We need to see the config.xml of PC2. it will be in the %APPDATA%\FAHClient directory.

If you can post it on here (but do not include the passkey)?

Code: Select all

<?xml version="1.0"?>

-<config>

<!-- Folding Core -->


<checkpoint v="5"/>

<core-priority v="low"/>

<!-- Network -->


<proxy v=":8080"/>

<!-- Slot Control -->


<power v="full"/>

<!-- User Information -->


<passkey v="***************************"/>

<team v="237394"/>

<user v="Jertzuu"/>

<!-- Folding Slots -->



-<slot type="CPU" id="1">

<cpus v="9"/>

</slot>

<slot type="GPU" id="0"/>

</config>

This is what it gives me. Same as on my PC1.

I tried pinging PC2 on PC1, got response, but when I tried pinging PC1 on PC2, got no reponse

[ajm]

That's weird. If PC2 was configured for remote access, the config.xml would also contain the following:

Code: Select all

<!-- HTTP Server -->
<allow v="127.0.0.1 <IP of PC1>"/>
<!-- Network -->
<proxy v=":8080"/>
<!-- Remote Command Server -->
<command-allow-no-pass v="127.0.0.1 <IP of PC1>"/>

[HaloJones]

I'm going to assume all your machines are on the same local network where all the IP addresses begin 192.168.0

Sitting at PC2, open FAH Advanced Control. Select local from the list of Clients. Then select Configure. Then select Remote Access. Scroll down to the bottom two boxes on the page under Passwordless IP Address Restriction. In the Allow box, put "192.168.0.0/24" without the quotation marks.

Then select Save.

On PC2 now look at the config.xml. Post what it looks like after doing that please.

[ajm]

According to viewtopic.php?f=16&t=34864#p330630 PC2 has IP 192.168.1.163

EDIT: also look up viewtopic.php?f=16&t=34864#p330419

[HaloJones]

According to viewtopic.php?f=16&t=34864#p330630 PC2 has IP 192.168.1.163

EDIT: also look up viewtopic.php?f=16&t=34864#p330419

I realise that but it's not in his config.xml so it can't have worked.

[Jertzuu]

According to viewtopic.php?f=16&t=34864#p330630 PC2 has IP 192.168.1.163

EDIT: also look up viewtopic.php?f=16&t=34864#p330419

I realise that but it's not in his config.xml so it can't have worked.

Somehow it didn't save when I changed it. Still no response though I changed it and rebooted PC2. PC2 has "127.0.0.1 192.168.1.0/24" on both passwordless and passworded restriction.

Edit: now it is connected, but when I'm trying to view PC2 on PC1 FAHControl it doesn't show the slots, sysinfo or log. And when changing back to PC1 all of them dissappear too. This has been my main problem from the beginning. Reinstalled the client on both systems and I still get the same bug

[HaloJones]

Stumped sorry. I've never seen a problem within Advanced Control once the network connection is working. Or then with HFM.net.

[ajm]

Well, with 127.0.0.1 192.168.1.0/24 it very probably is not going to work anyway, as the present network uses numbers higher than 24 (192.168.1.163 for PC2, for example).
I would replace 192.168.1.0/24 with the effective IP of PC1. It also is safer this way: only one PC on the network can access FAHControl remotely.
And then reboot PC2.

[HaloJones]

192.168.0.1/24 means every address from .1 to .255

the /24 is a network mask

[ajm]

Ah, indeed, sorry.
I still would want to see the config.xml of PC2, though. We already were at that point a few days back and we have seen today that the change was actually not made.