You are not logged in.

#1 2018-08-14 15:39:20

uhoso
Member
From: Soest, NRW, Germany
Registered: 2014-04-24
Posts: 30

remmina can not connect since update to freerdp-1:2.0.0_rc3-1

Since latest update to freerdp-1:2.0.0_rc3-1 remmina can't connect to rdpserver. Downgrading to freerdp-1:2.0.0_rc2-2 solves the problem.

Offline

#2 2018-08-14 18:38:47

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: remmina can not connect since update to freerdp-1:2.0.0_rc3-1

Do you see any error messages?

Offline

#3 2018-08-14 19:17:28

uhoso
Member
From: Soest, NRW, Germany
Registered: 2014-04-24
Posts: 30

Re: remmina can not connect since update to freerdp-1:2.0.0_rc3-1

launching remmina from console I get this error messages:

[
...
21:12:27:478] [21947:21950] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_DNS_NAME_NOT_FOUND [0x00020005]
[21:12:27:478] [21947:21950] [ERROR][com.freerdp.core] - getaddrinfo: Der Name oder der Dienst ist nicht bekannt
[21:12:30:537] [21947:21950] [INFO][com.freerdp.core.nego] - Detecting if host can be reached locally. - This might take some time.
[21:12:30:537] [21947:21950] [INFO][com.freerdp.core.nego] - To disable auto detection use /gateway-usage-method:direct
[21:12:30:543] [21947:21950] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Datenübergabe unterbrochen (broken pipe)
[21:12:30:543] [21947:21950] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[21:12:30:543] [21947:21950] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C]
[21:12:30:543] [21947:21950] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure
[21:12:30:543] [21947:21950] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 32: Datenübergabe unterbrochen (broken pipe)
Gtk-Message: 21:12:30.930: GtkDialog mapped without a transient parent. This is discouraged.

Offline

#4 2018-08-15 13:29:48

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: remmina can not connect since update to freerdp-1:2.0.0_rc3-1

Are you connecting through a hostname or an IP? If it's the former, can you try to connect with an IP?

Also, please use LC_ALL=C while launching remmina, so that all the output is in english:

https://wiki.archlinux.org/index.php/Co … s_and_code

Offline

#5 2018-08-15 16:11:11

uhoso
Member
From: Soest, NRW, Germany
Registered: 2014-04-24
Posts: 30

Re: remmina can not connect since update to freerdp-1:2.0.0_rc3-1

Sorry,

I'm usually connecting through a hostname. Trying it through IP I get following message:

[uli@uli ~]$ sudo LC_ALL=C remmina -c /home/uli/.local/share/remmina/1511697929196.remmina 
Failed to load plugin: /usr/lib/remmina/plugins/remmina-plugin-vnc.so.
Error: libvncclient.so.1: cannot open shared object file: No such file or directory
Failed to load plugin: /usr/lib/remmina/plugins/remmina-plugin-spice.so.
Error: libspice-client-gtk-3.0.so.5: cannot open shared object file: No such file or directory
StatusNotifier/Appindicator support: not supported by desktop. Remmina will try to fallback to GtkStatusIcon/xembed
WARNING: Remmina is running with a secret plugin, but it cannot connect to a secret service.
Gtk-Message: 18:03:09.067: GtkDialog mapped without a transient parent. This is discouraged.
[18:03:09:155] [4775:4779] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr
[18:03:09:155] [4775:4779] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd
[18:03:09:155] [4775:4779] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[18:03:09:156] [4775:4779] [INFO][com.freerdp.client.common.cmdline] - loading channelEx drdynvc
[18:03:09:162] [4775:4779] [INFO][com.freerdp.core.nego] - Detecting if host can be reached locally. - This might take some time.
[18:03:09:162] [4775:4779] [INFO][com.freerdp.core.nego] - To disable auto detection use /gateway-usage-method:direct
[18:03:09:178] [4775:4779] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_DNS_NAME_NOT_FOUND [0x00020005]
[18:03:09:178] [4775:4779] [ERROR][com.freerdp.core] - getaddrinfo: Name or service not known
Gtk-Message: 18:03:09.727: GtkDialog mapped without a transient parent. This is discouraged.

Offline

#6 2018-08-16 12:48:26

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: remmina can not connect since update to freerdp-1:2.0.0_rc3-1

Well, these two errors still point at a DNS error:

[18:03:09:178] [4775:4779] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_DNS_NAME_NOT_FOUND [0x00020005]
[18:03:09:178] [4775:4779] [ERROR][com.freerdp.core] - getaddrinfo: Name or service not known

Offline

#7 2018-08-16 17:31:42

uhoso
Member
From: Soest, NRW, Germany
Registered: 2014-04-24
Posts: 30

Re: remmina can not connect since update to freerdp-1:2.0.0_rc3-1

ok, I tried the same IP after downgrading to freerdp-1:2.0.0_rc2-2, same error. Seems, that the IP changed. I'll ask for the IP tomorrow and try again.

Offline

#8 2018-08-16 17:54:32

uhoso
Member
From: Soest, NRW, Germany
Registered: 2014-04-24
Posts: 30

