Hi! We use 2X Client for Linux to connect to MS Windows Server 2003 via MS RDP with smartcard redirection. And smartcard redirection didn't work well. We use 2x Client in this way: ./appserverclient -m MX -C -s ssl://terminalserveraddress Some information. We have two types of cards - Aladdin eToken PRO 32K [old] and Aladdin eToken PRO 72K (Java) [new]. You can find information about it here: http://www.safenet-inc.com/aladdin-cont ... smartcard/ Old smartcards are redirected well by 2X Linux client. But it's also work (read and write info from smartcard) too slow! New smartcards are redirected, but with errors, so we can't logon using smartcards. When we connect to MS 2003 server and try to logon we get an error. In attach.zip you can see this error on "sc_error_win.png". After that we can logon to MS 2003 server using login-password and we can see redirected smartcard, but it is wrong. We've tried to see info about redirected smartcard using "certutil" (standart Windows program). You can see results of that in attach.zip: "sc_error.jpg" and "sc_error.txt". Also, when we use native windows RDC client with smartcard redirection it works well with both of old and new smartcards. And finally, Linux RDP client "rdesktop" ver. 1.7.0 also redirects smartcards well. You can see info from "certutil" with good smartcard redirection in attach: "sc_good.jpg" and "sc_good.txt". Hope for your help!