Skip to content
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

Meshconnect router RDP connection should map UDP port also #76

Open
troymroberts opened this issue Nov 17, 2023 · 4 comments
Open

Meshconnect router RDP connection should map UDP port also #76

troymroberts opened this issue Nov 17, 2023 · 4 comments

Comments

@troymroberts
Copy link

Is your feature request related to a problem? Please describe.
No it's not related to a problem so much. But the default action of the Meshcentral router application on a right click RDP connection, maps a TCP 3389 port for connection which works however it doesn't map a UDP port also, which leaves RDP performance on the table

Describe the solution you'd like
The application should map an identical UDP port for 3389

Describe alternatives you've considered
I've mapped the ports manually on a per server configuration, but that's clunky and inconvenient.

Additional context
Add any other context or screenshots about the feature request here.

@troymroberts troymroberts changed the title Meshconnect router RDP connection Meshconnect router RDP connection should map UDP port also Nov 17, 2023
@tomsik-radek
Copy link

If mounting both manually doesn't introduce any problems, I don't see why it shouldn't happen, either by default or with a client (or server) side option.

@troymroberts
Copy link
Author

troymroberts commented Nov 20, 2023

If mounting both manually doesn't introduce any problems, I don't see why it shouldn't happen, either by default or with a client (or server) side option.

It doesn't seem to like doing it manually though. Sometimes when i attempt it, either one of the ports gets "stopped" or if i do it as a mapping. Meshcentral will pick a random port for the source port.

@si458 si458 transferred this issue from Ylianst/MeshCentral Apr 9, 2024
@si458
Copy link
Collaborator

si458 commented Apr 9, 2024

just moving this to the correct repo 👍

when you click RDP, meshcentralrouter will pick a random TCP port like 12345 and map that to the remote computer
do you also need it to map UDP port 12345 then to the remote computer as well?

@troymroberts
Copy link
Author

troymroberts commented Apr 9, 2024

just moving this to the correct repo 👍

when you click RDP, meshcentralrouter will pick a random TCP port like 12345 and map that to the remote computer do you also need it to map UDP port 12345 then to the remote computer as well?

Yes correct. So it should look like

Random port e.g. 12345 (local computer) ---> 3389 TCP (remote computer)
+
Same Random port e.g. 12345 (local computer) ---> 3389 UDP (remote computer)

RDP performance is assisted by the availability of UDP connections, especially over slow ones

So you should see the following connections details
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants