On Thu, Apr 25, 2002 at 01:15:47PM -0700, Dave Shiels wrote: > Charles Bowman wrote: > > It's my understanding of the LTSP documentation that thin clients are in > > the same building, and connected to the server by wires. I am wondering > > if LTSP could be used to connect geographically dispersed thin clients > > to a server. Most of the thin clients are within 10 miles of the > > intended server, but a few are 60 miles away. > > > > If LTSP is not appropriate, is there another way to solve the problem?
> Really location has nothing to do with it. If you by LTSP mean a chain of services like DHCP->TFTP->NFS->XDMCP, then all clients need to be on the same subnet as the LTSP server or you will have to exchange some of these services by other means. For example, you could have a boot-floppy (or use a local HD) with lilo and a kernel where lilo gives the kernel info on the IP, netmask, gateway on the local network and the IP of the (remote) NFS (and LTSP) server. In that case the DHCP and TFTP services was exchanged. If you have a dhcp server on the local network, I think you could use the "next-server" parameter to instruct etherboot to get the kernel from some other server (I'm not sure if etherboot has what is needed for this to work for servers outside the local network though). -- Hans Ekbrand
msg04736/pgp00000.pgp
Description: PGP signature
