RE: Pxes using windows 2000 TFTP & DHCP OR RIS

Diego Torres Milano <[email protected]>
Newsgroups gmane.linux.pxes.devel
Organization IN3
Message-ID <1091326259.6282.74.camel@zebra>
Thank you for the info.
If you would like to turn this into a micro/mini HOWTO, just let me know
and I will publish it.
There's a ___BIG BUG__ in Microsoft TFTP (2003) that is made evident by
some PXES code (a workaround is provided in PXES 0.9).
When PXES tries to get the Remote Configuration do something like this:

tftp confserver <<!
	get default.conf /tmp/default.conf
	get network.conf /tmp/network.conf
	get MAC.conf /tmp/MAC.conf
	get hostname.conf /tmp/hostname.conf
!

This works well with any other TFTP server but with the Microsoft one if
some of the files are missing the contents are mixed, that is one file
content is put into another file name.


On Sat, 2004-07-31 at 17:49, Pickup, Jordan wrote:
> We use PXES and RIS simultaneously from the same Windows 2003 server.
> Our RIS was configured and functional before we added PXES.
> 
>  
> 
> The configuration was the same with windows 2000, and we have used the
> same setup from PXES 0.5 through to 0.8.
> 
>  
> 
> The PXES files can go with the RIS files in the “\\RISServer\REMINST”
> share. 
> 
>  
> 
>       * The “pxelinux.0” file should go in the root of the share.
>       * A “pxes” folder should also go in the root of the share. This
>         folder should contain a “config” folder, which will contain
>         your conf files. (eg. the path to your default.conf file will
>         be \\RISServer\REMINST\pxes\config\default.conf)
>       * All the other files should go in the OSChooser\I386 folder
>         (\\RISServer\REMINST\OSChooser\I386) that should already be
>         part of your RIS setup. Also in this folder should be your
>         “pxelinux.cfg” folder which contains the “default” file with
>         the boot options.
> 
> 
>  
> 
> On the DHCP server (which for us is the same server as the RIS
> server), we make IP reservations for each pxes client to which we add
> the following two scope options:
> 
>  
> 
>       * 067 Bootfile Name – set to a value of “/pxelinux.0”
>       * 043 Vendor Specific Info – set to a value of “01 04 00 00 00
>         00 FF”
> 
> 
>  
> 
> With this setup, any IP range with those two scope options will use
> the RIS server to network boot to PXES, and any IP range without the
> options will network boot to RIS like normal.
> 
>  
> 
> Hope this helps.
> 
>  
> 
> Jordan
> 
>  
> 
>  
> 
>  
> 
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of der mer
> Sent: Saturday, July 31, 2004 9:35 AM
> To: [email protected]
> Subject: [pxes-devel] Pxes using windows 2000 TFTP & DHCP OR RIS
> 
>  
> 
> I am using windows 2000 server with Remote Installation Services
> (RIS). I want to configure Pxes to use the TFTP provided with windows
> 2000 server. Does anyone have any idea on how to do that? 
> 
> 
>                                    
> ______________________________________________________________________
> 
> Do you Yahoo!?
> Read only the mail you want - Yahoo! Mail SpamGuard.
> 
> 



-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.