Replies: 7 comments 2 replies
-
|
(Update: I stood up a windows server on EC2 in order to quickly sanity check RDP to this new server, still on my home network and still using Remmina client, and everything is copacetic. So I do think it's got something to do with the xrdp running on the microcomputer somehow...) |
Beta Was this translation helpful? Give feedback.
-
|
From all the evidence you've presented, it seems to be the link between the microcomputer and your home router. Have I got that right? Any chance you can use a cable to confirm? BTW - copacetic. Very nice - I'd not come across that before. It seems to be an American English word which hasn't (yet) made it into the wider anglosphere. |
Beta Was this translation helpful? Give feedback.
-
|
Ha! I learned "copacetic" from a professor I had, Stuart Kurtz. I don't think I've ever heard anyone else use it. There is a chance it's just the two (now three) of us left keeping it alive :) Thanks for your response! I finally managed to try with a cable - results below. TLDR yes, it definitely seems to be the wifi link between microcomputer and router. But still - if I take RDP out of the picture, connect to the microcomputer by HDMI, and browse YouTube over the same wifi link, I can at least watch a video at a completely normal clip. I don't know what protocol/port YouTube is using for the video part, but if I try the iperf3 test on ports 80 or 443 over wifi, the results are as dismal as the ones previously posted for 3389. I obviously don't know anything about RDP or the physical/data network layers; if you tell me this has nothing to do with (x)rdp, and comes down to the wifi adapter/router combo or something, I'm very ready to believe you. I simply don't know how to test this myself. Home network with wired connection between microcomputer/routeriperf3 on the xrdp server: iperf3 on the xrdp client: With xrdp started back up again, snapshot of iftop output from server: ping: |
Beta Was this translation helpful? Give feedback.
-
|
The only thing that springs to mind is #2905. See in particular this comment. That fix was merged for v0.10.x though, so if you're running that it won't be that. Which backend for xrdp are you using, and which version of xrdp? |
Beta Was this translation helpful? Give feedback.
-
|
I am running v0.9.17: I'm not sure how to check what xrdp backend I am using (sorry!! I am using a pre-built disk image made by someone else and did not install anything myself) but if I run Per the fix that you linked above, I tried but everything stayed pretty much the same. Just in case, I tried but then for some reason any RDP session I try to open just closes immediately, even though xrdp definitely restarted: |
Beta Was this translation helpful? Give feedback.
-
|
Your sessions are closing due to a problem with restarting xrdp-sesman. When you do this, the existing sessions remain running, but they cannot be connected to via xrdp (this is a known and longstanding bug). Because systemd only allows one session per user, you cannot start another session for the user. You will need to kill the processes associated with the running session before you can start another one. The You're probably using the xorgxrdp backend on an apt-based system. When you log in, you can select the backend on the login screen:-
HTH |
Beta Was this translation helpful? Give feedback.
-
|
Thanks so much for all your help on this. I confirm I am using Xorg! Based on what you said, I tried the following: Then, after starting a new ssh session: Then started a new RDP session. But the problem remains. I am probably wasting your time, especially given that this is an old version of xrdp. I cannot update the xrdp on this particular machine, but I will try to set up a different xrdp at some point on some other machine and see if the same thing happens. Thank you again! |
Beta Was this translation helpful? Give feedback.
-
|
Please have another go (when you can) with xrdp 0.10.x and report back. There are more compression options with 0.10.x, and this may well help. Another thing you could try is to use the |
Beta Was this translation helpful? Give feedback.
-
|
OK, will do! I will be away from my problem router for a couple weeks, but will resume after that! |
Beta Was this translation helpful? Give feedback.
-
Hello! I am using xrdp and Remmina for RDP sessions between my laptop and a microcomputer. It works well on some networks (I tried a school network as well as public coffee shop wifi), but on my home network the connection lags so much that it is utterly unusable. On the other hand, if I connect laptop and microcomputer to a phone hotspot (where, fwiw, the phone is on my home wifi), then the lag disappears. What could possibly be causing this?
These instructions #1600 (comment) from another thread seem most closely related, so below is iperf3 and iftop output for three different scenarios. The numbers agree with what I am experiencing. But why? I think I'm supposed to conclude that my home router is a potato, but it works fine for multiple zoom calls/youtube videos/etc? Is it possible it's a port/protocol thing? I am at a loss. Any help appreciated. Thanks so much!
Public wifi at coffee shop (no lag)
iperf3 on the xrdp server:
iperf3 on the xrdp client:
With xrdp started back up again, snapshot of iftop output from server:
Tried ping for good measure:
Over home network (huge lag)
iperf3 on the xrdp server:
iperf3 on the xrdp client:
With xrdp started back up again, snapshot of iftop output from server:
ping:
Over phone hotspot:
iperf3, server:
iperf3, client:
ping:
Beta Was this translation helpful? Give feedback.
All reactions