microsoft / microsoft/dev-tunnels
port 3389 does not work
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 508
- Forks
- 52
- Avg merge
- 20h 6m
- Merged PRs (30d)
- 7
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
Contributor 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.
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.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100