Secure Global Desktop Administration Guide > Getting started > Sun Secure Global Desktop Software Release Notes

Sun Secure Global Desktop Software Release Notes

This topic lists the known issues for this release. Please read carefully.

The numbers in square brackets [ ] are our reference numbers. If you observe different behavior than we've described in these notes, please let us know, quoting the reference number.

Summary of known issues

Applications
[124987]Users experience some text corruption when using an SCO Console character application object.
[128519]If you use Secure Global Desktop to run the xterm program, the xterm program may not end when you expect it to.
[129350]Unable to map the keypad Enter key (KPENTER) on the user's client keyboard to keys found on a real terminal.
[129508]Part of the X root window pattern appears at the edges of Windows applications displayed using the Microsoft RDP protocol.
[511589]Trying to start an application on a UNIX application server as root does not succeed.
[511963]The Native Client Document Viewer object is not configured with any application when Secure Global Desktop is installed on Solaris systems.
[514597]X applications run on the same machine as the Secure Global Desktop server fail to launch.
[601320]Large (complex) images fail to display when accessed on a UnixWare 7.1.1 server using a display other than the local X server.
[601631]Users can't use the numeric keypad in an aixterm application.
[602423]Secure Global Desktop terminal emulators cannot distinguish between the Return key and the keypad ENTER key on the user's client keyboard.
[602534]Secure Global Desktop terminal emulators cannot distinguish between the left and right SHIFT, CONTROL and ALT keys.
[603093]VMS X applications fail to start if X display security is on.
[603538]On Red Hat 8, the font does not display correctly in the KDE terminal emulator.
[603578]TAB and CAPS LOCK keys do not work.
[604006]In some X applications, the ALT and ALT GR keys do not work.
[606936]Applications configured to display in seamless windows may not display correctly on a Gnome 2.0.0 Desktop.
Arrays
[514224]Webtop sessions do not relocate successfully when a user logs in to one Secure Global Desktop server without logging out of another.
[517279]A "FATAL ERROR" message is logged when running the array make_primary command.
[600232]The distribution of application launches is skewed towards the servers hosted on a particular UNIX type.
[600380]Clients cannot connect because they cannot resolve the external DNS name or it resolves to an uncontactable IP address.
[600931]When traversing a firewall, attempts to connect to Secure Global Desktop either fail or result in error messages. Secure Global Desktop may also crash.
Array Manager, Object Manager, and command-line tools
[511140]Changes made using command-line administration tools are not reflected in running instances of Object Manager or Array Manager.
[512334]Some displayed times, for example the session start times shown in the Object Manager Sessions tab, use the wrong timezone.
[512839]Object names appear with different names in other parts of Object Manager.
[513097]In Object Manager, changing the Inherit Parent's Webtop Content attribute for an object doesn't update the Links tab.
[513995]The summary information shown at the bottom of the Sessions tab is wrong for some application objects.
[514014]Users can't start Object Manager or Array Manager.
[600130]A javax.naming.NameNotFoundException warning occurs when you create an object whose name contains a forward slash. The object is not created.
Microsoft Internet Explorer web browsers
[601214]On Windows 98SE Internet Explorer 6 fails to connect to Secure Global Desktop when a DNS lookup is unavailable.
Netscape web browsers
[510747]With Netscape browsers on UNIX or Linux client devices running the Enlightenment window manager, applications configured to display using Client Window Management do not appear correctly.
Printing
[601300]When Secure Global Desktop printing has been disabled, print jobs can still be queued.
[603493]On Windows 2000 users are unable to print a file from a mapped client drive.
[603591]Users see a warning dialog that says print jobs have failed to print. The warning says the jobs remain queued on the server.
[605026]With CUPS version 1.1.18 installed, the Secure Global Desktop printer install script (prtinstall.en.sh) fails.
[605526]Printing fails on Windows clients if the user doesn't have permission to edit the Windows registry.
Native Client for UNIX
[515536]The webtop displays with the left-hand pane significantly wider than the webtop object buttons.
[515726]Vt420 applications sometimes start with a '>' prompt.
[515734]There are problems with specifying the initial size of a window, either from the command line or from the application defaults file.
[516453]Support is required for multiple font set definitions for localization to languages with 16-bit character sets.
[516519]Cannot type the Euro character using ALT+0128 (on the numeric keypad).
[603758, 603779]On Red Hat 8, users experience problems with the Native Client Log in dialog.
[605086]Native Client users on Solaris can't log in to a Secure Global Desktop server when Secure Global Desktop security services are running.
Native Client for Windows
[516519]Cannot type the Euro character using ALT+0128 (on the numeric keypad).
Web servers
[125591]Users can't download the Native Client for Windows.
[515326]An EAPI warning message is displayed when starting the Apache webserver.
[515788]Unable to find matching tokens when connecting to the Netscape webserver.
[601657]The Apache event log shows a "Premature end of script headers" error every time a user logs in to Secure Global Desktop.
[601888]Users are unable to download Secure Global Desktop Java™ archives.
[604700]Users can't download the Native Client for Mac OS X

