I'm scratching my head over this issue. I have Fedora 3 SELinux and using KDE 3.3.2-0.1, system is up-to-date with Redhat Network. I've installed Citrix ICA Client for Linux (Ver. 8.0.85930, 128-bit SSL) and setup my Citrix connection to my work server. When I attempt to connect, it starts but fails on the reply from server. All my setting are correct and my prior version of Fedora (v.2) worked great.

What is got my going crazy is that it does not work from the desktop locally, but if I remotely connect to the X-Server and login to KDE, I am able to connect to my work perfectly. I'm a network engineer and I know there should be no difference with a firewall, port setting or etc, it's the same whether you are at the console or remote desktop. I can't figure this out, has anyone encounter this or might have a suggestion? Thanks

have installed the Citrix Client on a few linux distributions. I am currently running Fedora 3, but I used Ubuntu and Suse 9.2. I don't have SELinux enabled. I believe you will want to check out www.linuxjournal.com and search for a article about SELinux, I believe it was a three part series beginning around December of last year (04)

I have found out that it is better to the .tar file. instead of the rpm.
Also the Client install wants to be installed root, not super user root.

I also found that all Debian based distributions are needing the library libxaw6.0 installed before the client will work. I like the the version 8 is that it doesn't need the web browser open. you can launch the published programs from the task bar. I hope this helps!

The problem was with my Citrix Servers, not my linux box. The error message in my server logs was "Terminal Server Cannot Issue License". It was not a network problem. This is caused by the server assigning a license to the citrix client, however, because the client is not a microsoft OS, it did not have rights to a specific registry entery on the Citrix Server. Hope it helps for anyone else who has this issue!


Resolution

CTX105657 – User group does not authorize special permission for MSLicensing if MetaFrame client is newly installed with .exe installer package.

CTX463072 – Error: Cannot connect to the Citrix server.

Note: This step should not be needed. However, it may be worth investigating the Cryptography Registry keys under HKEY_LOCAL_Machine and HKEY_CURRENT_USER on both the server and workstation. See Microsoft TechNet and the usage of regmon and filemon from www.sysinternals.com for additional information.

These changes take effect from the client device.

NOTE: If you are making a desktop connection, then opening Program Neighborhood inside the desktop session (Pass-through) and the subsequent ICA connection is failing, the affected Workstation, in this case, is actually the server.

1. Open the Registry Editor (Regedt32.exe).

2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing.

3. Highlight this key, select Security on the toolbar, and select Permissions.

4. Click the Advanced key.

5. Verify that the Authenticated Users group is in Permissions Entries.
Note: If this group is not found, click Add, select the Users Group, and click OK.
In Permission Entry for MSLicensing, give full control to the Users group and click OK. In the Access Control Settings for MSLicensing, click Apply, then OK. In Permission Entry for MSLicensing, click Apply and then OK.

6. Attempt to connect using the Win32 Client.

NOTE: If using a NON Native Windows Client (Macintosh, Linux, or a Thin Terminal) without a local registry, the above permissions must be made to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\MSLicensing


Obtained at: http://support.citrix.com/kb/entry.jspa?entryID=1662