Customer upgraded from Stoneware WN 5.3 SP3 to WN 5.4. After the upgrade, we found that RDP applications no longer worked from Mac OSX Clients. They would get a Java Null Pointer Exception. In the past, we had to place /swproxy/rdp/NativeRDPApplet.jsp in the Startup URL section of the Web Application Proxies for them to work with OSX. After removing this line clients running OSX 10.4, and 10.5 could now connect to the RDP session, but users running 10.3 could not.
However, users running 10.4 and 10.5 versions are experiencing display problems when accessing IE7 on our windows terminal server through Stoneware. There seems to be problems with the screen not drawing correctly on some pages and frequent hangups.
Any ideas? The bigger issue for us at the moment is the clients with 10.4 and 10.5 that can at least connect. We have only a small number of 10.3 clients and are planning on upgrading them soon.
If you install the MS RDP client on those macs, then change the webapp
to the TS server to Client Selects and add the following to your login
script:
if clientos = MacOSX then
useClient(NativeRDP)
end
Then when the user clicks on the webapp and is on a mac, it will launch the Microsoft RDP client which should provide the most compatibility. When the webapp is set to the webRDP client, then for macs or PC using a NON IE browser, it uses the JAVA RDP client which is an Open Source project that seems to have lost steam in the past few years.
There are downsides to the MS RDP Client. They don’t do nice Single sign on. So the user would have to enter their credentials. And they would have to have the Microsoft RDP client installed on their machine.
Customer responded :
Thanks for the advice.
At this point the problem appears to only occur with Firefox, not Safari. In the past, we’ve always had our mac users use Firefox because Safari was problematic. Looks like the latest upgrade has reversed that.