Hi,

I configure my LTSP Server on a subnet 192.168.2.0.
which is working fine.
The Server is IP 192.168.2.5 (I m using only one IP)
The DHCP Server (192.168.2.2) is manage by a windows server on the same subnet
The PXE server is manage my LTSP Server.

So, LTSP works fine if the pc is plugged on the same hub.
If I plugged it behind a router on a different subnet (192.168.10.0)
PXE start and initialize LTSP as configure on my DHCP Server (Router :
192.1698.10.1, Boot Server: 192.168.2.5, Bootfile Name:pxelinux.0.)

but it stop after nfs-top:

Begin: Running /scripts/nfs-top...
Done.
[4294679.422000] NET: Registered protocol family 17
IP-Config: eth0 hardware address [Insert MAC Address here] into 1500 DHCP RARP

I read http://doc.ubuntu.com/edubuntu/edubuntu/handbook/C/ltsp-theory.html
The problem is link with ipconfig.
-----------------------------------
A small DHCP client called ipconfig will then be run, to make another
query from the DHCP server. This separate user-space query gets
information supplied in the dhcpd.conf file, like the nfs root server,
default gateway, and other important parameters.
-----------------------------------

Somebody find a solution which is to have another DHCP server on the
subnet,. which will be a bit hard for me.


Do you know what ipconfig do ?
So, what do I need to modify to be able to have LTSP Client on different subnet?


Thanks for your help. :-)
Smad

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_____________________________________________________________________
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