18.5. Oracle Virtual Desktop Client Troubleshooting

This section provides troubleshooting information for Oracle Virtual Desktop Clients.

18.5.1. Connection Problems When Using a VPN or WAN

The Maximum Transmission Unit (MTU) is the maximum packet size for connections. By default, the MTU is set to 1500 bytes.

If you experience problems when using a Virtual Private Network (VPN) or a wide area network (WAN), the MTU setting might be too high for your network.

To diagnose the correct MTU setting for your network, use the ping command to find the largest packet size that can be transmitted successfully.

On Windows platforms:

ping server-name -l bytes -f

where server-name is the name of the Sun Ray server and bytes is the packet size.

On Mac OS X platforms:

ping server-name -s bytes -D

where server-name is the name of the Sun Ray server and bytes is the packet size.

On Linux platforms:

ping server-name -s bytes

where server-name is the name of the Sun Ray server and bytes is the packet size.

To calculate the MTU setting, add eight bytes to the packet size.

To set the MTU, either change the setting on the Network tab or run the following command:

ovdc --mtu bytes server-name

where bytes is the MTU, in bytes and server-name is the name of the Sun Ray server.

18.5.2. Screen Rendering Problems

Screen rendering problems, such as slow screen redraw or blocks of black pixels, can occur if the Maximum Transmission Unit (MTU) setting is too high for the network.

The MTU is the maximum packet size for connections. By default, the MTU is set to 1500 bytes.

See Section 18.5.1, “Connection Problems When Using a VPN or WAN” for details of how to diagnose the correct MTU setting for your network.

18.5.3. How to Set the Logging Level

To help you to diagnose problems with Oracle Virtual Desktop Clients, you can increase the logging level.

Table 18.5, “Oracle Virtual Desktop Client Logging Levels” shows the available logging levels.

Table 18.5. Oracle Virtual Desktop Client Logging Levels

Level

Description

0

No logging

1

Critical messages

2

Warnings

3

Informational messages

By default, the logging level is 0, which sets logging to off.

The logging level is cumulative. For example, the maximum logging level 3 includes informational messages, warnings, and critical messages.

To set the logging level, run the following command:

ovdc --logging-level num server-name

where num is the logging level and server-name is the name of the Sun Ray server.

For example, to record warnings and critical messages for a connection to the sr-1.example.com Sun Ray server, run the following command:

ovdc --logging-level 2 sr-1.example.com

18.5.4. How to Change the Log File Location

By default, log messages are written to a .log text file on the client computer. The .log file is named after the profile used. For example, the log file for the default profile is called default.log.

The default location of the log file depends on the installation platform, as follows:

  • Microsoft Windows XP platformsC:\Documents and Settings\username\Application Data\Oracle Virtual Desktop Client\profilename.log

  • Microsoft Windows Vista and Microsoft Windows 7 platformsC:\Users\username\AppData\Roaming\Oracle Virtual Desktop Client\profilename.log

  • Mac OS X platforms$HOME/.Oracle Virtual Desktop Client/profilename.log

  • Linux platforms$HOME/.Oracle Virtual Desktop Client/profilename.log

If you use the --profile command option to specify the path to a profile, the log file is created automatically in the same directory as the profile. In the following example, log messages are written to the C:\tempfullscreen.log file.

ovdc --profile C:\temp\fullscreen 

18.5.4.1. Using the --logfile Command Option

You can use the --logfile command option to change the name and location of the log file. If the path to the log file contains spaces, surround the path with straight quotation marks (").

The following example uses the default profile and writes log messages to the mylog.txt file in the default location.

ovdc --logfile mylog.txt

The following example uses the default profile and writes log messages to the C:\temp\logfile.txt file.

ovdc --logfile C:\temp\logfile.txt

The following example uses the C:\profiles\fullscreen profile and writes log messages to the C:\temp\logfile.txt file.

ovdc --profile C:\profiles\fullscreen --logfile C:\temp\logfile.txt

The following example uses the C:\profiles\fullscreen profile and writes log messages to the mylog.txt file in the default location.

ovdc --profile C:\profiles\fullscreen --logfile mylog.txt

18.5.5. How to Use On-Screen Displays to Diagnose Connection Problems

The Sun Ray Software uses on-screen displays (OSD) to display the status of a connection. The OSD can be used to diagnose connection problems with Oracle Virtual Desktop Clients.

See the Sun Ray Client Troubleshooting Icons chapter in the Administration Guide for more details about the available icons and messages.