> From: Brian Fahrlander [mailto:[EMAIL PROTECTED]] > Sent: Thursday, June 27, 2002 1:53 PM > >>> Last year our school added a ltsp server to our pre-existing >>> Linux network. There were around 20 workstations on the ltsp >>> server. It worked well, until all 20 machines were being >>> used at the same time, then things slowed down. This summer >>> I have acquired three HP netservers. My plan is to use the >>> Netservers to handle 5-10 ltsp terminals each -- speeding >>> things up. However, configuration comes into question.
>> What is the config of your server? It might be cheaper to >> just beef it up. A decent server should be able to handle >> more than 20 workstations. > But before you get worried about running out of network > resources, have an independant network specialist put his > troubleshooting gear on the net. 100-base-T is apparently a > single bad connection, sloppy join or whatever, and you're > back to 10-base-t. We nearly tripled our bandwidth when > adding a Cisco router/switch/hub. It was really worth the > money! Couldn't agree more, but would add - a bad NIC can bring a network to its knees. I had a situation where, 3 seconds after powering up a particular computer, no one could log on (find the Samba PDC), and anyone who was currently logged in lost all Share connections - it was pure dumb luck that I discovered it was this one computer as quick as I did. The funny thing was, this NIC worked just fine with a Windows 2000 Server. Go figure. Charles ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _____________________________________________________________________ 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