I'm not sure what you mean about there not being an issue with Paradise disconnecting. If I pull the internet access ethernet cable out from the spaghetti of switches that is our network, it recreates one of the "no one can log on" scenarios I've been randomly frustrated with from time to time. On Thursday we had another such out... all morning. This meant I had the whole school cycle through my IT classes with no one able to log on to any computers and I had to quickly come up with alternative / back up lessons. Apparently this was one of the days when the very busy network guru was able to make an appearance, but I never saw him. He instead talked to the school secretary I'd asked to call him. After time tinkering with the radio transmitter / hub / modem thingie at her end, he satisfied her by concluding that "Paradise is down today. Should be back by 11:30" and left. :-/ So anyway, like I said, if I pull out the internet ethernet cable from the switches providing out LAN, then the LDAP seems to bawk and no one can log on until I put the internet cable back in again (single ethernet cable which goes to a radio reciever, getting a direct line from the radio hub from over the road). This is why am pretty sure that Paradise is an issue and that whenever we get failed connection to them, we have a failed LDAP situation in our LAN... the internet being the initiator for LDAP to go down. Terminal clients I did consider earlier as well. ...But are they really faster? Sometimes we do some heavy stuff like 3D graphics and so forth. I wouldn't like a situation where one central computer was doing all the real work and the whole network slowed down for the priority queue. Aside from the fact that I originally set up the boxes before a network was even in place, this is one of the main reasons why I summised a good scenario would be to simply have the /home dirs shared with each computer accessing its own programs and doing its own work. ...was I mistaken in the speed factor? I concluded it was so when people said of thin clients "they don't even have to be that powerful - you only need the middle one to be good". Certainly maintaining the installation of one computer would be easy but not at the expense of processing power. Please tell me if I'm wrong on this issue. Lance. Ben - dadstheword777 at ihug.co.nz wrote: > hi Lance > You will most likely find that Paradise hasnt actually > hasnt been disconnected as thought but that the LAN that LDAP > & Inet access both use has fallen for some reason. > Unlikely to be some added application or config. > Have you considered using a few terminal servers and setting > up the rest of the network as terminal clients? > It would simplify things and make the computers run faster (depending > on the server speed, ram, scsi ) etc. > LDAP just seems wrong to me given what the computers are being used for. > Thats just an opinion though and I'm happy to be wrong or corrected! > At least with a terminal server/client setup your using the full > potential of > Linux and it multi-user capabilities and the true power of linux while at > the same time maxing the resource capabilities making everything > work faster, safer, and more reliable! > > Just a thought, > Here is a link for Terminal server network for schools that may be of > interest > > http://www.k12ltsp.org/ > > Yours Ben > :-) > > > > klug.member.lancer at xoxy.net wrote: > >> Thanks for your reply. >> >> The original guy who set us up recommended LDAP over NIS. When I >> asked for some documentation on, say, how to add another computer if >> I needed to, he directed me to >> http://www.linuxhomenetworking.com/linux-adv/ldap.htm >> >> Are there any real reasons to choose one over the other? At least I >> now appear to have two guidelines to try out, and certainly I want to >> trial this to make sure I can do it before bawking up the real Mcoy. >> >> One of the more serious problems that is / has been occurring is that >> if the internet service provider (Paradise) gets disconnected, the >> entire LDAP driven LAN fails along with it, resulting in no one being >> able to log into any computers for even so much as using a word >> processor (not a good look for me in front of the whole school). I'm >> not certain whether this would have something to do with standard >> LDAP misconfiguration or whether the network guy has put something >> extra of his own in place "for security reasons" which he hasn't told >> me about and which may be falling over once the internet link fails. >> >> Do any of you network gurus out there have an incling as to what >> might be causing this and how to tweak it right? >> >> Any ideas on things which I should check? >> >> Lance. >> >> >> Nathan Cook - nathan at coast-computers.co.nz wrote: >> >>> You will need to setup a NIS server and then the NIS clients. It's >>> too much detail to go into here but have a look here: >>> http://www.tldp.org/HOWTO/NIS-HOWTO/index.html >>> >>> There is plenty there to keep you going for a few nights, I would >>> set up 2 PCs to test and run through a few scenarios before going >>> live, I can if you like lend you my spare PC for a few weeks if need >>> be, it's not much but will do the trick for testing (500mhz, 256mb >>> RAM, 40gb HDD). >>> >>> Regards >>> >>> Nathan >>> >>> klug.member.lancer at xoxy.net wrote: >>> >>>> Can anyone point me to where I can learn how to make a shared /home >>>> directory over a LAN setup like in our school? The guy who set that >>>> up did a nice job and all but there are some fairly major bugs and >>>> he's hard to get hold of. To be honest, I'm starting to get >>>> frustrated by the errors and the inability to get hold of him, but >>>> I don't want to go into too much detail on a public forum like this >>>> and think it's best if I start all over but learn to do things for >>>> myself. >>>> >>>> Basically, I want to know how to make one machine the file server, >>>> where the /home dirs are linked to the drive on that machine, so >>>> all saved work from students goes to one place instead of being >>>> duplicated on each machine, individual permissions intact. >>>> Obviously adding new student accounts etc will have to have >>>> identical user IDs. I'm not sure if I also want to share other DIRs >>>> like /bin etc. Common permissions would be nice (e.g: I can ban any >>>> student from playing a given game setting permissions on only one >>>> computer). >>>> >>>> I am not wanting to make a dumb terminal situation where the >>>> central computer has to be really powerful, or one computer has to >>>> do all the hard drive / memory tasks of the many machines - that >>>> would slow everyone down. /home access is all I'm really wanting at >>>> least for now. >>>> >>>> I am also interested in the antiporn set up as mentioned before >>>> (like having one machine as the internet gateway for the others) >>>> but for now setting up the LAN /home dir is my priority. I >>>> understand the network guru used LDAP for the current setup, but my >>>> experience in this is zilch. >>>> >>>> Can anyone point me to where I can learn this stuff fast enough to >>>> have set it up myself within the next week or so? (e.g: not a large >>>> thesis of many possibilities - I am a slow reader). Last time I >>>> asked a forum this I explained what I wanted in great detail, and >>>> all I got was "your network - up to youy how you go about it", >>>> which was not helpful. >>>> >>>> Thanks in advance. >>>> Lance. >>>> >>>> _______________________________________________ >>>> KLUG mailing list >>>> KLUG at linux.net.nz >>>> http://www.linux.net.nz/cgi-bin/mailman/listinfo/klug >>>> >>>> >>>> >>> >>> >>> _______________________________________________ >>> KLUG mailing list >>> KLUG at linux.net.nz >>> http://www.linux.net.nz/cgi-bin/mailman/listinfo/klug >>> >>> >>> >> >> >> _______________________________________________ >> KLUG mailing list >> KLUG at linux.net.nz >> http://www.linux.net.nz/cgi-bin/mailman/listinfo/klug >> >> > > > _______________________________________________ > KLUG mailing list > KLUG at linux.net.nz > http://www.linux.net.nz/cgi-bin/mailman/listinfo/klug > > >
| More information about the KLUG mailing list |
If you have any questions or comments about this page, email the
Webmaster Design Copyright © 1998-2005 Linux.net.nz |