Published app access...

[KSUN]

I have a system with Windows 2003 Server SP3. It is also a domain controller.

I have connected the server to a wireless router.

I have another computer logging on to this server using a domain account on the server.

Both computers can ping - they are listed under the domain etc.

I start the ICA client on the client computer - and am able to see the published app.

But, when i try to start the published app - it says - logging in , and then negotiating capabilities and just exits.

The app does not run.

I tried to run the published app through the program neighborhood on the server itself. Same behaviour.

Can any body help, please?

 

[enigma99]

KSUN,
Looks like you are having licensing issues.
You might want to look in the event viewer for any licensing events. Usually the client will try to launch the application but can not get a valid TSCAL and it closes the connection.

Look at your TSCAL settings and to test it out you might want to switch from "Per Device" to "Per User" mode.

Hope that helps.

 

[Gellings]

Hi,

I wil do a try.
I think it is your router who won't communicate with the 1494 port. Only the port 80 is comming through you router that's why you see only de publish applications (that uses port 80) en can't start the applications.

Let me know of you router is configure right.

 

[cbrunet17]

I doubt its a router problem if (if I udnerstand him correctly) he tried running the program on the server itself and it was acting in the same manner.

Like Enigma said, check the event viewer for around the time that you tried to start the app (on the server, not the client) and see what errors your getting. Then take the event ID and go to:

http://www.eventid.net/

to see what can be done about it. They have a comprehensive listing or all event ID's with great solutions.

 

[cashburn]

We had a similar problem at our office. It is a citirix licensing issue. The resolution to our problem was to go into the registry of the client computer and follow this path:

hkey_local_machine\software\microsoft\mslicensing

Delete the "mslicensing" folder and its subfolders. This will cause TS to issue a new license to the client machine and you should be able to now open published apps.