akallabeth

reverted with https://github.com/FreeRDP/FreeRDP/pull/11458 this was just an exchange of one warning for another.

@anhcuongdev please read https://github.com/FreeRDP/FreeRDP/wiki/BugReporting again. there is no indication of what you are actually using (the screenshot is `mstsc`?) just `FreeRDP` is too vague (there are clients/server/proxy/helper binaries in this...

@anhcuongdev does this also happen with current stable releases? we´ve rewritten most of proxy with 3.0

also, can you share your proxy configuration? (hard to guess what you do without some hints)

There is already the freerdp shadow server. It mirrors the session of the user it is started from.

@hardening correct, the links are for client side shadowing. the rpc mechanisms are a bit of overkill for freerdp (think dependencies on samba and others must be deployed/configured ...) but...

[[MS-TSTS]](https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-tsts/1eb45af1-94f1-4c42-9e13-dd0a018646fd) is a starting point, but be aware it references quite a bunch of others.

@cocoon `NLA` is currently not supported out of the box with the proxy (at least for the `client -> proxy` part) I agree that there should be an automatic fail...

@cocoon no. the reason is that `NLA` does not send the password in plain text to the server, so you don´t have a password to use on the other end....

@cocoon because the `NLA` fails and it falls back to `TLS`? see `[13:30:58:966] [840145:000cd1d2] [ERROR][com.freerdp.core.transport] - [transport_accept_nla]: client authentication failure` but you´re right, hard to tell from the log, that...