This is my fourth F@H install this week on my network, and the second on Windows 10; three machines are happily crunching away (when there are WUs, anyway) but the fourth can't connect to the client on itself for some reason. I don't think the client is actually starting. Default install with config set up to use my ID, team, and passkey. It just sits at 'Connecting'.
Bumping for visibility. I've allowed FAHClient and FAHControl through the local Windows 10 firewall and still no dice. It's my only machine not folding!
Welcome to the forum and thanks for the bump. There are so many new threads it's hard for all us to keep up!
On the fourth computer, how did you install the software? How are you starting F@h? Is the setup any different from the other Windows machines?
F@h is now the top computing platform on the planet and nothing unites people like a dedicated fight against a common enemy. This virus affects all of us. Lets end it together.
Thanks, Jesse! I know the team has been swamped with new folders, and I'm no exception. I appreciate the reply.
I installed F@H 7.5.1 with the regular installer, Express mode, and selected to run after closing the installer. I also see FAHClient.exe running at startup, but that's it. The only difference between this and my other machines is that I installed it over Remote Desktop, instead of connected directly. The machine also runs Backblaze for my cloud backup needs.
Sure thing! Below are the contents of the log.txt file in my FAHClient folder in AppData, and a warning I found in Event Viewer. It doesn't look like it's even having an issue connecting to the internet, but that the client is never starting on port 36330 locally (or any port, when I search by PID using the output of netstat -ano).
Also worth noting there's no more or less security software on this desktop than any of the other four, and they're all on the same LAN.
C:\Program Files (x86)\FAHClient\FAHClient.exe
Exception: Failed to connect to 127.0.0.1:36330: No connection could be made because the target machine actively refused it.
I know how it's going to sound, but have you tried to reboot the machine?
The "not configured" issue already has been solved this way, here: viewtopic.php?f=61&t=33181&hilit=not+configured
EDIT: I read further that this error message can indicate out of date drivers. It should not happen in win10, but the automatic update is maybe deactivated?
Also, if you have automatic update on the video drivers you may want to turn it off while folding. The updates provided by MS through Windows Update usually do not include the OpenCL support, and may remove it when they install.
One way to keep ahead of MS and this is to have recent enough drivers installed from AMD or nVidia that Windows Update doesn't see them as needing any update.