Raymond Wooninck [23.08.2013 10:50]:
On Friday 23 August 2013 10:35:12 Werner Flamme wrote:
Raymond,
I did so and the only 2 lines I got are
QDBusObjectPath: invalid path "" krdc(24796)/kdeui (kdelibs): Attempt to use QAction "remote_desktop_dockwidget" with KXMLGUIFactory!
Werner, what about running just the xfreerdp <servername> ?? What does this deliver ? As indicated in my first reply, let's first test if the underlying technology is working.
Hi Raymond, i tried several times, and indeed xfreerdp seems to be the culprit: first attempt: ---snip--- $ xfreerdp paext connected to paext:3389 Password: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: CERTIFICATE NAME MISMATCH! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ The hostname used for this connection (paext) does not match the name given in the certificate: PAEXT.intranet.ufz.de A valid certificate for the wrong name should NOT be trusted! Certificate details: Subject: CN = PAEXT.intranet.ufz.de Issuer: CN = PAEXT.intranet.ufz.de Thumbprint: 51:65:01:22:7c:3d:0d:9f:5d:90:43:75:57:29:b0:0c:b8:20:e1 The above X.509 certificate could not be verified, possibly because you do not have the CA certificate in your certificate store, or the certificate has expired. Please look at the documentation on how to create local certificate store for a private CA. Do you trust the above certificate? (Y/N) Y SSL_read: Failure in SSL library (protocol error?) Authentication failure, check credentials. If credentials are valid, the NTLMSSP implementation may be to blame. ---pins--- second attempt, with FQDN: ---snip--- $ xfreerdp PAEXT.intranet.ufz.de connected to PAEXT.intranet.ufz.de:3389 Password: Certificate details: Subject: CN = PAEXT.intranet.ufz.de Issuer: CN = PAEXT.intranet.ufz.de Thumbprint: 51:65:01:22:7c:3d:0d:9f:5d:90:43:75:57:29:b0:0c:b8:20:e1 The above X.509 certificate could not be verified, possibly because you do not have the CA certificate in your certificate store, or the certificate has expired. Please look at the documentation on how to create local certificate store for a private CA. Do you trust the above certificate? (Y/N) Y SSL_read: Failure in SSL library (protocol error?) Authentication failure, check credentials. If credentials are valid, the NTLMSSP implementation may be to blame. ---pins--- third attempt, some more parameters, at least the certificate is known now: ---snip--- $ xfreerdp PAEXT.intranet.ufz.de -d INTRANET.ufz.de -u wflamme connected to PAEXT.intranet.ufz.de:3389 Password: SSL_read: Failure in SSL library (protocol error?) Authentication failure, check credentials. If credentials are valid, the NTLMSSP implementation may be to blame. ---pins--- And yes, I am sure I did not make a typo with my password ;-) The next tries I do not quote here. I tried "--ntlm 2", "--ntlm 1", "--sec rdp", "--no-nla", "--no-rdp", each in a new attempt. The output was always the same as on the third attempt. Regards, Werner -- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org