Slashdot Mirror
"Thin Clients" that Support Linux and Windows?
An Anonymous Coward asks: "I have been searching for a thin
client that accesses both Linux and Microsoft systems and am dismayed
to find that most thin clients only support MS RDP or Citrix ICA.
Yes, I know that any old PC can be made into a 'thin client' and that
X-stations have existed for many years for Unix based systems, but I
will be buying new hardware for a new office that needs mainly
MS connectivity. Since I am also including a Linux server or two on
the network and think that Linux has a chance on the desktop, I would
like to purchase thin-clients that can connect to both instead of being
locked in by design from the start. This way, I can eventually move users
onto Linux desktops in the future without replacing anything on the
desktop." How hard would it really be to add on X11 functionality
to an existing Windows thin client? While the realities of the
current market makes finding such products unlikely, maybe if we can
drum up the interest now there may be hope to see something
like this in the future.
"I have a chance to buy top of the line hardware for this
project and am looking for something that has a small footprint,
no moving parts, ICA client or MS RDP, Linux connectivity
(embedded X server?), a real manufacturer and a nice design that
would not look out of place in a brand new, designer furnished
office.
The Compaq
Evo T20 serves my current needs perfectly, except that it
forever locks me into Windows on the desktop, Does anybody have
alternatives they can suggest?"
To have a windows client appear as an X11, check out Hummingbird's Exceed. Rutgers U had labs full of Windows desktops with Exceed running on them. Worked quite well.
Yep, I never spell check.
More incorrect spellings can be found he
I've been keeping an eye out for one of these at a decent price...
The IBM Network Station 1000 Model 8362 is a PowerPC-603-based thin client with support for VT emulation, X, ICA/Citrix, local Java apps, 1600x1280x8bit graphics, sound.
The complicated part is that they were designed to be slaved off of a Win2k/NT or AIX box, but people have figured out ways around that for the most part.
Best of all, they're silent, too.
They seem to go on E-Bay for around 300Eur (These guys have them for 450Eur with a 1yr warranty. [for those not in Europe, that's $270 and $400 US, respectively]
"don't fall into the fallacy of believing that Perl can solve social problems. Maybe Perl 6 can, but that's a ways off"
I am in the planning stage of an internet cafe with similar needs. The thin clients that have caught my eye are the IBM NetVista N2200e or NetVista N2800e. Spec Sheets say it will do everything you've asked...
Price is probably a bit of a kicker unless you order 50+... good old IBM.
--
$Canada = $US;
$Canada =~ s/house/igloo/g;
If by affordable, you mean priced inline with Windows-only Citrix-based terminals, like the Wyse WinTerms which start around $300, the options are slim. The best thing I came up with during my search would've been to take a New Internet Computer ($199) and hack up the boot CD with some custom software.
The downside to the NIC, of course is twofold. First, it will involve custom, non vendor-supported work on your part; secondly the NIC relies on a CD drive for the OS.
I looked, briefly, into assembling small, custom units, using 16 or 32MB IDE flash cards, and found that to compete with off the shelf units on price, you'd have to move to a much larger size and the appearance of a hacked up unit. To compete with them on size, and you'd have to go to single board computers with custom casings, and lose any sense of price parity.
I could suggest the possibility of getting Xterms, and then running a Citrix client from the Linux system, but that's too ugly. Not to mention that Xterms are quite a bit pricier than the winterms.
Looking at the winterms, adding xterm functionality to a box that alread has RDP, ICA, telnet and internet explorer would be a relatively simple task and, even if offered as an upgraded model, would probably help the marketing effort, I get the feeling that their licencing agreement for Windows RDP (or the WinCE the unit's based on) probably prohibits them from integrating it with a X11 based client.
Of course a winterm could connect to a unix server, if you want to run Solaris or AIX instead of Linux, you're free to get a citrix server for those systems at the same low-low price of the Windows servers. It's either that or hope somebody can reverse-engineer RDP and get a server working on Linux.
my sig's at the bottom of the page.
There is a Linux ICA client, which would allow you to deploy X terminals and present ICA clients to them from a Linux concentrator which would make the ICA connections to your WinNT/2K box. The disadvantage of this is the need to deploy both X and ICA to every client when you only need one or the other in practice normally. On the other hand, if you actually have the option of presenting Linux as an alternative, you can run your Windows apps in Application Publication mode and simply present them inside a Gnome or KDE environment on your X terms.
That makes a big difference. HP NetVectra's and a bunch of Wyse WinTerm's support RDP, ICA, and telnet (and ssh). I think HP's higher end models may even do X sessions. It's not hard to find them at all....
Then again, you could just get Citrix for Unix, and not worry about a thing (which maybe be in your best interests in a larger environment...)
eXceed does some neat things with automagically sending X apps to windows clients. It isn't cheap, but it is a nice X Server.
Here is one! http://www5.pc.ibm.com/se/products.nsf/$wwwovserie s/netvista+thin+client+n2200+family
I can't quite tell from the question, but: could VNC help here? Since there's a VNC viewer and server for almost every platform, you can be wonderfully agnostic about what you deploy.
One potential software part could be the use of rdesktop, found at www.rdesktop.org. It's an RDP4 client for linux and many other unices.
As for thin clients, I would certainly go towards the IBM route, mostly because IBM IMHO has shown itself to be linux friendly
-- Who is the bigger fool? The fool or the fool who follows him? --
Last time I checked, NCD, Wyse, Tektronix and IBM all sold combo X/ICA terminals. X for the Linux, ICA for the Citrix stuff and, increasingly, direct support for Windows Terminal Server.ther than Sun
I'd be surprised if anyone in the hardware X terminal business other than Sun didn't also support at least ICA at this point.
Another option everyone has forgotten these days is Tarantella, the SCO product, which runs as a server both under Unix (including Linux) and on Windows and can serve either kind of application via RDP and X11 if I recall.
NCD has made combo machines for years we use several here at work and they work fine (though we are 99% Citrix based). Their NCD Business Network Computers line looks like exactly what you need though I don't know the price.
Charles
Neoware sold many X/ICA thin clients. I think they currently have one that runs linux as it's OS as well as ones that run win2000. I haven't been watching them as much lately as I've been replacing my neostations with PC's running Linux. Neoware
Exceed also does this. You need windows on the box, but I see no reason why you cannot have CITRIX pull up a windows desktop and then have that pull up an x session through exceed.
Only 'flamers' flame!
Assuming you go with something that can run either windows or linux as an OS:
;)
Citrix has an ICA client for both Windows and for Unix. I have mainly used the one for Linux, and as far as I can tell, it works exactly as well as the one for Windows. I doubt there is much difference between the price for either.
If you want to use Windows as a host OS, that is a decent chunk of money right there. You can certainly run X11 apps to displayed to windows using StarNet's X-Win32, Hummingbird's eXceed, or WRQ Reflection X. The last one I know supports accelerated OpenGL and I don't think the other two do. If that's important for your type of work, take that into consideration.
If you really want good remote X11 support, though, do not use a Windows X server. Speaking from personal experience, they all have flaws. Use Linux as host OS, get the Citrix ICA Linux client, and just run X remotely when you need to. Best price/performance for sure. Plus, it gets the worker bees accustomed to the Linux desktop while using the Windows one. Makes it easier for the bait'n'switch later.
Just curious if there exists any instuctions on how to get exceed setup to connect to the Linux X server, I do it all the time here to connect to solaris boxes, but the same connect strings adjusted to to connect to the linux xterm don't seem to work.
Power Corrupts,Absolute Power Corrupts Absolutely, leaving one person(group)in charge is absolutely corrupt.
But is this the practical choice? For about the same amount of money, you can buy a Celeron-based system and install the requisite software. And you end up with hardware people know how to fix if it breaks. Unless your server is NT or AIX, you'll have to do some hacking either way, so Cost of Ownership isn't an issue. The IBM does have nice graphics and no noise -- but does that outweigh the other factors?
Please convince me that I'm wrong. I rather want to be.
Here's what I used:
Costs ended up being about $120 for the motherboard, $40 for the CPU, $15 for the heatsink, $50 for the disk on module, and $50 for the case, so ~$275, plus a keyboard and mouse, and the performance blew away the NetVista 2200 that I had been using.
For software, you can run Linux on the machine and use Citrix/ICA client or Terminal Server with rdesktop. The machine is fast enough you could run Linux locally from a remote NFS file system, or you could just use it for a display. The Linux Terminal Server Project has a lot of information about setting this. You might also want to look at the Diskless Windows Cookbook.
IBM Netstations should be able to do X, ICA, and perhaps RDP(I haven't used one in a year or so, but I'd imagine that they'd have RDP supporty by now). At one point we had about 50% of our office running on these. Over time our users' needs have changed so we've migrated away from these, but some of the other departments in my organization have a decent install base of IBM Netstations. The only gripe we had about them when we used them was the video output quality was less than great. This has probably been fixed by now though. Another option, that I have zero experiance with, might be Sun's SunRay or whatever there thin client is called. I think you can get an ICA client for it(though I have my doubts about being able to find an RDP client) and it does support X. The SunRay may have a fan also, which violates the no moving parts idea. IIRC a lot of the 'Windows' thin clients(Wyse Winterms, etc) have a fan, so you may be stuck with fans anyhow. One thing I have noticed about thin clients(and cheap 'PCs' like the Compaq iPac) is that even though they may have no, or very few, moving parts that the failure rates are still about the same as a full PC. They always seem to have cheap power supplies that give out, especially if you have crappy power at your location). You didn't mention the size of this rollout, but if it is a large one you should take a good look at the management options for the clients you buy. Some have great centralized manament options and some have none. This can make a big difference when you find you need to upgrade firmware or change the configs on a bazillion clients. Good luck with your rollout!
Why not have a X-Server running on that Citrix or MS desktop server ? Just 'emulate' the linux part using what you already have.
-Billco, Fnarg.com
www.tuxia.com has a thin-client solution. Linux embedded OS, native X Windows support, Citrix Metaframe optional.
I've seen these guys at LinuxWorld Tokyo and some other shows. They have some snazzy looking devices that will fit any "designer office". Unfortunately, last time I talked to them, they were turning more to set-top box development.
Can't hurt to take a look.
Sig?
Sigue Sigue Sputnik!!!
Use a small Linux distro if you don't want to but any of the precooked terminals.
TinyX handles X for Linux, Unix and BSD
RDesktop handles Terminal Services for NT4TSE and Windows 2000
The Metaframe Client does, obviously, Metaframe on your Windows and Solaris app servers.
The right link.
Sig?
Sigue Sigue Sputnik!!!
According to this HowTo, you can have the ThinkNIC boot directly from the net without making or using a CDROM.
Something I'd been doing when I didn't want to destroy a Windows installation that I might need at a later time is setup a VNC config file and run the following line in my win.ini file:
/config configfile
:-)
shell=c:\software\misc\vnc\vncviewer.exe
This worked for me in a couple of ways:
1) the computer boots up faster (no explorer.exe to load) and is more stable, no explorer to crash.
2) The vnc connection settings are all stored in the config file, and I run VNC full-screen, so it's transparent to the user that it's even a virtual desktop.
FWIW, YMMV.
If liberty means anything at all, it means the right to tell people what they do not want to hear. -- George Orwell
that should be your SYSTEM.INI file, not WIN.INI.
Sorry.
If liberty means anything at all, it means the right to tell people what they do not want to hear. -- George Orwell
Try Century Embedded Technologies. They have a thin client solution. I think a download too. Linux-based.
http://embedded.censoft.com
my mom dont like 20 second pauses:
she suggested 2diskxwin, tryin to be helpful
http://freshmeat.net/projects/natld
Check out rdesktop.org for a GPL RDP client that allows you to connect to a Windows Terminal Server.
http://rdesktop.org