vel@lists.sourceforge.net> wrote:
> It seems that the problem is not stable. Now, after successfully
> connecting with the old version, the new version is also connected, the
> problem is not reproduced. :-/
> If (when) the situation comes back, I'll try -sec:rdp.
>
> 12.01.23 09:06, Eric
gt; [08:54:48:136] [7620:029ceb60]
> [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual
> Channel ainput
> [08:54:50:634] [7620:0626f720] [INFO][com.freerdp.channels.rdpdr.client]
> - registered [drive] device #1: dnl (type=8 id=1)
>
>
> 12.01.23 08:35, E
If you can install and run the previous version of the client that worked
and capture the log from a successful connection, it will tell a lot (and
also verify that it isn't something that changed on the server).
I don't know enough about the current state of FreeRDP to know offhand if
something
Joan,
Hi, are you using the FreeRDP code base to do your parsing?
Since you say you can detect the CR PDU "more usually" instead of every
time, it sounds quite possible that you are parsing the PDU (or protocol in
general) incorrectly, perhaps getting lost somewhere else in the stream.
Some
This might be a useful thread for you:
https://sourceforge.net/p/freerdp/mailman/freerdp-devel/thread/CAAD4mYgNe2NvYA2ua8wBJrCrbTsWdcEFky0ZmeigBZvLtWmY2A%40mail.gmail.com/#msg36379264
On Wed, Sep 26, 2018 at 4:18 AM R0b0t1 via FreeRDP-devel <
freerdp-devel@lists.sourceforge.net> wrote:
> On
I would bring this up in the Windows Protocol Forums (
https://social.msdn.microsoft.com/Forums/en-US/home?forum=os_windowsprotocols),
or email to doch...@microsoft.com. They actively monitor for RDP issues
Does this happen only with valid credentials? If not then it would be a
more serious DoS
