Secure Global Desktop 4.31 Administration Guide > Applications, documents and hosts > Users are unable to use smart cards with Windows applications

Users are unable to use smart cards with Windows applications

If users find they are unable to use their smart cards with Windows applications, use the following checklist to identify the source of the problem.

Check	Description
Application server configuration	Is the application running on a Windows Server 2003 application server? Only Windows Server 2003 supports smart card device redirection. Has smart card device redirection been enabled for Terminal Services on the Windows Server 2003?
Secure Global Desktop configuration	Does the Windows application use Microsoft RDP as the Windows Protocol (--winproto)? Is the Secure Global Desktop smart card service enabled on the Array properties panel in Array Manager? Is the Allow smart card authentication box checked on the Application Launch properties panel in Array Manager?
Client configuration	Is the user using a supported client? Is the smart card reader working? On Windows clients: Check that the smart card reader listed in the Windows Device Manager. Check that the smart card service is running on the client (click Start Menu, Programs, Administrative Tools, Services). Check that the Sun Secure Global Desktop Client has detected the smart card reader and card. Right-mouse click on the Secure Global Desktop icon in the Windows system tray and select Connection info. The Smart card reader property should list the details in the format `reader`:`ATR_string` where `reader` is the manufacturer and model of the smart card reader and `ATR_string` is the Automatic Terminal Recognition (ATR) string which is a sequence of hexadecimal numbers used to identify the card to the system. On Linux/Solaris clients, start the Native Client, click Cancel when the log in dialog displays and then select View log from the Webtop menu. Check the message(s) that display and see below for details.

Native Client for UNIX/Linux smart card messages

No smart card support (<lib_name>): <error_message>

lib_name is the PCSC-Lite library file the Native Client tried to load. On Linux and Solaris this is libpcsclite.so. Depending on your dynamic linker path, this is normally installed in the /usr/lib directory. <error_message> is any additional error message from the dynamic linker.

This message only displays if the Native Client can't load a PCSC-Lite library.

Either install a version of the PCSC-Lite library or use the TTA_LIB_PCSCLITE environment variable to specify the location.

Smart card library loaded: <lib_name>

lib_name is the name of the PCSC-Lite library loaded by the Native Client.

This message only displays if the Native Client successfully loaded a PCSC-Lite library.

Failed to find context entry points in <lib_name>

lib_name is the name of the PCSC-Lite library loaded by the Native Client.

This message only displays if the PCSC-Lite library loaded by the Native Client does not support a minimum set of API routines.

Either install another version of the PCSC-Lite library or use the TTA_LIB_PCSCLITE environment variable to specify a different library.

Smart card support failed to initialize (0xH)

0xH is a PCSC hexadecimal error code.

The Native Client successfully loaded a PCSC-Lite library, but the smart card system on the client platform is not working.

Check that the smart card system is running on the client platform:

On Linux:
- Check that the PCSC daemon (pcscd) is running, for example by running /sbin/service pcscd status.
- Try restarting the PCSC daemon with a --debug stdout option. Insert the card in the reader and see if the reader and card are detected.
On Solaris:
- If you are using the PC/SC Shim for SCF package, check that the OCF server (ocfserv) is running. Enable it if it isn't (svcadm enable svc:/network/rpc/ocfserv).
- If you are using the Sun Ray PC/SC Bypass package, check the Sun Ray Server Software configuration.

Smart card reader: <reader name>

Lists the names of all the smart card readers attached to the client device.

If no smart card reader is listed, check the configuration of the client device.

Related topics
Array properties (array-wide) Smart Card Protocol Engine properties Using smart cards with Windows applications Configuring Microsoft Windows Terminal Services for use with Secure Global Desktop