Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
Linux is built to serve multiple users. Assuming that your network is secure, XDCMP should be able to handle your requirements (from memory, the security issue with XDMCP is that it transmits login passwords in the clear).
I don't know anything about windows ce, but you would need some sort of x-server running.
I hope that this helps and please post back the outcome!
Wow, that is what I call a great question. Is a real problem and I'm really looking forward to get a solution for it. Actually, here is my plan:
1. Customize a lightweight Linux distribution that connects through XDMCP automatically.
2. Install any Linux distribution on the W2K3 machine that fits your needs.
3. Perform a PXE installation on the thin clients.
Actually, this is the theory but I haven't tried to do it before. Righ now I'm working on it using virtual machines and I will contact you as soon as I make it work.
Distribution: Slackware, CentOS. Red Hat Enterprise Linux
You should check out the Linux Terminal Server Project which has created just what you are looking for. The Neoware clients, according to a cached article I found on Google, support the PXE the boot protocol. When this is enabled, they will download a Linux image from the LTSP server and then run Linux instead of Windows CE. All the apps run by the thin client will on the LTSP server with the thin client running a local X server.
avatarfx, please keep us informed about your progress with the virtual machines setup.
I'm also reading up on VNC. VNC is described as a way to "control" a machine from another machine. But I'm curious to know if it also lets you get online, run apps, etc on the remote machine. If so, the configuration seems very straight forward. If anybody has used VNC, please explain what it does.
Regarding the VNC, I would really suggest to look for XDMCP instead because VNC generates more network traffic than XDMCP (VNC is multiplatform, it sends every screen as a mapped image while XDMCP just send the X server calls and they're rendered locally).
I keep working on this. By the way, do you know how much HDD & Memory space do you have on the thin clients? I'm trying to customize DSL (Damn Small Linux) for the thin clients but it would be useful if I know how much space can you use. For the server, I'm actually trying my Fedora Core 5 box but actually almost any distro would do the job.