No remote on one machine

[HandOverFist]

I have one machine out of six that refuses to show up in remote access. I can see it grayed out, but it never comes alive (says disconnected). V8 5.5 on all machines using Windows 11. That particular machine also refuses to highlight the other running machines which are grayed out and says disconnected. I have refreshed several times as well as reinstalled V8 5.5 and the OS. Yes, all are linked to the same account. None of the completed WU's appear to be crediting to my account on that particular machine.

[muziqaz]

Yep, known issue

[HandOverFist]

So, 8 hours of Folding for nothing? Pretty expensive issue...

[muziqaz]

So, 8 hours of Folding for nothing? Pretty expensive issue...

No, your machine is connected, you just cannot see it from remote location

[HandOverFist]

8 hours of Folding on that machine is not credited to my account. Two 4080's running full tilt for 8 hours is some substantial ppd...

[muziqaz]

8 hours of Folding on that machine is not credited to my account. Two 4080's running full tilt for 8 hours is some substantial ppd...

Is that machine connected to internet and have those WUs been sent back to the server?
If yea, then you don't need to worry about it. Points will come to you

[HandOverFist]

Lol...now it downloads the first WU and just sits there and never starts. There is no winning today I suppose. The machine starts/runs BOINC with ease.

Not being able to see what the remote machines are doing is a real ball breaker. I could go a day or longer without realizing there is a problem with one or more of them. Is there some fix in the works to address this problem? Would it be worthwhile to go back to V4.9 and give it a try?

[muziqaz]

Lol...now it downloads the first WU and just sits there and never starts. There is no winning today I suppose. The machine starts/runs BOINC with ease.

Not being able to see what the remote machines are doing is a real ball breaker. I could go a day or longer without realizing there is a problem with one or more of them. Is there some fix in the works to address this problem? Would it be worthwhile to go back to V4.9 and give it a try?

No, older version will not fix your issue.
If the WU is sitting idle doing nothing, I would suggest looking into why it is doing that. Remote monitoring will not solve that.

[HandOverFist]

Just discovered the problem...time was not synced. Date was correct, but time was off by two hours. Might help someone down the road.

Still one fluke remaining...unable to pause that particular machine remotely or directly. Edit: Appears the fluke was related to the time change...responding normally now after it finished the ongoing WU's.