RDGen Client Issue (Connection Error) #54

Closed
opened 2025-03-31 23:50:23 +08:00 by p2-genetics6570 · 7 comments
p2-genetics6570 commented 2025-03-31 23:50:23 +08:00 (Migrated from github.com)

Hi everyone,

I’m experiencing an issue with the RDGen client that I generated using the script from the RDGen project. I’m hoping someone here can help me out.

Problems:

  1. Generated .exe file: When I try to run the generated .exe, nothing happens. The program doesn’t start, and there’s no error message to indicate what might be wrong.

  2. Installed .msi file: After installing the generated .msi file and starting the client, I can connect to the host, but I every 3 seconds, the connection is dropped and re-established. I constantly get the error message:
    “Connection error: Connection was reset by the peer.”
    Image

Steps I’ve Tried:

  • I’ve tried using different versions of the RDGen script, but the issue persists.
  • I’ve tried the original rustdesk client (no problems)

My Questions:

  1. Has anyone else experienced similar issues with RDGen and found a solution?
  2. Could this be due to a misconfiguration in the generator or on the server side?

I’d really appreciate any help or suggestions!
Thanks in advance for your support. 🙏

Looking forward to your suggestions! 😊

Best regards

Hi everyone, I’m experiencing an issue with the RDGen client that I generated using the script from the [RDGen project](https://github.com/bryangerlach/rdgen). I’m hoping someone here can help me out. #### Problems: 1. **Generated `.exe` file**: When I try to run the generated `.exe`, nothing happens. The program doesn’t start, and there’s no error message to indicate what might be wrong. 2. **Installed `.msi` file**: After installing the generated `.msi` file and starting the client, I can connect to the host, but I every 3 seconds, the connection is dropped and re-established. I constantly get the error message: *“Connection error: Connection was reset by the peer.”* ![Image](https://github.com/user-attachments/assets/9c753529-9cbb-418a-b366-0340a88d56c6) #### Steps I’ve Tried: - I’ve tried using different versions of the RDGen script, but the issue persists. - I’ve tried the original rustdesk client (no problems) #### My Questions: 1. Has anyone else experienced similar issues with RDGen and found a solution? 2. Could this be due to a misconfiguration in the generator or on the server side? I’d really appreciate any help or suggestions! Thanks in advance for your support. 🙏 Looking forward to your suggestions! 😊 Best regards
bryangerlach commented 2025-04-01 02:03:05 +08:00 (Migrated from github.com)

Are you using a custom app name? If so, what name are you using? There might be an issue with either the service name that is created or the installation folder that is used. Also, before running or installing it is best to uninstall any old versions of rustdesk, especially if you have installed the official client. I have noticed similar issues when trying to run/install a custom generated client while having the official rustdesk client already installed.

Are you using a custom app name? If so, what name are you using? There might be an issue with either the service name that is created or the installation folder that is used. Also, before running or installing it is best to uninstall any old versions of rustdesk, especially if you have installed the official client. I have noticed similar issues when trying to run/install a custom generated client while having the official rustdesk client already installed.
p2-genetics6570 commented 2025-04-01 12:46:55 +08:00 (Migrated from github.com)

Yes, I am using a custom app name, which is P2-Remote-Support. I've also tried this on completely fresh Windows VM images where RustDesk has never been installed before. This eliminates the possibility of conflicts with previous installations.

Yes, I am using a custom app name, which is P2-Remote-Support. I've also tried this on completely fresh Windows VM images where RustDesk has never been installed before. This eliminates the possibility of conflicts with previous installations.
bryangerlach commented 2025-04-03 00:03:51 +08:00 (Migrated from github.com)

Try leaving the custom app name blank and see if you are still having these issues. Do you have a firewall or anti-virus software that could be killing the service?

Try leaving the custom app name blank and see if you are still having these issues. Do you have a firewall or anti-virus software that could be killing the service?
Maxetto commented 2025-04-03 16:04:48 +08:00 (Migrated from github.com)

Have you selected Run as Administrator? If so, try removing it.
I had similar issue when I checked that option, leaving it disabled made everything work perfectly and I didn't notice any issues interacting with the apps, even if they were run as admin.

Have you selected Run as Administrator? If so, try removing it. I had similar issue when I checked that option, leaving it disabled made everything work perfectly and I didn't notice any issues interacting with the apps, even if they were run as admin.
p2-genetics6570 commented 2025-04-03 16:24:38 +08:00 (Migrated from github.com)

Have you selected Run as Administrator? If so, try removing it. I had similar issue when I checked that option, leaving it disabled made everything work perfectly and I didn't notice any issues interacting with the apps, even if they were run as admin.

Solved with this hint! Thank you!

> Have you selected Run as Administrator? If so, try removing it. I had similar issue when I checked that option, leaving it disabled made everything work perfectly and I didn't notice any issues interacting with the apps, even if they were run as admin. Solved with this hint! Thank you!
bryangerlach commented 2025-04-03 21:51:40 +08:00 (Migrated from github.com)

If the Run as Administrator is no longer working, then I will remove it. I will test it and see.

If the Run as Administrator is no longer working, then I will remove it. I will test it and see.
Maxetto commented 2025-04-09 16:04:24 +08:00 (Migrated from github.com)

If the Run as Administrator is no longer working, then I will remove it. I will test it and see.

In Windows 7 it works fine, in Windows 10 it changes between versions.
On newer W10 versions it seems to drop the connection every 3 seconds like stated, on older W10 versions it seems to work fine.
On every W10 version it won't make the service visible in the Task Bar (yet it's running) and the file transfer doesn't work. Also the EXE version has to be Run as Administrator otherwise nothing happens.
That's what I found.

> If the Run as Administrator is no longer working, then I will remove it. I will test it and see. In Windows 7 it works fine, in Windows 10 it changes between versions. On newer W10 versions it seems to drop the connection every 3 seconds like stated, on older W10 versions it seems to work fine. On every W10 version it won't make the service visible in the Task Bar (yet it's running) and the file transfer doesn't work. Also the EXE version has to be Run as Administrator otherwise nothing happens. That's what I found.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: 3344/rdgen#54