port 3389 does not work
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- networking
Research direction
Reproduce the issue by hosting and connecting a tunnel on port 3389, then compare it with a second client connection using port 3390. Trace the tunnel's connection and data path to determine why remote desktop data fails on 3389; done means data crosses the 3389 tunnel successfully.
Written by the indexing model from the issue text.
Description
Hosting a tunnel on port 3389 and then connecting to the tunnel seems to work based on the information in the command line.
However, when sending data across the tunnel (using the remote desktop connection app) results in an error in connection, and the data is not actually sent to the hosting computer.
If you run 'devtunnel connect xxxxx' in a second instance it will use 3390 on the client side and then the connections are successful
- Dominant language
- C#
- Stars
- 514
- Forks
- 53
- Avg merge
- 1h 52m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/dev-tunnels
-
Web forwarding drops HTTP/2 response trailers, which breaks gRPC (HTTP/2 itself now negotiates fine)Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/dev-tunnels#687 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
microsoft/dev-tunnels#659 ·
-
devtunnel create routing flaps between near-equidistant clusters, silently creating cross-cluster duplicatesMay be free again @plequere-ms claimed this 122 days ago, and no pull request is open. Open
microsoft/dev-tunnels#642 · 2 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/dev-tunnels#608 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/dev-tunnels#567 · 1 comment ·
All issues in microsoft/dev-tunnels
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Volodymyr-Petrunin/Bankomaten#45 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AvaloniaUI/Avalonia#22420 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
dotnet/SqlClient#4823 · 1 comment ·
Maintainers usually reply within 2 days
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area-testing p1-recommended
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day