Unable to connect to Metaframe XP 1

[Quetzal]

I have one client workstation that is unable to connect to Metaframe XP. Client can see the published apps during setup. When attempting to connect to app, get message that "nework or dialup problems are preventing communication with citrix server". Same user can connect to apps on different client machine.

 

[Voyager1]

Can a different user connect to the Citrix apps from that machine?

Double-check the version of the client software on that client machine. The latest Win32 client is 6.20.985. - Bill

"You can get anything you want out of life, if you'll just help enough other people get what they want" - Zig Ziglar

 

[Quetzal]

No user can connect (I tried two others including administrator). The client version is current. Any ideas?

 

[ATCal]

What OS is it running? Same as the other workstations?
Al
atc-computing@home.com

 

[Quetzal]

Problem machine is running NT 4.0 sp 6. We have this running on similar clients as well as on Win 2K.

This problem machine is my workstation. As you might guess, I do things on my machine that we don't do on the "regular" users. It may well be time for a rebuild, but I was hoping to avoid that.

 

[scooter1974]

The problem may be that the registry entry for Cmstart.exe is missing or corrupt. To correct this problem, run Regedt32.exe and go to

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon

AppSetup:Type = REG_SZ:

Data = USRLOGON.CMD,CMSTART.EXE

These values are the default values for the AppSetup entry. If Cmstart.exe is missing, add it manually and attempt to reconnect to the published application.

NOTE: Icast.exe (application launcher) waits for Wfshell.exe to complete before launching the initial program for the published application. If Cmstart.exe is not listed under AppSetup value, Wfshell.exe is not launched and Icast.exe will timeout (after two minutes by default), generating the error message mentioned above.

Is a dream a lie if it don't come true
Or is it something worse

 

[Quetzal]

I have no AppSetup key in the registry; however, there is no such key on the client machines that are working either.
Adding such a key/value does not help the problem.

However, I also believe that it may be a registry problem...if the proper entries could be identified.

 

[scooter1974]

The Registry key must be on the server, if its not you will not be able to connect to published apps!!!!!!! Robin Plomp
Senior System Engineer
CCA

Is a dream a lie if it don't come true
Or is it something worse

 

[Quetzal]

AppSetup key is on the server. Sorry, I thought I made it clear the other client machines can access apps just fine. I can use my userid on other clients to access apps just fine. I just cannot get my workstation to connect.

 

[Jehova]

May not help in this case, but I have seen this error before.

It occured when I was dialing in to the office and attempting to connect into our Citrix farm. I adjusted the connection under the custom icon, or application set to be the dial-up networking session I was using and then was able to get in.

Since then, I have switched to using a VPN connection, which seems to work fine with the client configured for either LAN or WAN.

 

[ATCal]

Did you try editing the app properties and try directly entering the IP address of the server?
Al
atc-computing@home.com