Re: Cannot chain load gPXE to Windows 2003 DHCP
Ron Jameson <[email protected]>
| Newsgroups | gmane.network.etherboot.user |
|---|---|
| Message-ID | <[email protected]> |
I compiled (in ubuntu live boot environment) the 0.9.7 to undionly.kpxe - copied to my TFTP server - also tried the most current build - neither even boot up or chainload. Tested the rom-o-matic .pxe - and that did nothing as well. There has to be something blocking the chaining in the 2003 windows server setup. My TFTP server I moved back to my RIS server hoping by keeping PXE & TFTP on the same - it would help...but alas, nothing still. Would teamed NICS on the servers cause issue? I would not think it would...but I am fishing now. I have not rebooted the DHCP server - but I have restarted the service. Stumped.... Ron -----Original Message----- From: Ron Jameson Sent: Sunday, August 09, 2009 12:16 PM To: 'Michael Brown' Subject: RE: [Etherboot-discuss] Cannot chain load gPXE to Windows 2003 DHCP Michael - yes, was trying to load Win7 direct to iSCSI target. I made the isci_boot.gpxe script, saved it as a unix file and also turned off 2 possible conflicting DHCP devices on my network (hava video streaming box) and for some reason - it is still not chaining the gPXE to the laptop. It loads PXE then once it gets all the DHCP info that PXE shows on connection, it unloads then just boots up to Windows XP on the laptop - not even getting the gPXE file. To add how my setup looks...I have tftp running on a Win2003 web server VM, my Win2003 RIS/PXE server runs on a second physical server and my DHCP is on a third physical server. In my DHCP scope - I had originally 066 pointing to my RIS/PXE server then in my Reservations for this gPXE laptop - I overwrote a new 066 option to point to my TFTP server this holds the undionly.kpxe & script. I also tried to change my server option 066 to the same TFTP gPXE server thinking PXE boot was going to my RIS server and getting lost - but that did not make any difference. Any clues on why this is not chaining? Ron -----Original Message----- From: Michael Brown [mailto:[email protected]] Sent: Sunday, August 09, 2009 7:03 AM To: [email protected] Cc: Ron Jameson Subject: Re: [Etherboot-discuss] Cannot chain load gPXE to Windows 2003 DHCP On Friday 07 August 2009 21:31:18 Ron Jameson wrote: > I think this could be DHCP issues related to the boot file - unless that is > only when I boot thru Pxe (the USBkey should have worked). So, after > giving up on the USB route - I am trying to chain load this and the docs on > the site seem incomplete. Do I need to make a script as the page shows on > the DHCP 067 option - tftp://servername/tftpscript.txt and also a second > 067 that is the boot file name. I setup a Windows 2003 tftp service on a > web server, dhcp is on another server - I can manually from a PC run TFTP > x.x.x.x GET undionly.kpxe and it copies it over - so I am pretty sure that > works...but my question is what belongs in the tftpscript.txt file? Does > this need to call the undionly.kpxe, load the DHCP NET0 or is that what > DHCP is supposed to do? Your description of what you are trying to achieve is quite unclear, but I am guessing that you are trying to install Windows 7 directly to an iSCSI target. If this is not correct, then these instructions will not work for you. Place undionly.kpxe on your Windows Server 2003 TFTP server (which you have already done). Configure your Windows Server 2003 DHCP server with option 067 Bootfile Name as "undionly.kpxe". Define a new user class called "gPXE" as shown at http://etherboot.org/wiki/pxechaining. Configure option 067 for the gPXE user class as "iscsi_install.gpxe". Create a file "iscsi_install.gpxe" containing #!gpxe set keep-san 1 sanboot ${root-path} and place this "iscsi_install.gpxe" file on your Windows Server 2003 TFTP server alongside undionly.kpxe. Create a DHCP reservation for the machine you are trying to boot via gPXE, and configure option 017 Root Path as "iscsi:X.X.X.X::::iqn.XXXX-XX.xxx.xxxx.xxx" where "X.X.X.X" is the IP address or DNS name of your iSCSI target, and "iqn.XXXX-XX.xxx.xxxx.xxx" is the iSCSI IQN that you want to install to. Michael ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july