Page 2 of 2

Re: Not a problem - I'm just curious

Posted: Tue Oct 21, 2025 3:16 pm
by muziqaz
Or local machine DNS setting

Re: Not a problem - I'm just curious - "solved"

Posted: Sat Oct 25, 2025 7:17 pm
by malkie
Well, not really solved - at least in the sense of an underlying problem being fixed.

I started using another old laptop running Win10, and was interested to notice that both Win10 machines could see the WU status for all three of my FAH machines. That is, they could see themselves, each other, and the Win11 machine. However, the Win11 machine could not see either of the others. At this point I was using a Chrome app window on all three machines.

I don't know what made me try this, but on the Win11 machine I created a Brave app window for FAH - with Brave shields down, of course. No other changes - just using a different browser. Wouldn't you know it - the Win11 machine can now see both Win10 machines.

Re: Not a problem - I'm just curious

Posted: Sat Oct 25, 2025 7:24 pm
by calxalot
Bears repeating that all system clocks need to be correct for clients to connect to node server. Possibly also the account server.

If you dual boot linux and windows, you might want to check your clock after rebooting.

Re: Not a problem - I'm just curious - "solved"

Posted: Sat Oct 25, 2025 7:45 pm
by muziqaz
malkie wrote: Sat Oct 25, 2025 7:17 pm Well, not really solved - at least in the sense of an underlying problem being fixed.

I started using another old laptop running Win10, and was interested to notice that both Win10 machines could see the WU status for all three of my FAH machines. That is, they could see themselves, each other, and the Win11 machine. However, the Win11 machine could not see either of the others. At this point I was using a Chrome app window on all three machines.

I don't know what made me try this, but on the Win11 machine I created a Brave app window for FAH - with Brave shields down, of course. No other changes - just using a different browser. Wouldn't you know it - the Win11 machine can now see both Win10 machines.
we had similar issues in early v8 development. What kick started for me was a separate MS Edge instance, while my default firefox was struggling

Re: Not a problem - I'm just curious - "solved"

Posted: Sat Oct 25, 2025 8:33 pm
by malkie
muziqaz wrote: Sat Oct 25, 2025 7:45 pm
malkie wrote: Sat Oct 25, 2025 7:17 pm Well, not really solved - at least in the sense of an underlying problem being fixed.

I started using another old laptop running Win10, and was interested to notice that both Win10 machines could see the WU status for all three of my FAH machines. That is, they could see themselves, each other, and the Win11 machine. However, the Win11 machine could not see either of the others. At this point I was using a Chrome app window on all three machines.

I don't know what made me try this, but on the Win11 machine I created a Brave app window for FAH - with Brave shields down, of course. No other changes - just using a different browser. Wouldn't you know it - the Win11 machine can now see both Win10 machines.
we had similar issues in early v8 development. What kick started for me was a separate MS Edge instance, while my default firefox was struggling
Unfortunately, from my other thread, I still need to manually pause and start folding every time after the Win11 machine completes a WU.

Re: Not a problem - I'm just curious - "solved"

Posted: Sat Oct 25, 2025 8:40 pm
by muziqaz
malkie wrote: Sat Oct 25, 2025 8:33 pm
muziqaz wrote: Sat Oct 25, 2025 7:45 pm
malkie wrote: Sat Oct 25, 2025 7:17 pm Well, not really solved - at least in the sense of an underlying problem being fixed.

I started using another old laptop running Win10, and was interested to notice that both Win10 machines could see the WU status for all three of my FAH machines. That is, they could see themselves, each other, and the Win11 machine. However, the Win11 machine could not see either of the others. At this point I was using a Chrome app window on all three machines.

I don't know what made me try this, but on the Win11 machine I created a Brave app window for FAH - with Brave shields down, of course. No other changes - just using a different browser. Wouldn't you know it - the Win11 machine can now see both Win10 machines.
we had similar issues in early v8 development. What kick started for me was a separate MS Edge instance, while my default firefox was struggling
Unfortunately, from my other thread, I still need to manually pause and start folding every time after the Win11 machine completes a WU.
time to switch to Linux ;)

Re: Not a problem - I'm just curious - "solved"

Posted: Sat Oct 25, 2025 8:47 pm
by malkie
muziqaz wrote: Sat Oct 25, 2025 8:40 pm
malkie wrote: Sat Oct 25, 2025 8:33 pm
muziqaz wrote: Sat Oct 25, 2025 7:45 pm

we had similar issues in early v8 development. What kick started for me was a separate MS Edge instance, while my default firefox was struggling
Unfortunately, from my other thread, I still need to manually pause and start folding every time after the Win11 machine completes a WU.
time to switch to Linux ;)
I have a USB stick with one of the recent Puppy distros. I should run it on one of the Win10 laptops. Otherwise, apart from an occasional weekend, they are both doing nothing except running FAH. One has an i5-4210U, and the other has an i5-5300U, so either should be good for a nice lite linux like puppy.