Unable to remotely login to computer at work - get dialog "An internal state error has occurred..."

[GordonD]

I'm trying to login remotely to my computer at work, using the Pulse Secure Terminal Services Client. When I try to connect to the host, I get a dialog saying, An internal state error has occurred. The remote session will be disconnected. Your local computer might be low on memory... etc.

It's the same symptom as issue https://community.pulsesecure.net/t5/Pulse-Connect-Secure/An-internal-state-error-has-occured/td-p/1...

My computer has aound 28 GB free, so there is no problem with resources. It's Windows 10.

These 3 programs were automatically installed when I went to connect to my computer on my company's web page: Pulse Secure Setup Client, Pulse Secure Setup Client 64-bit Activex Control, Pulse Secure Terminal Services Client. I've unstalled and let everything reinstall.

Any troubleshooting suggestions?

[[email protected]]

@GordonD, Issue might be related to NLA, any chance you happen to know what is the NLA status on the backend machine and on the VPN server?

Normally, internal state error message will be disaplayed if the NLA is not enabled on the VPN server but it is enabled on the remote machine which you're RDPing into.

[zanyterp]

Can you confirm that the computer you are connecting to is listed in the ACL as allowed? If the computer is not allowed, that is the message that will be displayed.

[dearone]

I have had this happen to me repeatedly. When this happens it has always meant that, for some reason, the computer that I am remoting into is shut down or stalled. Only a physical restart, by depressing the power button on the machine that I am trying to remote into, solves this. This is always very inconvenient as there is a reason why I have to remote in and cannot be physically in front of my remote computer. I wish there was a workaround, some way to restart your remote PC from the Pulse Secure interface. However, this is the issue. I do not know why none of the experts in this community mention this as the likely problem.

[dearone]

I have had this happen to me repeatedly. When this happens it has always meant that, for some reason, the computer that I am remoting into is shut down or stalled. Only a physical restart, by depressing the power button on the machine that I am trying to remote into, solves this. This is always very inconvenient as there is a reason why I have to remote in and cannot be physically in front of my remote computer. I wish there was a workaround, some way to restart your remote PC from the Pulse Secure interface. However, this is the issue. I do not know why none of the experts in this community mention that this is the likely problem.

[zanyterp]

hi @dearone,

i apologize that i forgot about the system being powered down as a reason for the message; thank you for the reminder of this use case