On Thursday 26 January 2006 14.40, you wrote:

I appreciate your answers, i didn't explain any scenario. Let's say i have some old machines and a new one, i want the old machines to act as simple terminals against the new one working as server. Is it possible? L.

(I forwarded this to the list, as it may help other people also) Yes, there are 4 different ways: 1) XWindows Remote. 2) VNC Via inetd 3) VNC with user sessions 3) FreeNX and NXClient. I assume that all the clients (the Old PC's) are within the same network and use 10mb ethernet cards (Old Pc's right?) I also assume that you have crossed out running applications locally, and even in mixed mode (Internet browser locally, and Office remote). XWindows Remote ============ This method is the most network intensive. This method requires the most CPU from the Old Pc's. Using this method, the user actually gets the login scrren from your server. When the user logs out all programs are stopped and all resources are freed. When a user logs out all programs are stopped and the resources are freed. (ie. no suspend/resume functionality) VNC in general ========= VNC is less network intensive than XWindows, but more intensive than Freenx. VNC requires memory on the server to simulate an X-Windows display.... VNC requires the least processing power on your Old PC's The VNC screens are of a lesserquality than the XWindows, and FreeNX, and are less responsive. The VNC Client can be run Linux,Windows,Mac,etc. The Session can be persented in a window or as full screen, you can even switch between the 2 modes. VNC via inetd ============ With this method the Users connect to the with: server:1 for 1024x768 size screen server:2 for 1280x1024 size screen server:3 for ...... When they connect they get the standard "Login Screen"from the server. When the connection breaks, the window is closed, or the user logs out all programs that are running are stopped, and all resources are freed. ie. no suspend/resume functionality. VNC with User Sessions =============== Using this session each user get an separate address to connect to: server:21 --> tom server:22 --> dick server:21 --> harry There is no need to use the standard login screen, as VNC does the user/password checking, (Albeit in a non secure method!). When the User closes the window, his entire X-Windows session keeps running on the server, and he can reconnect to it (even from other machines) to continue what he was doing... If he chooses to log out, the X-Windows Session is closed, and most of the resources freed, (It holds the In Memory Screen with a "Login Screen" running in background). FreeNX ========= This method uses the least network bandwidth. This method is the most responsive. This method allows you to use the local printer, Hardisk, CD-Roms, and even the local Soundcard. (Although I've only managed to use the local Disks to work until now) It Requires more CPU from the OLD Pc's than VNC. Don't have comparison stats between X-Windows remote and FreeNX. The Clients can run on Linux,Windows,and Mac in Either windowed or Fullscreen mode. You can changed the size of your desktop by simply resizing the window! You can suspend a session and resume it latter from elsewhere, (I've not managed this either so I cannot comment on the resource usage during the suspend phase). My Experience is that the administrator must go delete "dead" sessions periodically, (although this could be automated). Personally, I setup both vnc via inetd and FreeNX server, as I'm in the process of switching over from VNC to FreeNX. And as commented before I'm still learning NX. Pick your poison. Please note that I use both vnc and freenx to securely access the machines remote via internet. And I don't have a customer who is actually using the server via the Old Pc's (thin clients) yet. Jerry P.S. You do know that there are ISO images out there that you can boot your Old Pc's from and connect via vnc/nxClient/X-Windows remote. These iso usually let you install from CDRom to hardisk, and are