Fajar Priyanto wrote:
Munch...
> Hello Jim,
> Thank you so much for the direction.
> I've followed it and now am able to partition the network using dhcp as you
> stated.
>
> 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.
>
Munch again
Thoughts:
1. The client should be sending an ARP request for the tftp
server. If this is not happening, then something is wrong with
next-server in your version of dhcpd.
2. Try running tcpdump on the tftp server.
tcpdump -i eth0 host {ip that client should have gotten}
3. Can you manually run tftp to the server?
4. tftp is normally set to log to /var/log/daemon.log. Try
increasing the verbosity and see if anything shows up.
5.. You have the filename as /ltsp/i386/pxelinux.0 But you have
root-path = /opt/ltsp/i386/ Do you actually have two separate paths?
Remember that tftp usually runs in chrooted enviroment, so the
path to pxelinux.0 is relative to the jail that tftp runs in. e.g.
If I allow tftp to have access to /opt/tftp/
and then I have /opt/tftp/lstp/pxelinux.0 as my boot file
then the path I give for the filename is /lstp/pxelinux.0
If your paths are correct, then it means that you have permitted
/opt via tftp, which I would regard as a security risk. (Not a
huge one, but still...)
-------------------------------------------------------------------------
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
