mRemoteNG / mRemoteNG/mRemoteNG

Add option to increase the connection attempt limit beyond 20

Open
#955 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement
Dominant language
C#
Stars
11.1k
Forks
1.6k
Avg merge
16h 58m
Merged PRs (30d)
55

Description

Expected Behavior

Have the option to increase connection attempts beyond 20 to keep RDP sessions online when losing network connection for a few minutes.

Current Behavior

If you lose network access for a while, for example when putting the laptop into standby, resume it at home and login with VPN 20 connection attempts are usually not sufficient - so you lose connection to all RDP sessions and have to re-login.

Possible Solution

Have an option to increase connection attempts beyond just 20.

Steps to Reproduce (for bugs)

  1. Connect to one or multiple rdp sessions
  2. disconnect from the network for more than 2 minutes
  3. all connections fully drop because the limit of 20 connection attempts is not enough

Context

If you lose network access for a while, for example when putting the laptop into standby, resume it at home and login with VPN 20 connection attempts are usually not sufficient - so you loose connection to all RDP sessions.

Your Environment

Windows / RDP

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the RDP reconnect logic and the current limit of 20 connection attempts. Check how connection settings are exposed for Windows/RDP sessions and whether related tests exist. Done means users can configure more than 20 attempts and sessions remain connected through the described network interruption.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop, networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.