cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to connect to client using RDP: Get message "An internal state error has occurred....."

Highlighted
Occasional Contributor

Unable to connect to client using RDP: Get message "An internal state error has occurred....."

Hello,

I am using Pulse Connect Secure 9.1r3 and I have a user that cannot establish and RDP connection using port 3389. User gets error, "Pulse Secure Terminal Services Client - An internal state error has occurred. The remote session will be disconnected. Your local computer might be low on memory. Close some programs, and then try connecting to the remote computer again." 

 

I can confirm that the NLA box is checked within Pulse admin page as well as the Allow smartcard with NLA box is checked as well.

Also, I can confirm that with Pulse the machine that is giving this error is set to ALLOW within the ACL. 

I  can also confirm that there are FW rules on my boundary and internal FW to allow traffic from and to the Pulse client.

 

Am I missing something that I shouldn't be? Any troubleshooting steps that I should try? 

I work in a secure environment so providing screenshots or the config is not allowed. unless it is redacted extensively 

 

Any help would be greatly appreciated. Thank you in advance

2 REPLIES 2
Highlighted
Moderator

Re: Unable to connect to client using RDP: Get message "An internal state error has occurred...

do you have an ACL allowing access at Users>Resource Policies>Terminal Services?
What does your user access log show?
what does your events log show?
if you do have an RDP ACL that allows access, i would recommend opening a case with our support team
Highlighted
Occasional Contributor

Re: Unable to connect to client using RDP: Get message "An internal state error has occurred...

I'm having the same issue..  I am the VPN admin adn RDP admin so I can make any necessary changes.  The connection actually works sometimes.  We have a RDSH farm.... does the connection broker need to be in the ACL?    it feels like a conneciton broker issue.   NLA is checked.  any other tweaks?