freerdp can never connect

Hello,

What version of RDM are you running?

Do you have something relevant in Help -> View Application Log?

Best regards,

There's nothing in the log, currently using the 4.0.0.0 free edition.

Hi Tristan,

Could you activate debug logging for RDP connections?
You can turn it on in Options -> Type (RDP) -> Enable Logging. A restart is required for this settings to be fully functional.

You can then send the file created in C:\Users\{your user}\AppData\Local\Temp\RDM

You can then turn logging off as this file will rapidly grow to be several gigabytes.

Regards

Hi, thanks for looking into it, here it is - I removed the bits right after Sending Authentication token, as that seemed like it might contain sensitive information - let me know if you do need that:

[16:47:35:881] [8560:000025f8] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr
[16:47:35:881] [8560:000025f8] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd
[16:47:35:881] [8560:000025f8] [DEBUG][com.freerdp.channels.cliprdr.client] - VirtualChannelEntryEx
[16:47:35:881] [8560:000025f8] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[16:47:35:881] [8560:000025f8] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[16:47:35:881] [8560:000025f8] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[16:47:35:881] [8560:000025f8] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: FALSE
[16:47:35:881] [8560:000025f8] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: FALSE
[16:47:35:881] [8560:000025f8] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: TRUE
[16:47:35:881] [8560:000025f8] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[16:47:35:881] [8560:000025f8] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_NLA
[16:47:35:881] [8560:000025f8] [DEBUG][com.freerdp.core.nego] - Attempting NLA security
[16:47:35:885] [8560:000025f8] [DEBUG][com.freerdp.core.nego] - RequestedProtocols: 3
[16:47:35:999] [8560:000025f8] [DEBUG][com.freerdp.core.nego] - RDP_NEG_RSP
[16:47:35:999] [8560:000025f8] [DEBUG][com.freerdp.core.nego] - selected_protocol: 2
[16:47:36:000] [8560:000025f8] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_FINAL
[16:47:36:000] [8560:000025f8] [DEBUG][com.freerdp.core.nego] - Negotiated NLA security
[16:47:36:000] [8560:000025f8] [DEBUG][com.freerdp.core.nego] - nego_security_connect with PROTOCOL_NLA
[16:47:36:055] [8560:000025f8] [DEBUG][com.winpr.sspi] - InitSecurityInterfaceExW
[REMOVED] 9
[16:47:36:088] [8560:000025f8] [DEBUG][com.freerdp.core.nla] - Sending Authentication Token
[REMOVED]
[16:47:36:092] [8560:000025f8] [DEBUG][com.freerdp.core.nla] - Sending Authentication Token
[REMOVED]
[16:47:36:107] [8560:000025f8] [DEBUG][com.freerdp.core.gcc] - Server rdp encryption method: NONE
[16:47:36:343] [8560:000025f8] [DEBUG][com.freerdp.core.rdp] - recv Synchronize Data PDU (0x1F), length: 22
[16:47:36:343] [8560:000025f8] [DEBUG][com.freerdp.core.rdp] - recv Control Data PDU (0x14), length: 26
[16:47:36:343] [8560:000025f8] [DEBUG][com.freerdp.core.rdp] - recv Control Data PDU (0x14), length: 26
[16:47:36:343] [8560:000025f8] [DEBUG][com.freerdp.core.rdp] - recv Font Map Data PDU (0x28), length: 26
[16:47:36:343] [8560:000025f8] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGR16
[16:47:36:343] [8560:000025f8] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16
[16:47:36:345] [8560:000025f8] [ERROR][com.freerdp.codec] - mf_init failure

Are you connecting from a Server 2012 machine?

I'm connecting from a windows 7 x64 professional to a Server 2012 R2 Datacenter (64 bit), in this case.

Hi Tristan,

I was able to replicate your issue and have a fix ready.
It will be available in the next RDM release but in the meanwhile, you can solve the issue right away by downloading the attached file.
Simple copy the files in the same folder in RDM's installation path.

Let me know if you still experience the problem or if anything is unclear.

Regards

Thanks, it works perfectly when I add the dll. The added dll also works with the just released 4.0.1.0 - so I take it the fix will be included in the version after that one?

Yes, 4.0.1.0 was released before the fix was available. The next version will have the new dll baked in.