Re: remmina can not connect since update to freerdp-1:2.0.0_rc3-1

Correction: Launching remmina with downgraded freerdp with IP as user (without sudo) connected to server without problem.

output was

LC_ALL=C remmina -c /home/uli/.local/share/remmina/1511697929196.remmina 
Failed to load plugin: /usr/lib/remmina/plugins/remmina-plugin-vnc.so.
Error: libvncclient.so.1: cannot open shared object file: No such file or directory
Failed to load plugin: /usr/lib/remmina/plugins/remmina-plugin-spice.so.
Error: libspice-client-gtk-3.0.so.5: cannot open shared object file: No such file or directory
StatusNotifier/Appindicator support: your desktop does support it, but you did not compile remmina with cmake's -DWITH_APPINDICATOR=on
Gtk-Message: 19:44:42.034: GtkDialog mapped without a transient parent. This is discouraged.
[19:44:42:608] [4818:4822] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr
[19:44:42:608] [4818:4822] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd
[19:44:42:608] [4818:4822] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[19:44:42:608] [4818:4822] [INFO][com.freerdp.client.common.cmdline] - loading channelEx drdynvc
[19:44:42:617] [4818:4822] [INFO][com.freerdp.core.nego] - Detecting if host can be reached locally. - This might take some time.
[19:44:42:617] [4818:4822] [INFO][com.freerdp.core.nego] - To disable auto detection use /gateway-usage-method:direct
[19:44:42:642] [4818:4822] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_DNS_NAME_NOT_FOUND [0x00020005]
[19:44:42:642] [4818:4822] [ERROR][com.freerdp.core] - getaddrinfo: Name or service not known
[19:45:03:860] [4818:4822] [INFO][com.freerdp.core.nego] - Detecting if host can be reached locally. - This might take some time.
[19:45:03:860] [4818:4822] [INFO][com.freerdp.core.nego] - To disable auto detection use /gateway-usage-method:direct
[19:45:03:875] [4818:4822] [ERROR][com.freerdp.core] - getaddrinfo: Name or service not known
[19:45:24:073] [4818:4822] [INFO][com.freerdp.gdi] - Local framebuffer format  PIXEL_FORMAT_BGRA32
[19:45:24:073] [4818:4822] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16
[19:45:24:075] [4818:4822] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel disp
[19:45:24:076] [4818:4835] [INFO][com.freerdp.channels.rdpdr.client] - Loading device service drive [Daten] (static)
[19:45:24:076] [4818:4835] [INFO][com.freerdp.channels.rdpdr.client] - Loading device service printer (static)
[19:45:30:184] [4818:4835] [INFO][com.freerdp.channels.rdpdr.client] - registered device #1: Daten (type=8 id=1)
[19:45:30:184] [4818:4835] [INFO][com.freerdp.channels.rdpdr.client] - registered device #2: PRN1 (type=4 id=2)
[19:45:30:184] [4818:4835] [INFO][com.freerdp.channels.rdpdr.client] - registered device #3: PRN2 (type=4 id=3)
[19:45:30:184] [4818:4835] [INFO][com.freerdp.channels.rdpdr.client] - registered device #4: PRN3 (type=4 id=4)
[19:45:30:184] [4818:4835] [INFO][com.freerdp.channels.rdpdr.client] - registered device #5: PRN4 (type=4 id=5)
[19:45:30:184] [4818:4835] [INFO][com.freerdp.channels.rdpdr.client] - registered device #6: PRN5 (type=4 id=6)
[19:46:02:693] [4818:4835] [ERROR][com.freerdp.channels.rdpdr.client] - Ignoring unhandled message PAKID_PRN_CACHE_DATA (EventID: 0x00000002)
[19:46:02:708] [4818:4835] [ERROR][com.freerdp.channels.rdpdr.client] - Ignoring unhandled message PAKID_PRN_CACHE_DATA (EventID: 0x00000002)
[19:46:02:714] [4818:4835] [ERROR][com.freerdp.channels.rdpdr.client] - Ignoring unhandled message PAKID_PRN_CACHE_DATA (EventID: 0x00000002)
[19:46:02:727] [4818:4835] [ERROR][com.freerdp.channels.rdpdr.client] - Ignoring unhandled message PAKID_PRN_CACHE_DATA (EventID: 0x00000002)
[19:46:02:747] [4818:4835] [ERROR][com.freerdp.channels.rdpdr.client] - Ignoring unhandled message PAKID_PRN_CACHE_DATA (EventID: 0x00000002)
[19:46:37:628] [4818:4822] [INFO][com.freerdp.core] - ERRINFO_LOGOFF_BY_USER (0x0000000C):The disconnection was initiated by the user logging off his or her session on the server.
Failed to check FreeRDP event handles

The errors pointing at a DNS error still occur.

Last edited by uhoso (2018-08-16 17:56:19)

Offline

#9 2018-08-17 04:27:46

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: remmina can not connect since update to freerdp-1:2.0.0_rc3-1

Hmm, I think it's best if you report this issue to the upstream developers.

Offline

Board footer

Powered by FluxBB