Question about WYSE S10 (90210501) Network Terminal
This is a thin client that was connected to my network and working.
I replaced it with a Wyse V30L and was going to use this in a different app. I "G" the unit and set it up just as I have in the past. When I went to connect RDP a pop up screen comes up.
Remote Desktop Conntection
CETSC and will not connect.
The thin client can ping the server.
Any help would be appriecated. Thanks
a 6ya Technician can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repair professionals here in the US.
click here to Talk to a Technician (only for users in the US for now) and get all the help you need.
Posted on Jan 02, 2017
SOURCE: Wyse S30 thin Client with Ubuntu
I played with those a lot with the LTSP and finally made it work...
All in all, the problem is that the X.org cannot autoconfigure the graphic chip of this client. On ubuntu 7.10 you need to force it to use the amd driver and cannot do it from the LTSP.conf file.
In your LTSP.conf file, you have to point to a xorg.conf file specific for your s30 thin client (I called it s30xorg.conf). Then you need to build this xorg.conf file (lots of help on the net on how to do this) and place it in the right folder. (The folder is probably not the same than on my system but it should be pretty obvious or at least written in the manuals or help files where to pu it). In this xorg.conf file, you will need to specify the amd driver and some standard vesa resolutions and refresh rates (also widely availavble on the net). Then dont forget to rebuild your LTSP image with those new files in the tree.
If I remember correctly you will also need to disable the ubuntu splash screen from another config file somewhere... I am sure you will find which one.
Let me know if you can make it work... if what I said is total gebrish, go on reading everythin you can find on the net until you understand what is here.
Posted on Dec 04, 2008
This is caused by the terminals default display resolution (or the resolution that it was set to in its previous environment). The easiest way to get a display, would be to use a different monitor with a higher range of supported resolutions.
Fingers crossed the previous wnos.ini file would allow a G-key reset. If so, just hold down the G key when the terminal is booting, and it will reset to factory defaults. This might allow your monitor to work. (I think the default resolution is 800x600)
The problem you have is that the terminal might be locked down via the .ini file. So changing the configuration might be difficult. You could use a program like Wireshark to perform a network trace, this would tell you where the terminal is looking for it its wnos.ini file.
Then you will be able to setup a new wnos.ini on an FTP server set to the IP address(and path) the terminal is looking for, and this will allow you to set your own configuration.
Posted on Jul 07, 2009
The Wyse S10s require a firmware update to connect to Windows Server 2008. This is due to lack of support for RDP 6.1.
The update I've found to work best is 22.214.171.124.
The only way to get this update is to contact Wyse. However, I have deployed it on numerous clients (our entire base is S10s) and had great success.
Posted on Oct 07, 2009
Tips for a great answer:
Mar 18, 2013 | WYSE Winterm S30 Thin Client - Thin Client...
Mar 20, 2011 | WYSE Winterm V30 Thin Client - Thin Client...
Dec 03, 2010 | WYSE R90LE Thin Client 90952571L Network...
Jun 01, 2010 | WYSE S10 (90210501) Network Terminal
Jun 16, 2009 | WYSE S10 (90210501) Network Terminal
Apr 07, 2009 | WYSE S10 (90210501) Network Terminal
Nov 12, 2008 | WYSE S10 (90210501) Network Terminal
Feb 11, 2008 | WYSE S10 (90210501) Network Terminal
423 people viewed this question
Usually answered in minutes!