Access Denied when clicking any remote tool (process, program, event, etc)

Implemented

Access Denied when clicking any remote tool (process, program, event, etc)

avatar

Hi there. I have searched through the forum, and so far cannot find an answer to this issue, so forgive me if it is there, and I didn't find it. I used to be able to click on "Remote Share", or "Remote Process", etc., and see the shares or processes of the computer in question. Now, I get an "Access Denied" message and it won't let me. In the properties of the computer, I have it get my admin creds from "use default credentials", and have also tried using "linked (vault)", and specifying an admin cred from there (have confirmed that those creds work)....

So 2 questions, where does RDM get the "default creds" from - I can't find a place to make a set of creds default...and secondly, am I looking in the wrong place to set the password for the remote tools?

Thanks!

Quintin

All Comments (13)

avatar

Hello Quintin,

Thank you for reaching out to us regarding this,

I have a few questions which you can hopefully answer.

  • Which version of RDM are you using?
  • Which type of data source are you using?


That being said, for Remote Tools, you would need to set the credentials in the entry "Properties" under the "Management Tools" -> "Tools" section, do you encounter the same issue when changing this field to "Custom" and entering the credentials?

We also have the following knowledge base article regarding WMI troubleshooting that I believe would be helpful in your case:
https://docs.devolutions.net/kb/remote-desktop-manager/troubleshooting-articles/wmi-troubleshooting/

I'm unsure what the Default Credentials option would be referring to in this case and will need to look into this.

Let me know,

Best regards,

Samuel Dery

avatar

Thanks for your response. I will look at the link that you provided. I did try manually adding my creds as you suggested, using the custom option, and that has the same result.

I'll check out your link, and let you know if that helps or not.

Also, version of RDM is 2023.1.29.0 64-bit
Vault is a google drive vault.
Also, this happens on 2 computers - both mine, only accessed one at a time - using the same vault. One machine is AD joined, the other is my personal home computer, not AD joined.

Thanks,

Q

avatar

Good morning. I can use wmic at the command prompt, I also tried remote registry from regedit (all this on my non AD joined machine), and they all work...see wmic below:

C:\Users\Quintin>wmic /NODE:"ferrari.snjlaw.local" /user:"snjlaw\xxxxxxxxx" /password:********** bios get serialnumber
SerialNumber
xxxxxxxxxxxxxxxxxxxxxxxxxxxx

Not sure why this doesn't work within RDM (and from 2 different computers). I have to assume it is related to some setting in the data source, and not the program...I will create a new data source, add my creds, and 1 computer, and see what happens. Will keep you posted...

Q

avatar

Good morning again. I can report that creating a new data source, and adding a host and creds did not help. I know that this was working until recently, so am really not sure what could have gone wrong.

Thanks for any help with this.

Q

avatar

Hello,

Thank you for your swift reply!

In your tests, have you created a new Google Drive data source? If so, would it be possible for you to perform the same test but this time with a SQLite data source, and see if the issue remains the same? This test will allow us to rule out the possibility that this issue could be tied to the type of data source currently in use.

Best regards,

James Lafleur

avatar

Hi! I used a local data source for my test, but I can do a SQLite one as well if you think that might make a difference.

Q

avatar

I just tried that with a SQLite source, and had the same result. It logs onto RDP OK (and I assume that the default creds on the tools page means to use the creds assigned to the RDP tab)...I have tried default, and custom, and linked from my vault all with the same result, with known, good creds...

Thanks for your time and help with this! :)

Q

avatar

Hello Quintin,

Thank you for your replies,

I've linked your thread with our currently open case with the engineering department they are currently investigating this issue, I will keep you updated with any news I receive regarding this,

Let me know if you have further questions,

Best regards,

Samuel Dery

avatar

Thanks. Is there a case # that is open to the public to see progress? If not, that's fine, I'll wait for an update here :)

Have a great day!

Q

avatar

Hello Quintin,

Thank you for your reply,

I'm afraid not, unfortunately,

Have a nice day!

Best regards,

Samuel Dery

avatar

Hello Quintin,

Thank you for your patience,

I wanted to inform you that a fix for this issue should be included in the latest version of RDM 2023.2.12.0 which can be downloaded from here: https://devolutions.net/remote-desktop-manager/home/thankyou/rdmsetup/

If you're using an "Advanced" type of data source such as SQL Server, updating to this version may require a database upgrade, we have the following knowledge base article regarding this:
​​​​​​​https://docs.devolutions.net/rdm/windows/installation/database-upgrade/

Let me know if the issue persists for you after the update,

​​​​​​​Best regards,

Samuel Dery

avatar

Thank you so much! You have no idea how much I missed that :)

All good, everything works now!

Q

avatar

Hello Quintin,

Thank you for your reply,

Perfect, I'm glad to hear that it is now working as expected!

If you have further questions regarding this feel free to let me know,

Best regards,

Samuel Dery