Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to connect to published app or Farm

Status
Not open for further replies.

kemit

Technical User
Nov 6, 2002
17
GB
Hi,

I have a metaframe Xpe server farm.
Which currently only consist of one server running windows 2000 service pack 2, metaframe Xpe.
I have published a test app within server farm, but I am unable to connect to published app.

The app appears in browse list when a dedicated connection is configured. But when application is launched I receive the error "Cannot connect to the Citrix server, There is no server configured on the specified address".
I am also unable to connect to server farm.
No prompting for logon id etc, when conecting to sever farm (application set).

I am not able to connect via server desktop client or from client on remote desktop.
The protocol used to connect is tcp/ip+http.
The ica browser service is running on the server.
qfarm /APP list published app.
IMA service is running etc

Thanks in Advance


Any ideas anyone.
 
Mostly sound like a ICA problem. Try reinstall the the ica client first.
Can you get ICA traffic trough
in a cmd promt
telnet <ipadress> <port#>

port number is probably 1494

and merry christmas
 
Hi Traver,
Thanks for the input.
I am able to establist ica connection to a deskptop session.
This is using TCP/IP protocol though.
If I attempt to connect using HTTP+TCP/IP connection fails.
Also published app only visible when TCP/IP+HTTP selected.

If I excute netstat at the command prompt to list ative connections on client.
The Active TCP ports on client is displayed showing connection to server via port 1494 on server.
This is for the desktop connection using TCP/IP.

For HTTP+TCP/IP connection
TCP za0vm1:2552 Serv1Test:http TIME_WAIT
There appears to be an issue with connectecting using HTTP.

Telnet to pot 80 appears to work, although no command prompt is obtained.
Port scan shows port 80 enabled on server.

Any ideas please.


























 
hi,
we are experiencing the same problem. did you resolve it? if so how?
Jen
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top