Topic: thin client server with other box as dhcp server?

[dennyhalim]

i just saw this:
http://wiki.contribs.org/Thinclient

wondering if it can work fine if the dhcp server is not smeserver?
since my sme is not acting as dhcp server.

or...
can smeserver only act as dhcp server for thin clients and all other clients gets their ip from another dhcp server?

how do i make setup like one of the above alternatives?

tia

[Franco]

You would need to set up MAC restrictions in each DHCP server. This is fairly easy with SME:

Code: [Select]

mkdir -p /etc/e-smith/templates-custom/etc/dhcpd.conf

echo " deny unknown-clients;" > etc/e-smith/templates-custom/etc/dhcpd.conf/25DenyUnknownHost
Then reload the DHCP server.
This means that only registered clients can get an IP address from the server.

[TrevorB]

http://wiki.contribs.org/Thinclient

wondering if it can work fine if the dhcp server is not smeserver?
since my sme is not acting as dhcp server.

smeserver-thinclient does all the dhcp stuff for you, so there isn't much use in this contrib if you are using another server as your dhcp.

You can still supply your images from your smeserver via tftp (smeserver-tftp-server) if you configure your dhcp server to use the smeserver as your tftp server (next-server parameter in dhcpd - don't know much about MS stuff).

Put all of your files in /tftpboot e.g.
/tftpboot/pxelinux.0
/tftpboot/initrd
/tftpboot/vmlinuz
/tftpboot/<config files>
/tftpboot/pxelinux.cfg
/tftpboot/pxelinux.cfg/default

can smeserver only act as dhcp server for thin clients and all other clients gets their ip from another dhcp server?

Probably more hassle than it's worth. If you set up your tftp server, you'll probably find that there isn't much need to change it.

Good Luck!
Trevor B