When the thin client boots up and a screen appears, as was explained, all operations are on the server. If you get a window you can then ssh onto the thin client and run applications local to the thin client thus alleviating some of the work from the server and traffic on the local network.
ssh doesn't just work though. (Does anything to do with computers, ever just work) You have to create an account on the server for some user and mount the /home system on the thin clients, enable NIS andalso copy ssh encryption codes into the appropriate directories.
The instructions on how to do this are in the LTSP wiki on how to run local applications.
Ragnar Wisloff wrote:
Starla Williams skrev:
I have a small network of computers running SuSE Linux 9.1 and LTSP 4.1. I installed LTSP and ran the setup stuff, and the workstations are able to get their IP address, kernel, and filesystem without any problems. I can't get telnet, rsh, and ssh to work though. The workstations can connect to the server without any problem, but the server can't connect to any of the workstations. I've tried all telnet, rsh, and ssh and all three return "Connection refused". I tried logging onto one of the workstations and it said that the programs were running and that they were listening to the correct ports. Hosts.deny is empty. If anyone knows anything else I could check, I would really appreciate it.
I think there might be a slight misunderstanding here about what these workstations actually do. When you log into one of them, though you see everything on the screen as you would on a "normal" computer, all you see is generated on the server and sent across the network to the thin client. It's only the screen image that is shown on the thin client's display, no user space applications are actually running on them. The only things (unless you do something fancy) running on the thin client are the Linux kernel and the X server.
So it is perfectly normal that you cannot connect to the thin clients, they have none of the services you mention. The server probably runs them, and those services are what you see when you log on to a thin client and check for them. A bog standard LTSP thin client only has port 6000/tcp open, which is used for communication with the X server.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
