28
Remmina not working with Windows 10 RDP anymore
(gehirneimer.de)
submitted
10 months ago* (last edited 10 months ago)
by
BentiGorlich@gehirneimer.de
to
c/linux@lemmy.ml
Hi guys, Remmina won't connect to a windows 10 PC via RDP anymore. It worked until I upgraded to Fedora 39 (I think, maybe its something different though). I cannot see anything in the logs indicating what the error might be. I tried messing with the settings, particularly the TLS and Gateway ransport type settings, but that didn't change anything. It is not timing out eigher, the disconnect is nearly instant.
Logs
(DEBUG) - (rcw_map_event) - Mapping: RemminaConnectionWindow
(DEBUG) - (remmina_protocol_widget_map_event) - Calling plugin mapping function
(DEBUG) - (remmina_protocol_widget_open_connection_real) - Opening connection
(DEBUG) - (remmina_rdp_event_init) - Disable smooth scrolling is set to 1
(DEBUG) - (remmina_protocol_widget_open_connection_real) - Have SSH
(DEBUG) - (remmina_rdp_main) - RDP data path is /home/benni/.var/app/org.remmina.Remmina/data/remmina/RDP
(DEBUG) - (remmina_rdp_main) - Not using system proxy settings
(DEBUG) - (remmina_rdp_tunnel_init) - Tunnel init
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - SSH tunnel initialization…
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - Calling remmina_public_get_server_port
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - Calling remmina_public_get_server_port (tunnel)
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - server: 192.168.43.170, port: 3389
(DEBUG) - (remmina_rdp_tunnel_init) - protocol_plugin_start_direct_tunnel() returned [192.168.43.170]:3389
(DEBUG) - (remmina_rdp_tunnel_init) - Tunnel has been optionally initialized. Now connecting to 192.168.43.170:3389
(DEBUG) - (remmina_rdp_main) - gfx_h264_available: 1
(DEBUG) - (remmina_rdp_main) - Resolution set by the user: 588x620
(DEBUG) - (remmina_rdp_main) - Resolution set after workarounds: 644x620
(DEBUG) - (remmina_rdp_main) - proxy_type: (null)
(DEBUG) - (remmina_rdp_main) - proxy_username: (null)
(DEBUG) - (remmina_rdp_main) - proxy_password: (null)
(DEBUG) - (remmina_rdp_main) - proxy_hostname: (null)
(DEBUG) - (remmina_rdp_main) - proxy_port: 80
(DEBUG) - (remmina_rdp_main) - rdp_keyboard_remapping_list: (null)
(DEBUG) - (remmina_rdp_main) - Log level set to to INFO
(DEBUG) - (rco_on_disconnect) - Disconnect signal received on RemminaProtocolWidget
(DEBUG) - (remmina_file_save) - Saving profile
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_store_password) - Password “password” saved for file /home/benni/.var/app/org.remmina.Remmina/data/remmina/group_rdp_ps_192-168-43-170.remmina
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_delete_password) - password “ssh_tunnel_password” deleted for file /home/benni/.var/app/org.remmina.Remmina/data/remmina/group_rdp_ps_192-168-43-170.remmina
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_delete_password) - password “gateway_password” deleted for file /home/benni/.var/app/org.remmina.Remmina/data/remmina/group_rdp_ps_192-168-43-170.remmina
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_delete_password) - password “ssh_tunnel_passphrase” deleted for file /home/benni/.var/app/org.remmina.Remmina/data/remmina/group_rdp_ps_192-168-43-170.remmina
(DEBUG) - (remmina_file_save) - Profile saved
(DEBUG) - (remmina_file_save) - Connection profile states saved
(DEBUG) - (remmina_network_monitor_status) - G_NETWORK_CONNECTIVITY_FULL
(DEBUG) - (rco_on_disconnect) - Could not disconnect
I recently experienced this. I'm thinking it could be a lot of things, but when I logged into the device through the hypervisor I got a domain controller trust issue error. Can you login locally to the device and check for errors?
Also maybe try with a standard resolution? Although I wouldn't expect this to terminate the session it might be worth testing.
Will do later today
this sadly didn't work