Hello, We have this error when connecting to Windows server 2008 "An error was encountered when transitioning from TsSslStateHandshakeInProgress to TsSslStateDisconnecting in response to TsSslEventHandshakeContinueFailed (error code 0x80004005)"

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

Hello, We have this error when connecting to Windows server 2008 "An error was encountered when transitioning from TsSslStateHandshakeInProgress to TsSslStateDisconnecting in response to TsSslEventHandshakeContinueFailed (error code 0x80004005)"

L4 Transporter

An authentication error has occurred. (Code: 0x80004005)

1 accepted solution

Accepted Solutions

L4 Transporter

Hi we Fixed the issue.

For anyone with the same problem.

We solved by enabling the below security layer setting in Group Policy Manager in Windows 2008

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security

Field_Content_versions_oct20__068Vy00000cV7YnIAK.pngField_Content_versions_oct20__068Vy00000cUZCAIA4.pngAfter a restart the problem was fixed.

 

View solution in original post

8 REPLIES 8

L4 Transporter

Using RDP

L7 Applicator

Have you reviewed this ?

https://community.cyberark.com/s/article/PSM-RDP-Connections-result-in-An-authentication-error-has-occurred-Code-0x80004005

 

Windows 2008 is well out of support and CyberArk don't support connecting to it . However that technote may assist, but also will degrade the security of your PSM if you choose option 1 in the guidance .

 

Thank you Mal for the feedback!

Yes I saw it, but I wanted a confirm since it happened suddenly. I also saw it might be a certification problem

https://community.cyberark.com/s/article/00002374

because we also see  an RDP Window is suddenly closed and the error message “An internal error occurred” is shown.

L7 Applicator

How are you making the connection?

 

Test outside of CyberArk and see if the connection fails in the same way.

 

-Matt

Hi Matt,

sorry for the late reply.

Connect from PVWA or PSM server to target macchine with RDP.

at first we get

Field_Content_versions_oct20__068Vy00000bboAEIAY.pngthen we get

Field_Content_versions_oct20__068Vy00000bamNfIAI.png 

Outside CyberArk they can connect, which makes me believe an encryption problem like you suggested or perhaps a CA root certificates problem (Since it happened suddenly). Feels like CyberArk and Target macchine can't trust each other anymore.We already tried changing the password on both sides but no luck.

 

As for https://community.cyberark.com/s/article/PSM-RDP-Connections-result-in-An-authentication-error-has-o... we are waiting the Client to do some tests.

Thanks!

If direct RDP isn't working, that is def the first thing I would fix.

 

The way a PSM connection works is the connection goes from the PSM to the target. So as long as the RDP connection works from the psm to the target, then things should start to function.

 

-Matt

L4 Transporter

Hi we Fixed the issue.

For anyone with the same problem.

We solved by enabling the below security layer setting in Group Policy Manager in Windows 2008

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security

Field_Content_versions_oct20__068Vy00000cV7YnIAK.pngField_Content_versions_oct20__068Vy00000cUZCAIA4.pngAfter a restart the problem was fixed.

 

thanks for letting us know @ABDOU LAZEZ HUSSIEN EL SHEREDI​ !

 

-Matt

  • 1 accepted solution
  • 769 Views
  • 8 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!