davinder_rodey_mizuhocbus
asked on
Connectiing to Citrix MetaFrame XP / Windows Server 2003
I have a Windows 2003 server running Citrix MetaFrame XP. I've installed all the licenses and activated them. I've also created user accounts for remote access and "published" an application for users to connect to. I've also configured the web interface (via the wizard during installation) to serve as a method of connection.
The web interface loads fine and allows connections to the next stage where it displays icons of which applications are available (or published) but when I try to connect to the application I get the following error "Cannot connect to the Citrix MetaFrame server. The Citrix MetaFrame server you have selected is not accepting connections."
Any suggestions? Thanks.
The web interface loads fine and allows connections to the next stage where it displays icons of which applications are available (or published) but when I try to connect to the application I get the following error "Cannot connect to the Citrix MetaFrame server. The Citrix MetaFrame server you have selected is not accepting connections."
Any suggestions? Thanks.
Go to Management Console-->Servers-->right click the server-->Properties-->Mate
ASKER
The option was enabled. Any other ideas?
can you double check your Citrix feature release license?
what is you server’s feature release level?
what is you server’s feature release level?
ASKER
MetaFrame XP 1.0, Feature Release 3 Connection Pack (activated).
MetaFrame XO 1.0 for Windows, Feature Release 3 (activated).
I noticed that when I goto resource manager it lists my server as "unlicensed". Is there something I need to do to assign or apply licenses to different servers?
MetaFrame XO 1.0 for Windows, Feature Release 3 (activated).
I noticed that when I goto resource manager it lists my server as "unlicensed". Is there something I need to do to assign or apply licenses to different servers?
YOu need to assign licenses for CAL's.
AC
AC
ASKER
i assigned everything i could to the server but i still get the same error.
A) Make sure you have the citrix ICA WEB agent client installed on the remote machines.
B) Make sure you firewall is allowing ports 2598 and 1494 coming through.
C) Make sure that you have the citrix server able to talk with AD (Active Directory).
AC
B) Make sure you firewall is allowing ports 2598 and 1494 coming through.
C) Make sure that you have the citrix server able to talk with AD (Active Directory).
AC
ASKER
remote has the ica client installed, no firewalls are up (test setup consists of a simple LAN) and I'm not sure how to confirm Citrix has propper rights/configuration to work with AD.
I have a feeling that this might be related to terminal services although someone told me that as long as my remote devices are running a windows OS then I wouldn't need any additional licensing. The server is running on a Windows 2003 Standard server, where I've activated terminal services but haven't done anything beyond that--I thought at the least you get the 120 day trial. The remote device I'm connecting with is running Windows XP Pro (SP2), I know that the TS service is running but don't know how to further configure/view terminal server options under XP.
I have a feeling that this might be related to terminal services although someone told me that as long as my remote devices are running a windows OS then I wouldn't need any additional licensing. The server is running on a Windows 2003 Standard server, where I've activated terminal services but haven't done anything beyond that--I thought at the least you get the 120 day trial. The remote device I'm connecting with is running Windows XP Pro (SP2), I know that the TS service is running but don't know how to further configure/view terminal server options under XP.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Go into your Connection Configuration Manager, delete the ICA protocol and recreate it. It has been my experience as a consultant supporting a number if different enviroments that this is a common issue with both Windows 2000 and 2003.