Applications

Problem Using an SCO Console (SCO OpenServer 5.0.5+) character application object to run applications such as SCO Shell (scosh) and SCOadmin (scoadmin), users experience some text corruption. [124987]
Cause The tab3 terminal setting is not set.
Solution To correct this, set the tab3 terminal setting by entering "stty tab3" at the system prompt.


Problem If you use Secure Global Desktop to run the xterm program, the xterm program may not end when you expect it to. For example, if you set its application object's Resumable attribute to Webtop session, the application may not end when users log out of Secure Global Desktop. [128519]
Cause This is a problem with the xterm binary on UnixWare 7.
Solution Make sure the application object's Keep Launch Connection Open attribute is checked.


Problem It is not possible to map the keypad Enter key (KPENTER) on the user's client keyboard to keys found on a real terminal using Secure Global Desktop terminal emulators. [129350]
Cause Limitations in current versions of the virtual machine for the Java™ platform ('Java Virtual Machine' or 'JVM') on client devices.
Solution Future revisions of client device JVMs may resolve these limitations.


Problem Part of the X root window pattern may appear at the edges of Windows applications displayed using the Microsoft RDP Windows protocol. [129508]
Cause This occurs if the Windows application's width or height attribute is not a multiple of 4.
Solution Define the width and height to be multiples of 4.


Problem On any user's webtop, trying to start an application on a UNIX application server as root may not succeed. [511589]
Cause On most UNIX systems, the root user is not normally allowed to log into the system remotely, for example using telnet.
Solution Start applications as another user, or configure your UNIX system to allow root to access the system remotely. See your UNIX documentation.


Problem The Native Client Document Viewer object is not configured with any application when Secure Global Desktop is installed on Solaris systems. [511963]
Cause Secure Global Desktop Setup attempts to find Netscape binaries. If it can't, for example if Netscape is installed on another application server or in a non-standard location on the Secure Global Desktop server, it leaves the Application attribute blank.
Solution Using Object Manager, enter the full pathname for Netscape into the Application Command attribute of the Native Client Document Viewer object, located in the Secure Global Desktop System Objects organization.


Problem X applications run on the same machine as the Secure Global Desktop server fail to launch, reporting an error such as "Can't open display: unix:10" in the application launch dialog's Launch Details area. [514597]
Cause X applications built with the UDK on OpenServer may not work if the DISPLAY environment variable is set to "unix:n".
Solution In Object Manager, ensure that the Arguments For Command attribute of your X application object contains the following setting: 
-display $ALTDISPLAY


Problem Large (complex) images fail to display when accessed on a UnixWare 7.1.1 server using a display other than the local X server. [601320]
Cause The TCP extensions for high performance (rfc1323) are switched on by default on UnixWare servers. If the Secure Global Desktop server is installed on another operating system, rfc1323 may not be switched on by default or it may not be supported.
Solution Either switch on rfc1323 on the host where Secure Global Desktop is installed or switch it off on the UnixWare server.


