Folding Forum

EDIT: Remote for me is from my desk to my warehouse, not through the firewall. Just LAN.

I'm trying to find README or tutorial info on v7 remote monitoring setup, either native or HFM.NET

I froze the IP addy's of my folding stuff, added passwords, gave IP ranges, loaded HFM.NET, etc, and can't get any machine to see any other machine on a working network behind the firewall. Everything folding is 192.168.0.x.

I searched the HFM site and the Stanford site (and this one) for some kind of step by step to remote monitor.

Any links would be appreciated. It must be something simple that I'm not grasping. I can't see any version of 7.x, any version of Win, or any version of Linux, no matter what I set up to.

Have you seen https://fah-web.stanford.edu/projects/F ... oteClients?

Thanks! No, I was looking at the Install Guide I guess. Let me try that!

I surrender. . I followed the instructions as I understood them, and nothing changes.

I will have to setup up a dummy network this weekend with a couple of notebooks and experiment.

I didn't have any luck a couple of years ago either.

I can PING the machines, and I can "see" their public files, but can't remote monitor. Frozen at "Connecting" from the local (terminal) machine.

The most important hint I can give you is that when dealing with remote monitoring, all the clients need to be shut down (There needs to be nothing FAH* in the task manager) and restarted with virtually every change in the config. I started out modifying two clients and then I shut them both down and didn't go to my third till both of those worked. Then I added one more client and changed that config and then shut down all three clients. Then with the 4th I had to shut down four clients ...

Also, make it work without a password on all your machines before adding a password to them all. The password adds one more complexity that can cause it to fail making diagnostics harder. Don't forget that after making the password change in the config, all FAHclients need to be restarted again just like above.

Be methodical.

You only need to restart the client who's Remote Access config you're changing.
I recommend using an explicit simple password, the same on all machines on the LAN.
The passkey is supposed to be the default password if you don't set one, but I've never tested that.
I do not recommend altering the "Passwordless IP Address Restriction".

After restarting a client, you'll probably need to relaunch FAHControl for it to successfully connect to that client.

My method may be overkill but it worked for me...

can you telnet to the control port of the remote folding machines from your desktop?

telnet 192.168.x.x 36330
Welcome to the Folding@home Client command server.
>

calxalot wrote:You only need to restart the client who's Remote Access config you're changing.

There's a ticket on this: https://fah-web.stanford.edu/projects/F ... ticket/795

P5-133XL wrote:My method may be overkill but it worked for me...

Overkill is good.

I ended up getting the console machine to read one client machine!

Uh, then the client machine went primate-feces.

It could no longer sees itself at 127.0.0.1, so it proceeded to guess at which port to use to talk to itself, each port being a WARNING line in the log. The computer equivalent of running around your house looking for your car keys, with your car keys in your hand. You don't find them, because you already have them.

I'll try again after dinner.

It does bring back fond memories of the early Windows "Plug-and-Pray".

Where's those stupid IRQ jumpers when you need them!

EDIT: Whatever I did to that machine was lethal. You cannot reconfig via FAHControl. Infinite loop. Probably have to burn the WU, and do a fresh reinstall.

Yup, edited the config file, no dice. Reinstall in the AM.

...

Yeah, I got frustrated. It's something simple.

After my daughter's game, I'll go back and set up a couple test computers and try again.

HFM.net really works better as a monitoring platform.

The only real benefit of setting up remote monitoring using the v7 client is only that you can remotely change configs and pause/unpause.

Qinsp wrote:It does bring back fond memories of the early Windows "Plug-and-Pray".

Where's those stupid IRQ jumpers when you need them!

EDIT: Whatever I did to that machine was lethal. You cannot reconfig via FAHControl. Infinite loop. Probably have to burn the WU, and do a fresh reinstall.

Yup, edited the config file, no dice. Reinstall in the AM.

Are you always starting the FAH programs with the current directory set to the location of the data files or are you starting it in various places? When FAHControl cannot edit the config, can you verify that ONE COPY of FAHClient has been started in that data directory with read/write access to the files?