Hello Nathan. I'm not sure if there's a problem with ou email addys connecting. Sunday morning is the one time I annot make it. Sometime on Saturday, or perhaps Sunday afternoon would be fine. Please let me know what you would like. Lance. Nathan Cook - nathan at coast-computers.co.nz wrote: > The LDAP server will have the Router set as the DNS server, what you > want to make the LDAP server the DNS server, this will mean installing > a package (BIND is recommended), and then have it's own DNS server set > as the router. I have setup a similar operation and it worked a treat. > > I sent you an email yesterday but I doubt that it has got through to > you though, will try and call you about the weekend, but Sunday > morning is looking to be the day for me, how about you? > > Cheers > > Nathan > > klug.member.lancer at xoxy.net wrote: > >> Okay - I'm now in school. The main router for the internet (the radio >> hub which gaives cable internet via radio link from across the road) >> is 192.168.1.1 >> Is there any reason this would become an "essential" access route for >> LDAP to function? >> Any reason it may cause a DNS conflict when the internet goes down? >> >> I don't see any reason why the LDAP server should access the internet >> gateway for its own function. >> >> Lancer. >> >> >> >> klug.member.lancer at xoxy.net wrote: >> >>> Seeing as the problems of LDAP going down when the internet cable is >>> takenm out from teh school network seems to be something of a DNS >>> issue, >>> I thought I'd compare the Networks settings for the clients vs the >>> "default" ones I normally use. >>> >>> My defaults: >>> IP address: 192.168.0.1 (where the last dc is 1 for computer01, 2 for >>> the next and so on) >>> Netmask: 255.255.255.0 >>> Default gateway (IP): 192.168.0.254 >>> Primary nameserver: 192.168.0.1 (ALWAYS - so the computers point to the >>> same box) >>> >>> The network the LDAP clients are running has the following... >>> IP address: 192.168.1.131 (computer01=131, computer02=132...) >>> Netmask: 255.255.255.0 >>> Default gateway (IP): 192.168.1.1 <= Network guru said to change this >>> Primary nameserver: 192.168.1.1 <= I'm questioning this. >>> >>> The box the actual LDAP server is on is 192.168.1.251. I'm guessing the >>> 192.168.1.1 address is actually pointing to the internet router hub >>> over >>> the road (school office) and is thereby being used as primary DNS even >>> for LDAP, which causes connection failures once the internet ethernet >>> cable is pulled from the LAN. >>> >>> I'm thinking that I should change the 192.168.1.1 instances to >>> 192.168.1.251 to have them run from the LDAP server, however I'm not >>> sure why the network guru would have set them up otherwise and I'm >>> assuming he would have his reasons. >>> >>> Just a thought. I haven't tweaked it yet. Am I off the beaten track? >>> >>> Lancer. >>> >>> >>> >>> _______________________________________________ >>> 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 |