Problem Users can't use the numeric keypad in an aixterm application. [601631]
Cause A known issue.
Solution The X application keyboard map file needs to be adjusted for aixterm. The keyboard map files can be found in the /opt/tarantella/etc/data/keymaps directory.

Add the following entries at the end of the file:

KEYMORPH  96 0 0
KEYMORPH  97 1 1
KEYMORPH  98 2 2
KEYMORPH  99 3 3
KEYMORPH 100 4 4
KEYMORPH 101 5 5
KEYMORPH 102 6 6
KEYMORPH 103 7 7
KEYMORPH 104 8 8
KEYMORPH 105 9 9
KEYMORPH 110 period period

These entries change what is sent to the application when a key is pressed. For example, keycode 96 is mapped to KP_0, however the key morph entry causes 0 (zero) to be sent.

Note Make sure you edit the correct map for your locale, for example xuk.txt for English (United Kingdom).



Problem Secure Global Desktop terminal emulators cannot distinguish between the Return key and the keypad ENTER key on the user's client keyboard. [602423]
Cause A known issue.
Solution Native Clients can now distinguish between Return and the keypad ENTER key in both X and Character emulation sessions. However, the default behavior is to map the keypad ENTER key to Return.

To change the behavior of the keypad ENTER key in a character application session, you need to set up a keymap for your character application object (--keymap) and add a mapping for KPENTER, for example:

KPENTER="hello"

To change the behavior of the keypad ENTER key in a X/Windows application session, you need to modify your X keymap (for example, xuniversal.txt) and add a mapping for the KP_Enter key, for example:

92 KP_Enter KP_Enter NoSymbol NoSymbol 0x801c

Warning! The X keymap is a global/user resource, so all applications for that user may be affected by this change. If any of these applications do not handle KP_Enter, then you may need to consult your X/Windows application application vendor for assistance.

Note The Java™ technology clients are still unable to distinguish between RETURN and the keypad ENTER key.



Problem Secure Global Desktop terminal emulators cannot distinguish between the left and right SHIFT, CONTROL and ALT keys. [602534]
Cause A known issue.
Solution Native Clients can now distinguish between the left and right SHIFT, CONTROL and ALT keys.

To add support for the right hand modifiers, you need to have the following lines in your X keymap (for example, xuniversal.txt):

196  Shift_R NoSymbol NoSymbol NoSymbol 0x36
197  Control_R NoSymbol NoSymbol NoSymbol 0x801d
198  Alt_R NoSymbol NoSymbol NoSymbol 0x8038

If the keymap on the server does not contain any mappings for Shift_R, Control_R or Alt_R, the left version of each key will be used.

Note The Java™ technology clients are still unable to distinguish between the left and right SHIFT, CONTROL and ALT keys.



Problem VMS X applications fail to start if X display security is on. [603093]
Cause VMS does not support X Security.
Solution Secure Global Desktop uses X security by default. To use VMS X applications you must disable X security on the Security properties panel in Array Manager or by running:

tarantella config edit --security-xsecurity 0


Problem On Red Hat 8, the font does not display correctly in the KDE terminal emulator. [603538]
Cause The default font for the KDE terminal emulator requires the X Render Extension and this is not currently supported by Secure Global Desktop.
Solution The workaround is either:
  • to run the terminal emulator with 16-bit color depth; or
  • to use a more traditional mono-spaced font.


Problem TAB and CAPS LOCK keys do not work. [603578]
Cause A known issue with the XKEYBOARD extension on an XServer.
Solution Disable the keyboard extension.


Problem In some X applications, the ALT and ALT GR keys do not work. [604006]
Cause Support for the META key on a Sun ™ keyboard was introduced in Sun Secure Global Desktop Software version 3.30 and some X applications may choose to use the META key in preference to the ALT key, when both keys are made available in the X keyboard map.
Solution Edit the keyboard map file being used for the application. Replace the following lines: 
199  Meta_L NoSymbol NoSymbol NoSymbol
200  Meta_R NoSymbol NoSymbol NoSymbol
With the following: 
199  NoSymbol NoSymbol NoSymbol NoSymbol
200  NoSymbol NoSymbol NoSymbol NoSymbol


