> 2. LTSP is not well adapted for the enterprise from a > networking point of > view. It uses DHCP to provide important parameters such as > the image to > boot on the clients. LTSP is well adapted and tested for > workgroups on a > single subnet. It's best to keep it that way for the sake of > bandwidth, > unless you are using compression of some sort. What impact would it > otherwise have on overall network architectures?
I serve 3 subnets (physical networks) from a single dhcp/ltsp server this does require a router that is able to forward dhcp requests to the network that the DHCP server but in an enterprise environment this shouldn't be hard to come up with. > It's one of my personal goals to try and figure this out over the next > year. Unfortunately, I am just a software engineer and a programmer. > This will take serious consultation with a network engineer. > My skills > are more rudamentary in that area. One of your network engineers should be able to help you with the above problem. Matt _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _____________________________________________________________________ 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.openprojects.net
