Try taking the next-server directive out of the top subnet portion and try just 
leaving
the call out in the LTSP 5 section to see if that helps.  I have not ran an 
ltsp network
in this fashion so I don't know for sure how this should look.

Jim

> However I'm stuck on the next-server parameter. You see, I put the dhcp 
> server 
> on a different server other than the LTSP server. For this I use the 
> next-server parameter. Client can get the assigned IP (192.168.0.100), but 
> failed to contact the TFTP server.
> 
> =================
> This is my dhcpd.conf as per your help:
> =================
> 
> authoritative;
> server-identifier       centos5a;
> ddns-updates            on;
> ddns-update-style       interim;
> ddns-domainname         "jauh.com.";
> ddns-rev-domainname     "in-addr.arpa.";
> ignore                  client-updates;
> 
> include                 "/etc/ddns_key.key";
> 
> subnet 192.168.0.0 netmask 255.255.255.0 {
>   option domain-name "jauh.com";
>   option domain-name-servers 192.168.0.199, 10.1.2.253;
>   option broadcast-address 192.168.0.255;
>   option routers 192.168.0.254;
>   option subnet-mask 255.255.255.0;
>   next-server 192.168.0.197;
> 
>   pool {
>         allow unknown-clients;
>         range 192.168.0.20 192.168.0.30;
>         }
> 
>   pool {
>         deny unknown-clients;
>         range 192.168.0.50 192.168.0.60;
>                 host nonltsp1 {
>                 hardware ethernet 00:16:11:23:30:9f;
>                 fixed-address 192.168.0.50;
>                 }
>         }
> #}
> #LTSP Clients by Mac Address
> group {
>         use-host-decl-names on;
>         deny unknown-clients;
>         # TFTP server address: 
>         next-server 192.168.0.197;
>         if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
>         filename "/ltsp/i386/pxelinux.0";
>                 }
>         else{
>         filename "/ltsp/i386/nbi.img";
>                 }
>         option root-path "/opt/ltsp/i386";
> 
>         host client1 {
>                 hardware ethernet 00:16:17:23:30:9f;
>                 fixed-address 192.168.0.100;
>                 }
>         }
> }
> 
> zone jauh.com. {
>         primary 192.168.0.199;
>         key ddns_key;
> }
> 
> zone 0.168.192.in-addr.arpa. {
>         primary 192.168.0.199;
>         key ddns_key;
> }

-- 
This message has been scanned for viruses and
dangerous content by the Cotter Technology 
Department, and is believed to be clean.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.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.freenode.net

Reply via email to