I just downloaded the application Server and client today. I installed the server on a known working terminal server 2003. I installed the ApplicationServer client for windows on 3 different XP machines. I see all of the published apps, but when I go to launch any of them, the 2x Application Server Client App minimizes and nothing happens. This happens for all 3 Windows XP computers. There are no firewalls between the clients and the server. And the XP firewall is turned off. I installed the Linux client and that runs the applications fine. Any Ideas? Edit: I just noticed that this is the same problem that mtills posted about in the topic: "Appserver client on XP Embedded". Maybe something is hosed with the latest appserver client distribution?
Client disappears without launching the Application I had a similar experience today in that I set up a brand new Windows 2003 Server R2 and installed Terminal Services and the license etc. and then installed the application server. When I access the applications from a the browser the Client shows the applications but when I launch them the client disappears without an error and the application does not launch. So I also would be interested in the answer to this problem.
Found out that the client works fine when it's installed on the server. I moved the Windows XP SP2 computers to an OU with no GPO. - No luck Logged in as admin on the workstations and tried - No luck Made sure the clients can access both ports on the server. Each client can definitely access port 20002 on the server because I get a list of the published apps. Using the Microsoft MSTSC.exe with the "Start the following program on connection" settings the same as one of the published apps works perfectly fine. This means each client can connect to the TS port. Still the same problem. I see the list of published apps, but when I try to launch one, the 2x app minimizes to the taskbar and nothing happens. No error message pops up and nothing is written to the local computer's event log. I also just tried the client on a Windows 2000 SP4 machine with the exact same problem.
I just installed the Beta 4 Version that was posted and it solved the connection issues I was having. I guess I'll give up on v3 and wait for v4 to be finalized.
Beta 4 solved my problem also I also installed the beta 4 version and everything works fine for me also. Thanks for letting me know about it. Simon
When you have problems related with the 2XApplicationServer Client, try this command: regsvr32.exe msrdp.ocx This will re-register the 'msrdp.ocx' in the system and usually will solve typical problems that were mentioned in the previous posts.
