[GH-ISSUE #149] Using configuration on remote share #126

New issue

Closed

opened 2026-02-26 11:56:50 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 11:56:50 +03:00

Owner

Originally created by @gofastgirl on GitHub (Sep 5, 2021).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/149

Hi,
Some I'm trying to do a configuration, but PRemoteM is not happy.
I have 3 different client machines that I use to connect to various VMs via RDP only.
So I put all PRemoteM files onto a shared drive that all guests can access.
I configured PRemoteM to connect to a couple of my VMS.
I configured PremoteM to store it's database in the same folder as the executable.
I added permissions to the ini and db files for EVERYONE Full Access
But I keep getting errors.
Database: Permission denied for reading! Please check your password of file occupation.

Any ideas what I need to do to get this to work?
Thanks!

Originally created by @gofastgirl on GitHub (Sep 5, 2021). Original GitHub issue: https://github.com/1Remote/1Remote/issues/149 Hi, Some I'm trying to do a configuration, but PRemoteM is not happy. I have 3 different client machines that I use to connect to various VMs via RDP only. So I put all PRemoteM files onto a shared drive that all guests can access. I configured PRemoteM to connect to a couple of my VMS. I configured PremoteM to store it's database in the same folder as the executable. I added permissions to the ini and db files for EVERYONE Full Access But I keep getting errors. Database: Permission denied for reading! Please check your password of file occupation. Any ideas what I need to do to get this to work? Thanks!

kerem

2026-02-26 11:56:50 +03:00

closed this issue
added the
question
label

kerem commented

2026-02-26 11:56:51 +03:00

Author

Owner

@VShawn commented on GitHub (Sep 10, 2021):

Database: Permission denied for reading! Please check your password of file occupation.

Since we open the database in exclusive mode, our PRemoteM database can not be shared by two client.

You can make a copy of PRemoteM in each of your gustes, and let them use their individual database. You have to export/import data manually when you change your connection info.

About the data sharing/sync, you can take a look at this ticket, I think sharing sqlite database will alway cause conflicts, so I hope I can add mysql support or C/S structure support, then we can get a central data source, and all the client can read data from the same source.

https://github.com/VShawn/PRemoteM/issues/76

@VShawn commented on GitHub (Sep 10, 2021): >Database: Permission denied for reading! Please check your password of file occupation. Since we open the database in exclusive mode, our PRemoteM database can not be shared by two client. You can make a copy of PRemoteM in each of your gustes, and let them use their individual database. You have to export/import data manually when you change your connection info. --- About the data sharing/sync, you can take a look at this ticket, I think sharing sqlite database will alway cause conflicts, so I hope I can add mysql support or C/S structure support, then we can get a central data source, and all the client can read data from the same source. https://github.com/VShawn/PRemoteM/issues/76

kerem referenced this issue

2026-02-28 12:01:34 +03:00

[GH-ISSUE #126] It is recommended that RDP connection do not use the credentials saved by Windows system to connect, and add RDP security option #1064

kerem referenced this issue

2026-02-28 12:01:39 +03:00

[GH-ISSUE #125] Option to cleanup Terminal Server Client registry tree, so user can re-setup connection's parameters #1065

kerem referenced this issue

2026-03-01 17:17:00 +03:00

[GH-ISSUE #126] It is recommended that RDP connection do not use the credentials saved by Windows system to connect, and add RDP security option #2024

kerem referenced this issue

2026-03-01 17:17:01 +03:00

[GH-ISSUE #125] Option to cleanup Terminal Server Client registry tree, so user can re-setup connection's parameters #2023