RDP on to connection server blocked

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

RDP on to connection server blocked

L3 Networker

To be clear I can use RDP to connect to other things in CyberArk, however I can no longer log on to the Connection servers themselves using RDP, either directly or via CyberArk.

 

When trying to do this directly I get the log in credentials request, it then goes to establishing quality of connection and the errors out

Error code: 0x3

Extended error code: 0x7

 

I can't see anything in the event logs on the servers.

 

All other CyberArk functionality is working as expected just not RDP directly on to the servers

 

Servers have been patched with January update, I have other servers also patched and can RDP on to them with no issues, all 4 of my Connection servers I can't, so seems to be specific to these servers only.

 

I have checked the following

Event logs, nothing obvious.

Disabled Applocker and no difference

Networking and Firewalls (Connection is made, login details requested but then dropped, so this feels more like something locally configured on the server blocking RDP sessions running on the server, rather than blocking the connection)

RDP using the local Administrator account - Fails

 

At a bit of a loss as to what has changed, Servers rebooted for patching so something could have kicked in then.

1 accepted solution

Accepted Solutions

L0 Member

Hi there,

 

We experienced (are experiencing) the same problem. Try doing this and see if you can connect to your RDP targets. Use the /admin switch in your RDP connection string (to connect in administrative/console mode) and see if it works.

 

Example:

old connection string = servername.xyzcorp.com

new connection string = servername.xyzcorp.com /admin

 

My guess is this will probably work.

 

We found in order to connect without the /admin switch, I had to do the following:

 

On the PSM server open Server Manager > Remote Desktop Services > under Collections > RemoteApp > Tasks > Edit Properties > Security > Security Layer

 

If we set the Security Layer to RDP Security Layer, we can connect without the /admin flag. If we set the Security Layer to SSL/TLS, the connection fails with the error unless we use the /admin flag.

 

So there seems to be a combination of Network Level Authentication/TLS security at play here somehow.

 

I'll be curious to know if this works for you/what your results are.

View solution in original post

7 REPLIES 7

L6 Presenter

Have you confirmed there were no changes to the GPOs? And which users / groups are in the Remote Desktop Users group? Check the effective GPO policy for Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > User Rights Assignment > Allow log on through Remote Desktop Services to see if your user's group is populated there. Since CyberArk connections are going through, it looks like the PSM users still have that permission.

L3 Networker

All the PSMConnect accounts and local Administrators group have the allowed to RDP rights.

Accounts being used are all server admins and can login via Console in VMware.

Admin accounts don't need to be in the Remote Desktop users group, but i did add a couple to test but makes no difference.

So unless it is not enumerating the group administrators for some reason I can't see why it would suddenly stop working.

L2 Linker

Check on RD Broker Role if they are running or not if RD Broker is installed then you may remove or disable RD Broker feature and try to connect again.

Thank you for that, we do have the broker installed.

I am struggling to find any CyberArk docs that cover the set up and install of RDS on the Connection servers, the installation guide does not mention it other than for licencing.

Its weird it has all been working fine for the last 4 months.

Hope your issue has been fixed, it may be due to cumulative update.

L0 Member

Hi there,

 

We experienced (are experiencing) the same problem. Try doing this and see if you can connect to your RDP targets. Use the /admin switch in your RDP connection string (to connect in administrative/console mode) and see if it works.

 

Example:

old connection string = servername.xyzcorp.com

new connection string = servername.xyzcorp.com /admin

 

My guess is this will probably work.

 

We found in order to connect without the /admin switch, I had to do the following:

 

On the PSM server open Server Manager > Remote Desktop Services > under Collections > RemoteApp > Tasks > Edit Properties > Security > Security Layer

 

If we set the Security Layer to RDP Security Layer, we can connect without the /admin flag. If we set the Security Layer to SSL/TLS, the connection fails with the error unless we use the /admin flag.

 

So there seems to be a combination of Network Level Authentication/TLS security at play here somehow.

 

I'll be curious to know if this works for you/what your results are.

L3 Networker

Have found that enforcing RDP works a treat, however users then get an error message for their RDP connections about not being compatible.

I tried the /Admin flag previously but it didn't work, but have retested and it does work now which is weird. I have also set up a seperate CC for the /admin and this works fine (RDP'ing to Cyberark servers through CyberArk seems weird but we have the PSMs behind an LB and firewalls blocking direct connections)

 

I also discovered an CyberArk KB for it which suggest some other policy changes should be done but these failed to work for me.

PSM - Direct RDP connection to the PSM server does not work after hardening of PSM server

 

I also found something on Micorosoft that said enabling/disabling FIPS encryption on the client/server side fixes the issue, though is relating to Remote Help not specifically RDP, however not tried this as it implied you will need to remove and re do BitLocker, or that Bitlocker encryption might not work afterwards or something else as it was not explicit just the usual vague statement.

Remote Assistance connection doesn't work - Windows Server | Microsoft Learn

  • 1 accepted solution
  • 2084 Views
  • 7 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!