RDP session handshake failing with some Windows computers
We have a few Windows computers which are unable to successfully complete handshake with RDP backend no matter what client is used while at the same time other Windows, Linux and OS-X computers work flawlessly.
All the computers that fail are in a Windows domain so we were hoping it's just some policy settings we can change but there are other computers in the same domain that work and the logs do not give much clue as to the reason why.
For comparison I've collected gnome-remote-desktop debug log output for connections from different clients running on one of the Windows computers which cannot connect and for connections from Windows and Linux computers that work. The logs are attached in a text file (debug-logs.txt) to keep this description readable.
All three clients are unable to complete handshake. Log output of MS store client seems to indicate an invalid password (although verified to be entered correctly), the other two fail because of SEC_E_INVALID_TOKEN roughly at the same stage of handshake. This behavior is to be the same between Fedora Silverblue 35-1.2 and Fedora Silverblue 36.20220312.n.0 for the server (the machine running gnome-remote-desktop).
It's surprising that even Windows build of FreeRDP client does not work. That seems to rule out all Windows policies being the cause because FreeRDP client should not be affected by those. What else could it be that can cause different RDP client implementations running on the same computer to fail the handshake?