Hello,
This is debug output from a working connection specifying tls and a
non-working connection specifying any as the security type.
openssl is 1.1.1k.
// RDP security parameter set to tls
Jul 18 12:22:41 guac guacd[661242]: guacd[661242]: INFO:#011Creating new
client for protocol "rdp"
...
Jul
Hello,
I haven't seen any differences for this connection issue between epel repo
1.5.5 and compiled from source on the same system.
I've done some more testing on this issue and for RDP connection
parameters, if username and password are not specified and security is set
to blank or 'any' the co
On Fri, Jul 12, 2024 at 3:38 AM Patrick M wrote:
> An one my side: native install, in-place upgrade from 1.4.0 to 1.5.5
> Debian 11, FreeRDP 2.3.0.
>
>
Did you compile them yourself, or are they packages from a Debian repo? Are
you able to generate debug-level messages during a connection attempt
An one my side: native install, in-place upgrade from 1.4.0 to 1.5.5
Debian 11, FreeRDP 2.3.0.
PM.
Le ven. 12 juil. 2024 à 03:40, Stephen Young
a écrit :
>
> Native install.
> Rocky Linux release 8.10, FreeRDP version 2.2.0, guacd 1.5.5 and libguac
> installed from epel repo. Is there any other
Native install.Rocky Linux release 8.10, FreeRDP version 2.2.0, guacd 1.5.5 and libguac installed from epel repo. Is there any other information you would like?Thanks,S.On Jul 11, 2024, at 19:06, Nick Couchman wrote:On Thu, Jul 11, 2024 at 7:09 PM Stephen Young wrote
On Thu, Jul 11, 2024 at 7:09 PM Stephen Young
wrote:
> Hi,
>
> We are also seeing this exact connection issue after upgrading from 1.4.0
> to 1.5.5.
> So far we also have not been able to track down the cause. Debug logging
> from freerdp isn’t giving much helpful (to me) information. The securit
Hi,
We are also seeing this exact connection issue after upgrading from 1.4.0 to
1.5.5.
So far we also have not been able to track down the cause. Debug logging from
freerdp isn’t giving much helpful (to me) information. The security connection
mode is set to any, and ignore-cert is true.
S.
Thank you for your answer.
As the configuration is strictly the same on this server on 1.40 and
1.5.5, it seems that there is a difference regarding
RDP authentication behavior between these versions.
Looked at the release notes without seeing what parameters could have changed.
Still looking...
On Thu, Jul 11, 2024 at 6:06 AM Patrick M wrote:
> Hi,
>
> Following an upgrade 1.40 --> 1.5.5, I have 2 issues:
>
> - On RDP connections, I starting to have the following infamous error
> although this was working correctly before:
> RDP server closed/refused connection: Authentication failure (
Hi,
Following an upgrade 1.40 --> 1.5.5, I have 2 issues:
- On RDP connections, I starting to have the following infamous error
although this was working correctly before:
RDP server closed/refused connection: Authentication failure (invalid
credentials?)
In connection config, Security mode is s
10 matches
Mail list logo