-
Notifications
You must be signed in to change notification settings - Fork 14.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[proxy] Connection Windows 2008 R2 occasionally disconnects directly #8374
Comments
which client do you use to connect to the proxy? |
anyway, should change the behavior to just drop such packets with a warning and not terminate the session. |
The client operating system is windows11. Info Log.``` [21:23:35:181] [19:96] [INFO][proxy.server] - [SessionID=F298B03DF226F9D62A5D82C0396C6602][pf_server_handle_peer]: peer connected: 192.168.208.215 [21:23:35:266] [19:96] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 [21:23:35:266] [19:96] [INFO][com.freerdp.core.connection] - Server Security: NLA:0 TLS:1 RDP:0 [21:23:35:266] [19:96] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:0 TLS:1 RDP:0 [21:23:36:703] [19:96] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 104: Connection reset by peer [21:23:36:703] [19:96] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D] [21:23:36:703] [19:96] [INFO][proxy.server] - [SessionID=F298B03DF226F9D62A5D82C0396C6602][pf_server_handle_peer]: starting shutdown of connection [21:23:36:703] [19:96] [INFO][proxy.server] - [SessionID=F298B03DF226F9D62A5D82C0396C6602][pf_server_handle_peer]: stopping proxy's client [21:23:36:703] [19:96] [INFO][proxy.server] - [SessionID=F298B03DF226F9D62A5D82C0396C6602][pf_server_handle_peer]: freeing server's channels [21:23:36:703] [19:96] [INFO][proxy.server] - [SessionID=F298B03DF226F9D62A5D82C0396C6602][pf_server_handle_peer]: freeing proxy data [21:23:36:704] [19:96] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe [21:23:37:754] [19:97] [INFO][proxy.server] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_server_handle_peer]: peer connected: 192.168.208.215 [21:23:37:833] [19:97] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 [21:23:37:833] [19:97] [INFO][com.freerdp.core.connection] - Server Security: NLA:0 TLS:1 RDP:0 [21:23:37:833] [19:97] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:0 TLS:1 RDP:0 [21:23:37:264] [19:97] [INFO][com.freerdp.core.connection] - Accepted client: XIAOBAI-PC [21:23:37:264] [19:97] [INFO][com.freerdp.core.connection] - Accepted channels: [21:23:37:264] [19:97] [INFO][com.freerdp.core.connection] - rdpdr [21:23:37:264] [19:97] [INFO][com.freerdp.core.connection] - rdpsnd [21:23:37:264] [19:97] [INFO][com.freerdp.core.connection] - cliprdr [21:23:37:264] [19:97] [INFO][com.freerdp.core.connection] - drdynvc [21:23:37:264] [19:97] [INFO][com.freerdp.core.gcc] - Active rdp encryption level: NONE [21:23:37:264] [19:97] [INFO][com.freerdp.core.gcc] - Selected rdp encryption method: NONE [21:23:39:473] [19:97] [INFO][proxy.server] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_server_get_target_info]: fetching target from config [21:23:39:473] [19:97] [INFO][proxy.server] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_server_post_connect]: remote target is 192.168.208.222:3389 [21:23:39:473] [19:98] [INFO][proxy.client] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_client_connect]: connecting using client info: Username: Administrator, Domain: WIN-G0MGP0D03U7 [21:23:39:473] [19:98] [INFO][proxy.client] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_client_pre_connect]: Loading addins [21:23:39:264] [19:98] [WARN][com.freerdp.crypto] - Certificate verification failure 'unable to get local issuer certificate (20)' at stack position 0 [21:23:39:264] [19:98] [WARN][com.freerdp.crypto] - CN = WIN-51SBJ0197QU [21:23:43:469] [19:98] [INFO][proxy.client] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_client_on_activated]: client activated, registering server input callbacks [21:23:43:469] [19:98] [ERROR][proxy.client] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_client_post_connect]: frames dir created: /opt/freerdp/data/captures/Administrator/192.168.208.222_05-11-2022_21-23-43-469 [21:23:43:469] [19:98] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRA32 [21:23:43:469] [19:98] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16 [21:23:43:470] [19:98] [INFO][proxy.channels] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_channels_on_client_channel_connect]: Channel connected: rdpdr [21:23:43:470] [19:98] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded proxy backend for rdpsnd [21:23:43:470] [19:98] [INFO][proxy.channels] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_channels_on_client_channel_connect]: Channel connected: rdpsnd [21:23:43:470] [19:98] [INFO][proxy.channels] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_channels_on_client_channel_connect]: Channel connected: cliprdr [21:23:43:470] [19:98] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpgfx [21:23:43:472] [19:98] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel disp [21:23:43:472] [19:98] [INFO][proxy.channels] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_channels_on_client_channel_connect]: Channel connected: drdynvc [21:23:43:957] [19:97] [WARN][com.freerdp.core.fastpath] - [fastpath_send_multiple_input_pdu] called before activation [UNKNOWN] [21:23:43:958] [19:97] [ERROR][com.freerdp.core.peer] - peer_recv_callback: CONNECTION_STATE_ACTIVE - peer_recv_pdu() fail [21:23:43:958] [19:97] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 [21:23:43:958] [19:97] [INFO][proxy.server] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_server_handle_peer]: starting shutdown of connection [21:23:43:958] [19:97] [INFO][proxy.server] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_server_handle_peer]: stopping proxy's client [21:23:43:958] [19:97] [ERROR][com.freerdp.core] - freerdp_abort_connect:freerdp_set_last_error_ex ERRCONNECT_CONNECT_CANCELLED [0x0002000B] [21:23:43:057] [19:98] [ERROR][com.freerdp.core.rdp] - rdp_recv_tpkt_pdu: rdp_recv_deactivate_all() fail [21:23:43:057] [19:98] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 [21:23:43:057] [19:98] [INFO][proxy.channels] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_channels_on_client_channel_disconnect]: Channel disconnected: rdpdr [21:23:43:057] [19:98] [INFO][proxy.channels] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_channels_on_client_channel_disconnect]: Channel disconnected: rdpsnd [21:23:43:058] [19:98] [INFO][proxy.channels] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_channels_on_client_channel_disconnect]: Channel disconnected: cliprdr [21:23:43:058] [19:98] [INFO][proxy.channels] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_channels_on_client_channel_disconnect]: Channel disconnected: drdynvc [21:23:43:062] [19:97] [INFO][proxy.server] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_server_handle_peer]: freeing server's channels [21:23:43:062] [19:97] [INFO][proxy.server] - [SessionID=40C4ABD4A1FC7DAC99CA559D4BBEFACC][pf_server_handle_peer]: freeing proxy data ``` Debug Log.
Thanks to @akallabeth. |
@wojiushixiaobai ok, but which client application do you use to connect? |
@akallabeth |
ok, this looks like a backport is due, as this is already handled on master |
@wojiushixiaobai ok, pushed a backport to the stable branch. A new release will follow this week. |
Connecting to Windows 2008 R2 with freerdp-proxy version 2.8.1 is disconnected randomly.
The same problem exists on Windows 7 ( Windown 7 has been upgraded to RDP8 ).
the RemoteFX and RDP 8.0 enhancements are not available for Windows Server 2008 R2 Session Host.
Error Connection Log.
[com.freerdp.core.fastpath] - [fastpath_send_multiple_input_pdu] called before activation [UNKNOWN]
Successful Connection Log.
The text was updated successfully, but these errors were encountered: