We recently upgraded our production IVEs from 7.2R3 to 7.3R2. Since then the performance of the Hob Java RDP client has been horrible - laggy, slow and nearly unusable.
I rolled back a test system from 7.3R2 to 7.3R1 and the Hob Java RDP performance went back to normal, which is about on par with the Win32 Juniper Terminal Services client.
Has anyone else experienced this issue?
Solved! Go to Solution.
The fix has been confirmed. If you are running into this issue, please open a case so we can provide the files to resolve the issue.
Was the upgrade from 7.3R2 > 7.3R3 or 7.3R1>7.3R2. The latter would make sense as the hob applet was upgraded to 3.3.0692 in 7.3R2 (http://www.juniper.net/techpubs/software/ive/releasenotes/j-sa-sslvpn-7.3r2-releasenotes.pdf). I have not heard of any performance issues with the newer applet.
The upgrade was from 7.2R3 to 7.3R2.
I also have a test system that was upgraded from 7.3R1 to 7.3R2. I rolled the test system back to 7.3R1 and the RDP issues went away. The version of Hob was 3.3 before and after the rollback, but the poor performance was only seen under 7.3R2 ( and not under 7.2R3 or 7.3R1).
So to summarize....
7.2R3 - Good
7.3R1 - Good
7.3R2 - Bad
It could be related to the hob applet change. This was changed in 7.3R2 and 7.4R1. Hob applet was upgraded from 3.3.0470 to 3.3.0692. Are we seeing slowness in multiple client types (Windows, Mac OS X, etc)?
I would recommended opening a case with JTAC to properly track this issue as Juniper will need to reach out the third party who develops the HOB applet. Please provide the case number once created as I will try and get the ball rolling on this one.
FYI. This issue should only affect Mac OS X users due to Apple's migration away from their own Java plug-in to Oracle's Java plug-in release. HOBLink has provided a potential solution and we are testing the following solution.
Yes, we did open a case and Juniper did provide fix for the issue in the form of a new version of the Hob client. We loaded the new client to the system through the standard process to add third party Java applets and configured the custom HTML.
So, far it appears the performance is back to what we would expect. The new version is jwt 33.0754 I believe. From a technical standpoint, my issue has been resolved. I'm now just waiting for an answer on whether or not this applet will honor our Premier Java RDP licenses as it did not replace the default version of the Premier Java RDP client.
(Thanks to everyone for the suggestions)
The default version cannot be removed from the SA. The files provided by JTAC are the later version of JWT which the issue is resolved. The same license should apply.