mRemoteNG / mRemoteNG/mRemoteNG
Auto reconnect with VNC - Feature request
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 11.1k
- Forks
- 1.6k
- Avg merge
- 16h 58m
- Merged PRs (30d)
- 55
Description
Hi,
Expected Behavior
When a vnc controlled device restarts the tab should stay open and a "Reconnecting 1 of 10" message should appeare.
If the device is up again the connection is reestablished.
Current Behavior
When a vnc controlled device is restarting the tab closes/disappeares without a message.
Possible Solution
Integrate a configureable vnc reconnect setting. E.g. you can configure that after 5,10, 20.... unsuccessful reconnects the
tab should close or stay with error message.
Context
Usually i have multiple vnc tabs open e.g. for updating multiple machines.
If a update requires a reboot i have to know which machines i had open to reopen them after some minutes.
Regards
Gero
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
No files or tests are named. Start by tracing how VNC connections and their tabs handle device restarts, then identify where connection loss closes the tab. Done means the tab remains open, shows configurable reconnect progress, restores the connection when available, and follows the configured failure limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100