Cannot launch the published application

[vrcatherine]

We have metaframe XP server and most of the clients get connected to the NFUSE and work. From 1 month i had seen that from some machines (probably new which did not have a ICA client) when i login to citrix with NFUSE or neighborhood it shows all the published apps . But when i click on any application it doesn't do anything.

Any help !!!



---Thanks
Cathy

 

[adehart]

You've probably tried this already but if you manually install the Citrix client, does it launch properly after that? It may just be having problems detecting if the client is installed and if not, forcing the download of the client. I don't use the NFUSE interface much (we use the PNAGENT mostly) but I recall seeing something like this at one point for machines that didn't have the client installed and when I had messed up the ability to install the client through the web interface.

- Anthony

 

[vrcatherine]

Thanks for the reply.

I got it fixed the issue was that the Terminal server was not issuing the licenses.



--Thanks
Cathy

 

[redmat]

Greetings,

Can you please tell me why wasn't the Terminal Server not issuing the licenses and how did you fix it?

Actually, I am having a similar problem with my setup. The difference is I have a Citrix server in a different subnet than the Thin Client Terminal at remote site trying to access the Server. There is a connectivity between the two as the server can ping the client and vice versa. Also using the client terminal (Fujitsu-Siemens' FUTRO B machine in this case)I can see the list of published applications on the server, but when I click on them nothing happens.

I am not even able to access the desktop using RDP. If you think this is a Terminal Server License issuing related problem then please reply with any suggestions you may have.

Any help in this regard is much appreciated.

 

[Ogi]

Hi,

Have you placed the server name in the key in TermService. Can you ping the server by the name and not the IP? I understand you statement above about being able to ping your license server but it must be ping"able" by it's name not IP. Might be worth putting an entry in the servers hosts file for safety!

Cheers,
Carl.

 

[vrcatherine]

I was checking the Citrix server Event viewer and it was
creating a log everytime whenever a client/end user is trying
to click on publish app.

The event viewer log said
" cannot issue terminal licensing"


Got into the registry and checked the citrix server
whether its pointing to the right Terminal Licensing server
as in our network the Citrix server and the domain & terminal
licensing server or different.


Check this registry settings on the citrix server

HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/MSLICESING/PARAMETERS

in that check DomainLicenseMulti KEY


---Cathy

 

[bran2235]

VRCATHRINE,
Don't you mean:
hklm\system\current_controlset\services\termService\parameters-
Add Reg-Sz (string value) SERVERNAME

?????
Just curious
You're adding the WTS Licensing Server, correct??


Brandon

 

[vrcatherine]

YEP

 

[redmat]

Hi folks,

Thanks for your prompt replies and kind suggestions.

With the Terminal Server things seems to be pointing in the right direction. I didn't recieve any TS warnings in the Event Viewer when trying to connect to the published apps. Moreover, I can say that TS is configured properly because the TS is issuing licenses to the clients that exist in the same subnet. It is this one client that I am trying to connect from a remote location with a different subnet.

Ogi, the client was not able to ping the server with its name. It was able to do so after I added an entry in 'lmhosts' file on the client. The server on the other hand can ping the client with its name.

Let me give some more information here in order to be more clear. We have Citrix Server (MetaFrame XPs FR1) and some non-windows Thin Clients (running eLux) in the Main Office on one LAN and on the same subnet, say it be: 192.168.1.0, with server having IP 192.168.1.3. Now the clients on the same subnet with IP addresses 192.168.1.10, 192.168.20, 192.168.1.30 can easily connect to the server and get assinged a TS CAL by terminal server (confirming that TS is configured right). As mentioned, the thin clients are non-windows and are connecting fine, I on the other hand, tried to connect to the server from a regular Windows based machine on the same subnet by using ICA win32 client. It too connected fine and got assigned a license by the TS.

On the other hand, the remote site has a different subnet of, lets say: 192.168.4.0. The client be it 192.168.4.23 on this remote subnet cannot connect to the server at 192.168.1.3. The remote site is connected to the main office over a 64kps ADSL data link connection. There is all kinds of connectivity (NetBIOS, HTTP, SMTP etc.) between the two sites with both side gateways configured to allow all types of traffic on any port (No doubt here for any authentication TCP 1494 or ICA browsing ports to be blocked. It can all go through). With this setup the thin client terminal can see the published applications on the server but it cannot connect to any. When any application is clicked for opening nothing happens and it takes for ever.

Now at the remote site, I also tried to connect to the server using a Windows machine with ICA win32 client. And to my surprise, after trying to connect to the server the ICA client returns an error saying "Cannot connect to the Citrix server: There is no Citrix Server configured on the specified address". Although, I don't get any such error from the thin client terminal where I can even see the published apps on the server. The TCP/IP settings tried on thin client and the windows machine are exactly the same.

What am I doing wrong here? Am I missing something? Can it still be a Terminal Server related issue (as it seemed to be at first when trying to connect from the thin client)? Can you fine folks suggest something that could further help me dig deeper into this. Any ideas? Much appreciated.

Thanks a bunch,

Regards,
-redmat