starred/1Remote

Fork 0

mirror of https://github.com/1Remote/1Remote.git synced 2026-04-25 13:36:03 +03:00

[GH-ISSUE #230] Sometime PRemoteM is locking account #3084

New issue

Closed

opened 2026-03-13 01:38:26 +03:00 by kerem · 2 comments

kerem commented

2026-03-13 01:38:26 +03:00

Owner

Originally created by @coooly on GitHub (Apr 15, 2022).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/230

Originally assigned to: @VShawn on GitHub.

Describe the bug
Trying to connect to machine that's no entirely rebooted is locking account used.
Maybe PRemoteM is agressive when trying to login.

Expected behavior
Not locking account.

Screenshots
"As a security precaution, the user account has been locked because there were too many logon attempts or password change attempts. Wait a while before trying again, or contact your system administrator or technical support."

Desktop (please complete the following information):

OS: WIN 10
PRemoteM Version [e.g. 0.6.2.2 Store Version]

Originally created by @coooly on GitHub (Apr 15, 2022). Original GitHub issue: https://github.com/1Remote/1Remote/issues/230 Originally assigned to: @VShawn on GitHub. **Describe the bug** Trying to connect to machine that's no entirely rebooted is locking account used. Maybe PRemoteM is agressive when trying to login. **Expected behavior** Not locking account. **Screenshots** "As a security precaution, the user account has been locked because there were too many logon attempts or password change attempts. Wait a while before trying again, or contact your system administrator or technical support." **Desktop (please complete the following information):** - OS: WIN 10 - PRemoteM Version [e.g. 0.6.2.2 Store Version]

kerem closed this issue

2026-03-13 01:38:32 +03:00

kerem commented

2026-03-13 01:38:37 +03:00

Author

Owner

@VShawn commented on GitHub (Apr 18, 2022):

Hi, sorry for late.

It appears to have been caused by multiple logins with incorrect passwords.

The only thing I've done on this part is set the AutoReconnectionEnabled property to true, And I thought it would cause you issue.

https://github.com/VShawn/PRemoteM/blob/dev/PRemoteM/Model/Protocol/RDP.cs#L548

There are no other so call agressive operations.

So I think probably not a issue related to PRemoteM. Can you check your Event Viewer, to check out where the malicious action from. And whether they coincide in time with PRemoteM's activity.

Hoping for your feedback, Shawn.

@VShawn commented on GitHub (Apr 18, 2022): Hi, sorry for late. It appears to have been caused by multiple logins with incorrect passwords. The only thing I've done on this part is set the `AutoReconnectionEnabled` property to true, And I thought it would cause you issue. https://github.com/VShawn/PRemoteM/blob/dev/PRemoteM/Model/Protocol/RDP.cs#L548 There are no other so call `agressive` operations. So I think probably not a issue related to PRemoteM. Can you check your Event Viewer, to check out where the malicious action from. And whether they coincide in time with PRemoteM's activity. Hoping for your feedback, Shawn.

kerem commented

2026-03-13 01:38:43 +03:00

Author

Owner

@majkinetor commented on GitHub (May 10, 2022):

I will close this as there is no response and as it seems there is nothing to do.

@majkinetor commented on GitHub (May 10, 2022): I will close this as there is no response and as it seems there is nothing to do.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/1Remote#3084

No description provided.

Rows
Columns