Dear Mick,
I haven't tried this myself (no iPXE at home today) but it looks like
something along these lines should work:
|#!ipxe
chain tftp://<OTC SERVER IP ADDRESS>/pxelinux.0|
See http://ipxe.org/cmd/chain.
This of course assumes that your OTC server has a fixed IP address.
Note that you do not need to use the path on the OTC server - only the
bit below the TFTP server root (which in this case is just pxelinux.0).
This should not be necessary though, as the OTC proxy DHCP normally
just works - it doesn't need a next-server set like most other thin
client PXE setups. Your gPXE isn't a version prior to May 2009 is it, as
this doesn't (according to Internet) support proxy DHCP?
Also, if you are using user-defined mac addresses in iPXE for some
reason, remember that this means that you will need a different client
configuration in the OTC manager from that used for a hardware PXE boot
as the client will not be recognised otherwise.
If this still doesn't work, I advise using a network traffic analyser
of some kind to see what is going on with the server(s) TFTP traffic
responding to PXE - I have found this saves loads of time trying to work
out why clients aren't booting.
All the best,
Mark
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
The Open Source Thin Client Solution http://openthinclient.org
openthinclient-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openthinclient-user
