[THIN] Re: Clients cannot connect to published app.

Rick,

Yes, I agree that it has to be a browsing issue.  I have already tried
to telnet to port 80, and every other port I set the XML Service to
listen on.  I can successfully telnet to that port.  When I try to
initiate a session to a published application, the system is in a
TIME_WAIT state when trying to connect to the XML port.  It appears that
the server is not sending back any information that the client is
requesting.

I already know how the client tries to get a published application.  My
problem is what is causing this?

Like I said, there is no firewall at all (software or hardware) in
between the client and the server.

Has anyone experienced this at all?

Thanks,


CHRIS LYNCH -  MCSE, CCNA, CCA
NETWORK ENGINEER - INFORMATION TECHNOLOGY
NRT Incorporated, 27271 Las Ramblas, Mission Viejo, CA 92691
Chris.lynch@xxxxxxxxxx  Tel 949.367.3406



-----Original Message-----
From: Mack, Rick [mailto:RMack@xxxxxxxxxxxxxx] 
Sent: Friday, July 05, 2002 3:15 PM
To: 'lynch00@xxxxxxx'
Subject: RE: [THIN] Re: Clients cannot connect to published app.


Hi Chris, 
Connecting directly to the server doesn't require any ICA client server
browsing. If you're connecting to a published application, the ICA
client has to find any metaframe server, get redirected to the data
collector for that zone and then query the it to get redirected to a
server hosting the published application.
The 6.3 clients use TCP/IP+HTTP by default. So the client needs to be
directed to one of the servers in the zone, either by defining a server
address list, or by having a DNS entry in your domain (ica) which points
to your metaframe servers. 
If you don't have a server list defined on the client, or an appropriate
DNS entry, nothing happens. 
Another essential component of the published app resolution process is
the XML service on the Metaframe servers. If this isn't working, or
you've changed the default port address (80) to something else, things
won't work. Try "telnet metaframe_server_ip 80, and hit return a few
times, you should get a response. If you've got IIS running on the
Metaframe servers as well, check the XML service is running (net start)
or if its running on a non-standard port address (defined at metaframe
installation time) then the ICA clients will need to be changed
accordingly.
Regards, 
Rick 
Ulrich Mack 
rmack@xxxxxxxxxxxxxx 
Volante Solutions 
18 Heussler Terrace, Milton 4064 
Queensland Australia. 
tel +61 7 3246 7777 



-----Original Message----- 
From: Chris Lynch [mailto:lynch00@xxxxxxx] 
Sent: Saturday, 6 July 2002 5:26 AM 
To: thin@xxxxxxxxxxxxx 
Subject: [THIN] Re: Clients cannot connect to published app. 


Anyone have any suggestions? 
Thanks, 
CHRIS LYNCH -  MCSE, CCNA, CCA 
NETWORK ENGINEER - INFORMATION TECHNOLOGY 
NRT Incorporated, 27271 Las Ramblas, Mission Viejo, CA 92691
Chris.lynch@xxxxxxxxxx  Tel 949.367.3406 


-----Original Message----- 
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Chris Lynch 
Sent: Wednesday, July 03, 2002 12:59 PM 
To: thin@xxxxxxxxxxxxx 
Subject: [THIN] Clients cannot connect to published app. 


  
-----BEGIN PGP SIGNED MESSAGE----- 
Hash: SHA1 
I have a test server that is running Windows 2000 Server with Service
Pack 2, SRP1SP2, MetaFrame Xpe with SP2/FR2, and I have a problem
connecting clients to published apps.  Users can make a connection to
the server using RDP or ICA, but only a Custom application connection TO
THE SERVER ONLY.  Even if they specify an application to connect to in
the Custom ICA Connections, they receive "I/O Error."  The ICA client
ver is 6.30.1050
Like I said, I can connect directly to the server, but not to a
Published App. 
This server is in a workgroup, and I do have Local users and groups
configured.  I remember seeing an article on Citrix talking about there
are some missing REG keys for the ICA protocol, but I cannot find it
anymore.  I don't remember if that article deals with this issue.
I do have the FR set on the server.  I can manage it via the Citrix
Management Console.  But my test users get the infamous "I/O Error". 
Also, they are not going through a firewall, they are on the same IP
subnet, I do have the XML Service listenng on the correct port, and the
clients are configured with the correct port for the XML service (which
is the default).
Anyone have any suggestions? 
Thanks, 
CHRIS LYNCH -  MCSE, CCNA, CCA 
NETWORK ENGINEER - INFORMATION TECHNOLOGY 
NRT Incorporated, 27271 Las Ramblas, Mission Viejo, CA 92691
Chris.lynch@xxxxxxxxxx  Tel 949.367.3406 
-----BEGIN PGP SIGNATURE----- 
Version: PGP 7.1 
iQA/AwUBPSNXnfl56xfvzmMfEQIOQACeLTt+AgAsHH+cbooU7xit98XjUxQAn0oH 
sCt4EoRbkE+uQ0px8GzQHRD/ 
=f9cK 
-----END PGP SIGNATURE----- 





=================================== 
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link. 
http://thethin.net/citrixlist.cfm 





=================================== 
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link. 
http://thethin.net/citrixlist.cfm 



**********************************************************************
This email may be confidential and/or privileged. Only the intended 
recipient may access or use it. Any dissemination, distribution or
copying of this email is strictly prohibited. If you are not the
intended recipient please notify us immediately by return email and
then erase the email.

We use virus scanning software but exclude all liability for viruses 
or similar in any attachment or message...,..,..,.


**********************************************************************





===================================
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link.

http://thethin.net/citrixlist.cfm

Other related posts: