Enable Wyse ThinOS Support

[Conquested]

My company is using 2X ApplicationServer to publish applications and terminal server desktop connections. Everything works great from the 2X Client for Windows, Mac, and Android.

My issue is that we are adding 25 Wyse thin clients running the Wyse ThinOS. I have added the DHCP options for the Wyse devices and enabled Wyse ThinOS Support under the 2X Secure Client Gateway Properties.

The Wyse thin clients correctly connect to the gateway and prompt for the user credentials. Once authenticated, the list of connections are correctly presented. The problem is that none of the listed connections work. The all fail with the error message "Connection Refused." When I look at the connection settings on the Wyse thin client, under Host Names it is repopulated with "VM-#" where # is the number of the application or connection published on the 2X server. If I replace this VM-# string with the IP address of the terminal server, everything works correctly.

Anyone have any suggestions on how to get the 2X Wyse connection broker feature working correctly?

Thanks,
BJ Meyer

 

[MBearden]

BJ - were you ever able to get this working?

We are about to do a proposal for 2 prospects, each about 130 thin clients and this is a huge part of our deployment.

Any updates / guidance?

- Marcus Bearden

 

[Conquested]

So here's the update:

The problem was the configuration of the "direct connection address" in the gateway properties. Oddly, it was set to the loopback address of 127.0.0.1. I plugged in the correct IP and everything is working great.

2x Support was very helpful in finding the resolution. They mention that the Wyse support must use the direct connection method, because it doesn't have the full blown 2X client. That sent me down the path of testing to see if I could use the 2X client on a Windows machine, but change the connection method from SSL Gateway to Direct Connect. Sure enough, this would fail. This let me know that it was a configuration issue on the server.

So, if you have issue with your Wyse Connection Broker functionality, make sure you verify that you can connect via direct connect from the 2X client.

Additionally if you are using Wyse thin clients, you do not have to set the 188 DHCP option for the connection broker. You can also specify it in the WNOS.INI file. To use this file you must have an FTP server configured for Wyse use and the DHCP options set for the FTP server and credentials.

For generating the WNOS.INI file, I highly recommend using ConfGen: http://www.technicalhelp.de/modules.php ... oad&cid=15

This will allow you to control settings on the Wyse devices much like group policy does for Windows.

-bj

 

[aperello]

So here's the update:

The problem was the configuration of the "direct connection address" in the gateway properties. Oddly, it was set to the loopback address of 127.0.0.1. I plugged in the correct IP and everything is working great.

2x Support was very helpful in finding the resolution. They mention that the Wyse support must use the direct connection method, because it doesn't have the full blown 2X client. That sent me down the path of testing to see if I could use the 2X client on a Windows machine, but change the connection method from SSL Gateway to Direct Connect. Sure enough, this would fail. This let me know that it was a configuration issue on the server.

So, if you have issue with your Wyse Connection Broker functionality, make sure you verify that you can connect via direct connect from the 2X client.

Additionally if you are using Wyse thin clients, you do not have to set the 188 DHCP option for the connection broker. You can also specify it in the WNOS.INI file. To use this file you must have an FTP server configured for Wyse use and the DHCP options set for the FTP server and credentials.

For generating the WNOS.INI file, I highly recommend using ConfGen: http://www.technicalhelp.de/modules.php ... oad&cid=15

This will allow you to control settings on the Wyse devices much like group policy does for Windows.

-bj

Can you send any demo for the values we need in the WNOS.INI I have the FTP and want to try with some of them. This config Works also if the 2X server was a public IP address in a https protocol NOT VPN ??

Thanks !!