XFreeRDP error BIO_should_retry returned a system error 32 Broken pipe solved

Written by Claudio Kuenzler - 0 comments

Published on September 26th 2023 - Listed in Linux Windows Network

When I wanted to connect to a remote Windows server using a VPN tunnel, I got the following error from FreeRDP:

ck@mint ~ $ /opt/freerdp-nightly/bin/xfreerdp /kbd:0x00000807 /size:1280x1024 /u:Administrator /d:example.com /v:10.10.45.15
[08:54:55:214] [24305:00005ef2] [ERROR][com.freerdp.core.transport] - [transport_default_write]: BIO_should_retry returned a system error 32: Broken pipe
[08:54:55:214] [24305:00005ef2] [ERROR][com.freerdp.core] - [transport_default_write]: ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]

The error(s) looks somewhat mystical and not self-explaining at all. A hint is however the part "TRANSPORT_FAILED". Could it be a connection problem?

It's always worth to verify the RDP port (tcp/3389 by default) can be reached on the target server:

ck@mint ~ $ telnet 10.10.45.15 3389
Trying 10.10.45.15...
telnet: Unable to connect to remote host: No route to host

Indeed, there is a communication issue.

It turned out I missed setting the route of the destination network (10.10.45.0/24) to my VPN (Wireguard) gateway.

After this route was added in my newly setup router running OpenWrt, communication worked:

ck@mint ~ $ telnet 10.10.45.15 3389
Trying 10.10.45.15...
Connected to 10.10.45.15.
Escape character is '^]'.
^]
telnet> quit
Connection closed.

And FreeRDP was able to connect to the RDP server again.

Add a comment

Comments (newest first)

No comments yet.