mRemoteNG / mRemoteNG/mRemoteNG
Request for an option to keep tabs open after closing connection
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 11.1k
- Forks
- 1.6k
- Avg merge
- 16h 58m
- Merged PRs (30d)
- 55
Description
Request for an option to keep tabs open after closing connection without using the option
"automatically try to reconnect when disconnected from server (rdp & ica only)" because this causes a lot of udp traffic in the network.
Expected Behavior
I need an option to keep open tabs after closing the connection for a quick reconnection without permanent alive requests in the network.
Current Behavior
For each tab permanent requests to the target-computer are send. I have open 15 tabs and this causes to much traffic in the network and is a confusion for the network-administrator when he searches firewall-logs.
Possible Solution
Possibility 1: an option to keep tabs open after rdp-disconnection for further use
Possibility 2: an option to turn down the number of rdp-reconnection-requests; it is not necessary for the program to ask every second, if the computer is available for reconnection
Steps to Reproduce (for bugs)
- the traffic runs on UDP-Port 3389
Context
Your Environment
- Version used: 1.75.7012 and 1.76.20.24669
- Operating System and version (e.g. Windows 10 1709 x64): Win 7 x64, Win 10 x64, Win Server 2012R2
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
Start by locating the RDP connection and reconnection handling for open tabs; the issue names no files or tests. Compare the two proposed behaviors—keeping tabs without repeated requests or reducing reconnection frequency—and define which option should be implemented, with completion verified by confirming that disconnected tabs do not generate unnecessary UDP traffic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop-dev, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100