Heya, I have several Computers in my network and I used to remote control them in the past via Krdc and Krfb. And with in the past I mean “before I switched from green to purple”. I just was tasked to perform some installations on the daughters computer and installed krfb on her side and krdc on mine. But krdc just closes the connection after a second or so. Any idea how to debug, what to check and so on?
Did you try connecting by IP?
start krdc in terminal/konsole and check the written output when you try to connect.
Most likely it is some signature or key mismatch that krdc unfortunately does not handle well.
IP, hostname, FQDN, all three variants with both protocols (vnc, rdp). ping is working for IP, hostname and FQDN.
This is what I tried first - Konsole just says nothing. like nothing in nada, niente, empty.
check journalctl -p 3 -xb and dmesg for possible errors or hints.
You can also try to connect with freerdp in konsole - can’t help you with the correct syntax right now though.
both log thingys gace absolute no clue what’s wrong here. So I tried a different approach: Started krdc via sudo in a konsole, and now I get some (useful) output:
sudo krdc
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Couldn't start kwalletd: QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
Couldn't start kwalletd: QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
Couldn't start kwalletd: QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
Couldn't start kwalletd: QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
Couldn't start kwalletd: QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
Couldn't start kwalletd: QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
So I activated kwalletd, but no change in behaviour.
that output is expected because root is not configured to launch anything graphical and also kwallet is not possible as root - that’s why you only see it when running it with sudo.
I asumed something like this - any more ideas what to check, were to look? I don’t want to use teamviewer or something similar for this…
only trying to connect using xfreerdp /u:USERNAME /v:TARGET /w:WIDTHPIXELS /h:HEIGHTPIXELS and check if that produces some meaningful output.
well, at least I have some information now:
xfreerdp /u:username /p:password /v:10.10.70.86:5900 /w:800 /h:600
[10:08:39:187] [19100:19102] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 104: Connection reset by peer
[10:08:39:187] [19100:19102] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
[10:08:39:203] [19100:19102] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 104: Connection reset by peer
[10:08:39:203] [19100:19102] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
[10:08:39:203] [19100:19102] [ERROR][com.freerdp.core] - freerdp_post_connect failed
Looks like a network/firewall issue. Will try to analyse this further by getting the computer out of the restricted network it is currently in and putting it into the not restricted one, but I don’t think that this is the issue here, because I did not change my network setup since the last time it has worked…
Now I am getting confused. I have a VM for testing relevant changes to my system, just fired this up and on this one it is working like a charm, so the issue must be with my main system. Definately no network issue, because the VM usees the same network (as in “bridged network” inside vbox)…