Skip past navigation linksSecure Global Desktop 4.31 Administration Guide > Applications, documents and hosts > Troubleshooting sound in Windows applications

Troubleshooting sound in Windows applications

Select the section that best matches the problem:

No sound plays at all

If no sound is playing at all in the Windows Terminal Services session, use the following checklist to resolve the problem:

Things to check Description
Can the Secure Global Desktop client play sound? The Sun Secure Global Desktop Client on all platforms can play sound.

See the Secure Global Desktop Release Notes for details of which classic clients can play sound.
Does the client have an audio device? To be able to play sound, the client must have an audio device. If the client has a device, check that it works.

Users with Solaris Operating System (Solaris OS) or Linux client devices must also have read and write access to the following audio devices:

  • The /dev/audio device on Solaris Operating System (Solaris OS) platforms.
  • The /dev/dsp device on Linux platforms.

Note On Solaris Operating System platforms, if the AUDIODEV environment variable has been set to a different device, the Sun Secure Global Desktop Native Client tries to use this device before trying the /dev/audio device.
Is the volume muted on the client device? Check the volume control on the client device to see whether the user has muted the volume or set the volume level too low to hear.
Has the Windows audio service been enabled on the Secure Global Desktop server? By default, the Windows audio service is disabled for a Secure Global Desktop array. Check that the Windows audio service has been enabled on the Array properties panel in Array Manager.
Has the sound quality been changed? By default, the Windows audio service uses Medium Quality Audio. Changing the sound quality to Low Quality Audio or High Quality Audio limits the audio formats used in the Terminal Services session and may mean that the client cannot play sound.

Reset the sound quality to Medium Quality Audio on the Array properties panel in Array Manager.
Is the application running on a Windows 2003 server? You can only play sound in Windows 2003 Terminal Services sessions.
Has sound been enabled on the Windows 2003 server? By default, sound is disabled for Windows Terminal Services sessions. See the instructions for enabling sound.
Is the volume muted on the application server? Check the volume control on the application server or in the application to see whether the user has muted the volume or set the volume level too low to hear.

Sound is muffled or distorted

If sound is muffled or distorted, adjust the audio quality and compression settings to see if this improves the sound.

You can adjust the following:

Note The net gain of compressing audio data, which is pre-compressed, may be limited.

Not all users require sound

If you enable sound on the Windows 2003 application server and enable the Secure Global Desktop audio service, all users will be able to play sound in their Windows Terminal Services session. However, playing sound increases the amount of network bandwidth used and so you may want to restrict its use. Currently, the only way to do this is to disable sound for groups of users on the Windows 2003 server. To do this:

  1. Either:
  2. Select the group policy object you want to edit.
  3. Click Computer configuration, Administrative Templates, Windows Components, Terminal Services, Client Server Data Redirection.
  4. Open Allow audio redirection.
  5. Click Disabled.
  6. Click OK.

Changes to this setting only apply to new Windows Terminal Server sessions.

Related topics

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