Problem Applications configured to display in seamless windows may not display correctly on a Gnome 2.0.0 Desktop. [606936]
Cause An unpatched version of the Metacity Window Manager.
Solution Install the Gnome 2.0.0 Window Manager patch. Patch ID : 115780-03. Available from the SunSolve web site (http://sunsolve.sun.com)


Arrays

Problem If the clocks on all array members are not synchronized, webtop sessions may not relocate successfully when a user logs in to one Secure Global Desktop server without logging out of another. [514224]
Cause The timestamps on the webtop sessions determine which is newer. The newer webtop session is considered to be current. If clocks are not synchronized, the timestamps may give misleading information.
Solution Make sure that clocks are synchronized between Secure Global Desktop servers in the array. For example, you can use rdate.


Problem A "FATAL ERROR" message may be logged when when running the array make_primary command if a synchronization is occurring elsewhere in the array. [517279]
Cause This error message is displayed as a consequence of the data distribution mechanism readjusting after the array topology has been changed.
Solution In these circumstances, the error message is innocuous and may safely be ignored.


Problem In an array of Secure Global Desktop 3.01/3.00 servers using CPU-based load balancing which are hosted on a mixture of UNIX platforms (for example, Solaris and Linux), the distribution of application launches can be skewed towards the servers hosted on a particular UNIX type. [600232]
Cause A known issue.
Solution There is a partial solution available with Secure Global Desktop 3.11 which has not been available before.

The load of each server in the array is measured periodically as the CPU idle percentage. This is multiplied by a per-server weighting factor to form a weighted idle value which is replicated around the array for use in launch decisions. When an application launch decision is to be made, the servers in the array are categorized (by weighted CPU idle value) into two sets of servers: the least-loaded set and the most-loaded set. After this the Adaptive Internet Protocol (AIP) routing constraints determine the choice of server made from the least-loaded set and the choice is not necessarily the server with the highest weighted CPU idle value.

The default weighting is 100 and can be found in

/opt/tarantella/var/serverconfig/global/host_DNS_name.properties

in the property tarantella.config.host.tier2loadbalancing.weighting.

This value can be changed using a suitable editor. The new value takes effect when the server is restarted.

In an array, increasing the weighting increases the likelihood of launches being made on a server and decreasing the weighting decreases the likelihood of launches on a server, assuming that the weightings on all of the other servers in the array remain unchanged.

In an array of Secure Global Desktop servers on different UNIX platforms (for example, Linux and Solaris) of roughly the same power, it is expected that the effect of a launch (the amount by which each successful launch affects the CPU idle percentage) will be UNIX platform dependent and that each launch will show less of an impact on Solaris than on Linux. Therefore, in these circumstances, we suggest you use a weighting of 50 on the Solaris servers versus the default value of 100 on the Linux servers. Beyond that, to get an even spread of launches across disparate servers, it is a matter of trying different values for the weighting until you achieve the desired effect.

Note:

  1. The primary server in an array is more heavily loaded than a secondary because it is the primary. It should not be expected to handle the same number of launches as a secondary server. In a very large array, it may be prudent to set the weighting of the primary server to 0 so that it handles no launches at all.
  2. The CPU idle is measured as a percentage and so is in the range 0-100. The weighted idle must fit into a signed 32-bit integer so weightings in excess of 21,000,000 are not recommended. In practice, weightings should be kept to much smaller numbers than this (for example, < 1000).
  3. CPU-based load balancing of an array where all of the servers in the array run the same UNIX platform and are of similar power is known to work successfully in Secure Global Desktop 3.01/3.00.


Problem Clients cannot connect because:
  • they cannot resolve the external DNS name from the network they are on, or
  • they can resolve the name but it resolves to an IP address uncontactable from the network they are on.
[600380]
Cause Clients connect to the server by using the external DNS name. This name may only be resolvable by a DNS server located on an internal network, so clients external to this network may not be able to resolve it. Alternatively the name may be resolvable but the IP it resolves to may only be accessible via either an external or an internal network (for example if a server has two network interface cards, one connected to an internal network and one connected to an external network).
Solution Ensure the client can resolve the external DNS to an IP address that it can connect to. To do this either:
  • Configure DNS to return a different IP address for the external DNS name depending on which network the client is accessing it from. This means the external DNS name from a client on the internal network would give a different IP address from a client connecting from an external network, or
  • Amend the clients' hosts files so that the external name is resolves to the appropriate IP address connectable by that client.

Example:

The external name of the server is www1.indigo-insurance.com.

The server has two network interface cards (NICs), one connected to the company's internal network and one connected to an external network (for example, the internet).

The IP address of the internal NIC is 192.168.10.13.

The IP address of the external NIC is 192.168.10.57.

Clients on the internal network should be configured (either using DNS or in their hosts files)

to resolve www1.indigo-insurance.com as 192.168.10.13.

Clients on the external network should be configured to resolve www1.indigo-insurance.com as 192.168.10.57.



Problem When traversing a firewall, attempts to connect to Secure Global Desktop either fail or result in error messages. Secure Global Desktop may also crash. [600931]
Cause In the default configuration of firewall forwarding, the web server is set to listen to 127.0.0.1:443.

If the Secure Global Desktop server is started before the web server is started, Secure Global Desktop uses all the interfaces which results in web connections being proxied to itself in an infinite loop. The connection fails and may result in Tarantella crashing.

If the web server is started before the Secure Global Desktop server, an error message displays. The error appears to be serious but is in fact harmless.

Solution If you want to use firewall traversal and avoid these issues, you must:
  1. Configure the web server to bind only to the 127.0.0.1 (local host) interface, and
  2. Configure Secure Global Desktop to use all the other interfaces.

Consult your web server documentation for information on how you configure the web server to bind only to the 127.0.0.1 interface.

To configure Secure Global Desktop to use all the other interfaces, run the following command: 

tarantella config edit --tarantella-config-server-bindaddresses-external \
  "!127.0.0.1"

If you wish to specify exactly which other interfaces you want Secure Global Desktop to use, run the following command: 

tarantella config edit --tarantella-config-server-bindaddresses-external \
  "[comma-separated list of DNS names and/or IP addresses]"

Note On some shells you cannot use double quotes ("!127.0.0.1") as the !127 may get substituted. Use single quotes instead ('!127.0.0.1').



Array Manager, Object Manager, and command-line tools

Problem Changes made using command-line administration tools are not reflected in running instances of Object Manager or Array Manager. [511140]
Cause Simultaneous configuration by more than one administration tool is not supported, and may lead to inconsistencies in the datastore.
Solution Do not run more than one administration tool (for example, the tarantella object command and Object Manager) at the same time.


Problem Some displayed times, for example the session start times shown in the Object Manager Sessions tab, use the wrong timezone. [512334]
Cause The timezone is not supported by JDK™ 1.1.
Solution Edit the /opt/tarantella/etc/data/timezone file to define your timezone. See the file for instructions. Alternatively, you can set the TZ environment variable to the POSIX description of your timezone before you start Secure Global Desktop.


Problem The characters backslash \ and plus + cause problems in object names, appearing with different names in different parts of Object Manager. [512839]
Cause These are special characters that must be escaped, using a backslash \. In this release, Object Manager escapes them inconsistently.
Solution We recommend that you avoid using backslash \ and plus + characters in object names.


Problem In Object Manager, changing the Inherit Parent's Webtop Content attribute for an object doesn't update the Links tab. [513097]
Cause A known Object Manager issue.
Solution To update the Links tab, choose Properties for the object again.


Problem The summary information shown at the bottom of the Sessions tab may be wrong for some application objects (upgrades from Secure Global Desktop version 3.0 only). [513995]
Cause Part of the object name is passed to the case-sensitive views table in lower case characters.
Solution Stop the server and remove the file /opt/tarantella/var/ens/.object. Restart the server. Ignore the error message.


Problem Users can't start Object Manager or Array Manager if there is an apostrophe ' within their person object name (for example, .../_ens/o=Indigo Insurance/ou=Bill's OU/cn=Bill Orange). [514014]
Cause A known issue.
Solution We recommend that you avoid using apostrophes in object names.


Problem A javax.naming.NameNotFoundException warning occurs when you create an object whose name contains a forward slash. The object is not created. [600130]
Cause Secure Global Desktop interprets the forward slash as a part of the organizational hierarchy. For example, if you try to create an object with the relative name cn=a/b beneath o=organization, Secure Global Desktop will try to create an object called b within the o=organization/cn=a object. This fails because o=organization/cn=a does not exist.
Solution If you use a forward slash, you must backslash protect (escape) it. For example, to create an object with the relative name cn=a/b beneath o=organization, type cn=a\/b. This will create an object o=organization/"cn=a/b".


Microsoft Internet Explorer web browsers

Problem On Windows 98SE Internet Explorer 6 fails to connect to Secure Global Desktop when a DNS lookup is unavailable. [601214]
Cause The virtual machine for the Java™ platform ('Java Virtual Machine' or 'JVM') needs a DNS lookup to be able to download the Secure Global Desktop Java archive. If there is an entry, or even if the entry resolves to the wrong IP address, Internet Explorer will be able to connect to Secure Global Desktop. Internet Explorer 5 on Windows 98SE and Internet Explorer 6 on Windows 2000 do not seen to be affected by this problem.
Solution The solution is to add a name resolution entry for the Secure Global Desktop server into the hosts' files (in C:\windows).

Note This does not have to be the correct IP address (for example, 127.0.0.1 will work).



Netscape web browsers

Problem With Netscape browsers on UNIX or Linux client devices running the Enlightenment window manager, applications configured to Display Using Client Window Management may not appear correctly. [510747]
Cause Issues concerning the compatibility of the Enlightenment window manager with Netscape browsers.
Solution Use an alternative window manager on the client device.


Printing

Problem When Secure Global Desktop printing has been disabled, print jobs can still be queued. [601300]
Cause After disabling the Secure Global Desktop print system by running tarantella print stop, it is still possible to spool print jobs on application servers. These jobs will remained queued until Secure Global Desktop printing is restarted.
Solution To prevent these print jobs from being submitted, Secure Global Desktop Administrators must manually disable the Secure Global Desktop print queue on the application servers.


Problem On Windows 2000 users are unable to print a file from a mapped client drive. [603493]
Cause Windows 2000 SP3 introduced a fault that causes printing from a mapped network drive to fail when using Windows Terminal Services.
Solution You can either:
  • copy the file on to the application server and print it from there; or
  • obtain a fix from Microsoft.

See the Knowledge Base Article Q328020 for details.



Problem Users see a warning dialog that says print jobs have failed to print. The warning says the jobs remain queued on the server. [603591]
Cause The Secure Global Desktop clients check the status of printing services on the primary Secure Global Desktop server in the array, rather than with the array member the user will be using for printing services.

If the primary server says that printing services are available, the client will try to print, even if printing services have been paused/stopped on the secondary.

If the primary server says that printing services are not available, the client will not try to print, even if printing services are available on the secondary.

Solution As a workaround, we recommend you only change the status of printing services across the array, for example by pausing printing for the whole array.


Problem With CUPS version 1.1.18 installed, the Secure Global Desktop printer install script (prtinstall.en.sh) fails. [605026]
Cause A known issue.
Solution Upgrade to version 1.1.19 of CUPS.


Problem Printing fails on Windows clients if the user doesn't have permission to edit the Windows registry. [605526]
Cause A known issue. Some components of the Windows client needs to read various registry keys in order to detect and create printers. They also need write access to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\RNG\Seed key in order to detect client printers (this is required by the Windows EnumPrinters API).
Solution To be able to print, users must have write access to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\RNG\Seed registry key and read access to the rest of the registry.

This applies to the Sun Secure Global Desktop Client, the Java technology client and the Native Client for Windows on Windows client devices.


Native Client for UNIX

Problem The webtop is first displayed with the left-hand pane significantly wider than the webtop object buttons. [515536]
Cause A known issue.
Solution Resize the webtop frame.


Problem If your login password ends in an unusual character, vt420 applications may sometimes start with a '>' prompt. [515726]
Cause A known issue.
Solution Type 'CTRL-C' to return to the regular command prompt.


Problem There are problems with specifying the initial size of a window, either from the command line using '-geometry' or from the application defaults file. [515734]
Cause A known issue.
Solution A partial workaround is to set the size of the webtopFrame to half the required width: 
./ttwebtop -xrm "*webtopForm.width:512" -xrm "*webtopForm.height:768"


Problem Support is required for multiple font set definitions for localization to languages with 16-bit character sets. [516453]
Cause A known issue.
Solution This problem will be resolved in a future release.


Problem Cannot type the Euro character using ALT+0128 (on the numeric keypad). [516519]
Cause The Native Client for UNIX does not support this method of typing the Euro character.
Solution Type the Euro character using ALT GR+4.


Problem On Red Hat 8, users experience problems with the Native Client Log in dialog. The Native Client incorrectly clears the Location field even if a location has been stored and incorrectly stores an invalid password even if a user then supplies a correct password. [603758, 603779]
Cause This is a known issue and occurs when the system locale setting uses a UTF8 locale.
Solution Closing the Log in dialog and then opening it again clears the problems. The workaround is to set LANG to use a non-UTF8 setting, for example LANG = en_GB rather than LANG=en_GB.UTF-8.


Problem Native Client users on Solaris can't log in to a Secure Global Desktop server when Secure Global Desktop security services are running. [605086]
Cause Missing /dev/random device on the client. This is essential for Secure Global Desktop security services.
Solution Install the Solaris patch that contains this device. On Solaris 8, this is patch 112438-02.


Native Client for Windows

Problem Cannot type the Euro character using ALT+0128 (on the numeric keypad). [516519]
Cause The Native Client for Windows does not support this method of typing the Euro character.
Solution Type the Euro character using ALT GR+4.


Web servers

Note These are problems and issues that we've identified with web servers that you may notice when using Secure Global Desktop. They might be fixed by the web server's vendor in a later release.

Problem Users can't download the Native Client for Windows. [125591]
Cause By default, some Netscape web servers treat files with ".exe" extensions as CGI programs to run on the server, rather than files to download to the client.
Solution Edit your web server's mime.types file and remove "exe" as an extension for the "magnus-internal/cgi" type. Then add "exe" as a file extension for the "application/octet-stream" type, for example: 
application/octet-stream        bin dms lha lzh exe class jar cab


Problem The Apache event log shows a "Premature end of script headers" error every time a user logs in to Secure Global Desktop. [601657]
Cause The error message is a standard Apache message which occurs when the CGI fails to execute a script. When you run Secure Global Desktop with the Security Pack and have a test certificate installed, the web browser tries to download a custom certificate. As the certificate doesn't exist, the Secure Global Desktop ttacustomca.cgi script fails, producing the error.
Solution If you do not have a custom certificate installed, the error is expected behavior and can be ignored. The error can be prevented by installing a custom certificate.


Problem Users are unable to download the Secure Global Desktop Java™ archive. [601888]
Cause The web server's configuration is incorrect and so it does not download jar and cab file types.
Solution Edit your web server's mime.types file and add "jar" and "cab" as file extensions for the "application/octet-stream" type, for example: 
application/octet-stream        bin dms lha lzh exe class jar cab


Problem Users can't download the Native Client for Mac OS X. [604700]
Cause Your web server's configuration is incorrect and so it does not download dmg file types.
Solution Edit your web server's mime.types file and add "dmg" as a file extension for the "application/octet-stream" type, for example: 
application/octet-stream        bin dms lha lzh exe class jar cab dmg


Related topics

Copyright © 1997-2005 Sun Microsystems, Inc. All rights reserved.