HFM.net not connecting

[robby659]

Hi,
I started folding sometime back in 2010, and since I got my Computer upgraded I decided to start folding again.
And since I've got the Client running on my

Main computer:
i7 3770
2x Geforce GTX 680

And my server:
Q9550
Geforce GTX 285

It would be great to get HFM working. But for some reason it won't connect to either of my clients.
Since my Server is running Ubuntu I assume there's a problem in the firewall. Anyway, I can't check that right now, since the machine is down for maintenance.
But HFM won't even connect to the local client on my Main computer.

Every time I setup the client and "Test Connection" nothing happens and in FAHControl the log outputs this:

Code: Select all

16:49:05:Started thread 91 on PID 4616
16:49:07:Started thread 92 on PID 4616

So I click on OK and all I get is this:
(can't post URLs yet) It shows "Slot: Unknown, Core: Unknown, ETA: 00:00:00" etc

Now if I go to: "Clients => View cached logfile " I can see the logfile, so a connection seems to be there, it's just not showing for some reason.

Can anybody here give me a hint?
And please excuse my bad english!

[davidcoton]

Welcome to the Forum.

If you are using the latest client (7.4.4), there is a known problem (in HFM) which prevents the connection working. We are waiting for a fix. See the thread under 3rd Party Contributed Software: viewtopic.php?f=14&t=9903&start=480

[P5-133XL]

HFM.net stopped working after v7.36. If you use an older version of the folding clientHFM.net will start working again but you'll add some client bugs.

[bruce]

There's another possilibity -- one which I have not yet found a solution.

On my home network, I have Ubuntu, Win7 and WIn8. My Linux only runs IPV4. When Win7 started supporting concurrent stacks for IPV6 and IPV4, I systematically disabled IPV6 since IPV4 within my LAN is (A) Familiar, (B) I understand it, and (C) IPV6 serves no purpose for me.

After I upgraded my router and started connecting WIN8 computers, I started having troubles. Now Wins/DHCP has started giving me IPV6 addresses for machines on which IPV6 has been disabled and pings time-out and remote V7 connections fail to connect even though those machines have IPV4 addresses. I'd expect the same thing from HFM.

[P5-133XL]

I had to explicitly disable IPV6 on my router too to get rid of IPV6 addresses on internal pings.