Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2569
  • Last Modified:

WYSE ThinOS and Citrix XenApp

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
Freda Driscoll-Sbar
Asked:
Freda Driscoll-Sbar
  • 6
  • 2
1 Solution
 
Dirk KotteSECommented:
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
 
Freda Driscoll-SbarDirector of System OperationsAuthor Commented:
Thanks. I'll give it a shot.
0
 
Freda Driscoll-SbarDirector of System OperationsAuthor Commented:
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
Lessons on Wi-Fi & Recommendations on KRACK

Simplicity and security can be a difficult  balance for any business to tackle. Join us on December 6th for a look at your company's biggest security gap. We will also address the most recent attack, "KRACK" and provide recommendations on how to secure your Wi-Fi network today!

 
Freda Driscoll-SbarDirector of System OperationsAuthor Commented:
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
 
Dirk KotteSECommented:
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
 
Freda Driscoll-SbarDirector of System OperationsAuthor Commented:
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
 
Freda Driscoll-SbarDirector of System OperationsAuthor Commented:
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
 
Freda Driscoll-SbarDirector of System OperationsAuthor Commented:
Researched and re-ordered the wnos.ini file statements, then tested successful.
0

Featured Post

Lessons on Wi-Fi & Recommendations on KRACK

Simplicity and security can be a difficult  balance for any business to tackle. Join us on December 6th for a look at your company's biggest security gap. We will also address the most recent attack, "KRACK" and provide recommendations on how to secure your Wi-Fi network today!

  • 6
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now