"Authorization Failed: N/A" when initiating RDP session from SPP

I tried adding a Windows server asset and its service account to a session request on SPP. After I downloaded and opened the RDP file, it loaded the SPS blue screen for a while before the "Authorization Failed: N/A" error occurred.
I tried connecting directly to SPS by creating a generic RDP traffic control, using inband connection, and I was able to access the Windows server through SPS. 
Why couldn't I connect to the Windows Server when initiating with SPP?

I haven't changed anything to the "safeguard_default" policy.
I created similar configurations with SSH connections on SPP and it worked fine.
Thanks.

Parents
  • Hello haianh,

    It’s pretty hard to tell what’s going on with the RDP connection based on the info you’ve shared. I’d recommend opening an RDP tail log before trying to connect to the target server. That way, you can capture the exact error that’s causing the issue.

    To do this, go to the SPS node that’s recording the session. Head over to Basic Settings → Troubleshooting → View Log Files. Then, change the Log type to rdp and click Tail. A new window will pop up showing live details about the RDP connection.
    Once the tail log window is open, switch to SPP and try connecting with the RDP file.

    You should now see everything that happens during the RDP session, including a more detailed error message instead of just “Authorization Failed.”

    If you want, you can post the log here and I can help you pinpoint what’s going wrong.

    Best regards,

    Darko

Reply
  • Hello haianh,

    It’s pretty hard to tell what’s going on with the RDP connection based on the info you’ve shared. I’d recommend opening an RDP tail log before trying to connect to the target server. That way, you can capture the exact error that’s causing the issue.

    To do this, go to the SPS node that’s recording the session. Head over to Basic Settings → Troubleshooting → View Log Files. Then, change the Log type to rdp and click Tail. A new window will pop up showing live details about the RDP connection.
    Once the tail log window is open, switch to SPP and try connecting with the RDP file.

    You should now see everything that happens during the RDP session, including a more detailed error message instead of just “Authorization Failed.”

    If you want, you can post the log here and I can help you pinpoint what’s going wrong.

    Best regards,

    Darko

Children
No Data