We have a user who works with Window 8 at home. Last week no problem logging in on the sa2500. After login he selects a Terminal Server and the terminal server client starts.
Last week I updated the Sa2500 to j-sa-7.3r3.0-b23377-package. It seems like after this action he was not able to start the terminal server session.
After logging in on the sa2500 he gets the message:
Juniper terminal Services Client stopped working.
He says that W8 is up to date. I re-installed the Juniper terminal server client. Java setting?
What more actions can I take??
The problem is with one user.
I have a windows 8 test machine and the user can login with no problems. At home he logs in with explore 10 and firefox.
I asked him to install the latest java version and turn off his windows firewall but he still gets the message.
is this the new application crash message? can you obtain a screenshot and post it here?
are there other windows 8 users successfully connecting?
The message is a pop up window with the text, Juniper terminal service client stopped working, not more.
The problem is only on the users W8 machine at home. At the office on a W8 test machine there no problems. I don't have more W8 users.
Last week he had no problems, the message was after the upgrade I did.
Unfortunately, looks like there is a conflict on his machine. Please open a case with JTAC so they can work with you to get information from the failing machine to work toward finding out what is happening
I have the same issue. It worked fine with Windows 8, but when I upgraded to 8.1 I started getting this same error.
Iewisra, Does the issue stop if you access the backend RDP server using IP rather than hostname? In that case this could be the same issue as described in http://kb.pulsesecure.net/InfoCenter/index?page=content&id=kb28418