Solved

WYSE ThinOS and Citrix XenApp

Posted on 2014-04-02
8
2,296 Views
Last Modified: 2014-04-22
Hello.

I have a WYSE thin client S10, firmware 7.1.22 that I'm trying to get onto a Citrix XenApp 6.5 farm. The units are getting "Connection Refused" when attempting to connect. INI file below:

IcaBrowsing=HTTP

CONNECT=ICA \
Host=192.168.1.26 \
BrowserIP=192.168.1.50/Citrix/xenapp \
Description="XenAPP 65 “ \
LocalCopy=no
0
Comment
Question by:Lee Seeman
  • 6
  • 2
8 Comments
 
LVL 24

Expert Comment

by:Dirk Kotte
ID: 39974186
are you able to connect with a other device and the pnagent/receiver to the server?
I think you need a WebInterface Site for receiver to connect with the thinclient (because there is a path behind the IP)
If the thinclient is able to connect the XML service directly, you should need no path. (try the IP only)
0
 

Author Comment

by:Lee Seeman
ID: 39974823
Thanks. I'll give it a shot.
0
 

Author Comment

by:Lee Seeman
ID: 40000142
Unfortunately we've run into a new, wider problem with our WYSE units. For some reason they are connecting intermittently to our FTP server. This is how it works:

Site A has the Citrix array behind a SonicWall router
Site B had the IIS FTP server which fed the INI file to the S10 units

Units outside Site A CANNOT connect to the FTP server or the array consistently. So we moved the WNOS files to Site A to be served locally on a FileZilla FTP server. We are watching connections to the server, however the units are still not consistently getting connected to the FTP or the array.

NOTE: S10 units INSIDE the Site A firewall are working perfectly, every time. There is no rule we see on the firewall that would block FTP or cause intermittent connectivity with VPN traffic (we are allowing "All" to/from the VPN). The only two things that changed in our environment recently are: A few weeks ago we configured LDAP/SSO on our firewalls, so HTTP traffic is being authenticated across the same tunnel. Also, we put a pre-release firmware on the router at Site A to address some other issues. These two changes are the only ones that fit the timeline.

Any thoughts?
0
Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

 

Author Comment

by:Lee Seeman
ID: 40000576
We are running a Citrix XenApp Web interface server and other non Wyse devices connect flawlessly. The Wyse terminals can connect to the old 4.5 farm, but not the 6.5 farm with same thinos config.
0
 
LVL 24

Expert Comment

by:Dirk Kotte
ID: 40001181
The wyse terminals from side B cannot connect to XenApp6.5?
There are no problems from Side A.
Do I understand that rightly?
Check if Port 2598 and 1494 are open at the firewall.

If all wyse terminals are unable to connect the xenapp 6.5 Farm ... possible they try the old browsing (port 1609 I think) which is no longer supported.

You should try to use PNAgent functions with wyse devices.
0
 

Author Comment

by:Lee Seeman
ID: 40006754
Just to clarify this Question:

WYSE devices running firmware 7.1.122 configured and working for Citrix PS 4.5 are not migrating to XenApp 6.5 smoothly with current WNOS.INI

Current WNOS.INI
;connect=ica \
IcaBrowsing=HTTP 
;description="Wellmore Desktop" \
;icon=default \
;username=" " \
;password=" " \
;browserip=192.168.1.26 \
;application="Wellmore Desktop" \
;autoconnect=1 \
;reconnect=0 \
;TcpTimeOut=200 \
;Sessionconfig=all unmapusb=no mapdisks=yes \
;IcaBrowsing=UDP \
;Seamless=yes \
PnliteServer=http://CX-F2-WI ReconnectAtLogon=2 ReconnectFromButton=2 Timeout=30 AutoConnectList="Wellmore:WellmoreDesktop"
Desktop" Timeout="30" \ 

Open in new window


The WYSE device boots up and ask for auth., then presents all published apps/desktops and we have to scroll to page 2 of apps and select Wellmore Desktop to connect to Citrix desktop.

A.) We would like to have it auto-connect to published app/desktop=WellmoreDesktop
B.) We want to lock down the ThinOS environment so settings do not get tampered with, or other published apps from  being accessible.

Thanks,
0
 

Accepted Solution

by:
Lee Seeman earned 0 total points
ID: 40007289
I resolved this by reordering my wnos.ini and adding the below at the top of the execution order:

PnliteServer=192.168.1.26 AutoConnectList="Wellmore:wellmoredesktop" ReconnectAtLogon=2

Open in new window

0
 

Author Closing Comment

by:Lee Seeman
ID: 40014352
Researched and re-ordered the wnos.ini file statements, then tested successful.
0

Featured Post

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

What do we know about Legacy Video Conferencing? - Full IT support needed! - Complicated systems at outrageous prices! - Intense training required! Highfive believes we need to embrace a new alternative.
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
Hi friends,  in this video  I'll show you how new windows 10 user can learn the using of windows 10. Thank you.
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question