Re: Cannot chain load gPXE to Windows 2003 DHCP

Well...I added the sleep.gpxe to the undionly.gpxe - it sleeps for 5 before running the gPXE DHCP - but that did not help.   I get the timeout error 0x4c106035 - then stops.  Sometimes it runs thru a reload of the intel PXE - but fails with timeout then stops.    On all occasions - if I CTRL-B and manually do this - it works fine.  Once in awhile when manually entering DHCP NET0 - it will timeout the first, but the second it will work.

I attempted to make a undionly.kpxe with the embedded image of sleep.gpxe and also a custom script which would chain to my install_iscsi.gpxe on my TFPT server - but that fails and my thought was I need to fix the timeout issue first as if we timeout - I have not IP to be able to get to my script on the network.   I even embedded a script that says:

#!gpxe
Dhcp net0
Dhcp net0
Set keep-san 1
Sanboot ${root-path}


My thought was a brute force of multiple dhcp net0 would make it respond OK...but after the first timeout - it stops.

Hoping there still may be someone that may have a clue to where my timeout could be.   I have RIS/WDS off, moved TFTP to my web server and all points to that server (avoiding my RIS/WDS all together - just for testing). 

Ron

-----Original Message-----
From: Ron Jameson 
Sent: Wednesday, August 12, 2009 10:10 AM
To: '[email protected]'; '[email protected]'
Subject: RE: Re: [Etherboot-discuss] Cannot chain load gPXE to Windows 2003 DHCP

Thanks Andrew....this did get me to actually boot gPXE - but still some issues...

I did setup reservations in my DHCP scope for this and have the options 66 going to my RIS server (pxe/tftp) & 67 has undionly.kpxe.   The second 067 option under userclass gPXE runs the gPXE script where I set the keepsan and sanboot the iSCSI.  The DHCP setup matches the wiki page you referenced and I can manually tftp to my RIS server and transfer a file which worked prior.

Now, I turned off WDS/RIS and now gPXE loads (finally) - but is running undionly.kpxe with the hardcoded autoboot procedure I am sure.   Next issue is it times out during the DHCP NET0 phase which I have yet to fix.   I may have to compile the undionly.kpxe with a sleep option as I read in the forums.  When I manually run DHCP net0 - it loads the info and I can manually finish the boot process (set keep-san 1, sanboot iscsi......etc.)

Now..oddly - the first gPXE boot appears to run the autoboot procedure - it is not however running the 067 option with userclass gPXE (which runs the script).  Is this setup as defined under the wiki page about chainloading only when you have a PXE server on the network (which I turned off for now)?  If so - then I may need to get some PXE services running to let me run the script (where I have some control by loading the DHCP NET0 a few times to get over the timeout thus bypassing the autoboot hardcoded one in gPXE). (sounds like a workaround)

Another question arises- can I run WDS/RIS and gPXE on the same LAN?  I use the RIS/WDS often to load XP installs, ghost loaders etc.


Thanks for the help thus far...getting closer.


Ron



From: [email protected] [mailto:[email protected]] 
Sent: Wednesday, August 12, 2009 9:14 AM
To: Ron Jameson; [email protected]
Subject: Re: Re: [Etherboot-discuss] Cannot chain load gPXE to Windows 2003 DHCP

Ron,

The PXE service that is running on your RIS/WDS server is a special type of DHCP server specifically for PXE clients. When chainloading gPXE from a TFTP server on the network, you don't actually need a PXE server to negotiate this connection. The options available in any vanilla DHCP server will do the trick.

As a troubleshooting step, take a look at the DHCP options in this image: http://www.etherboot.org/wiki/_media/configure-options.png

If you followed the chainloading guide Michael linked you to a few emails back, configure option 66 (with a user class of "none," which is the default) with the DNS name or IP of your TFTP server on which you placed undionly.kpxe. Configure option 67 (again, with a user class of "none") as "undionly.kpxe".

Now, if you can do a "tftp -i <option 66> get <option 67>" successfully at a command line, then you should be able to chainload.

The last step is to disable your PXE service on your RIS/WDS server. When you do this, ensure that you keep the TFTP service online. Disabling the PXE service will ensure that any PXE client listens to the options you've just configured in your DHCP server instead of the ones offered in their stead by your PXE server.

Finally, attempt a PXE boot and see if you can chainload gPXE from the network.

Best of luck!

-Andrew Bobulsky

On Aug 12, 2009 9:34am, Ron Jameson <[email protected]> wrote:
> It never loads gPXE..but I think I have the reason....digging further into your web site.   I have 2003 RIS/WDS in legacy mode - that is my PXE/TFTP server.  Will this not work on a RIS sever due to how RIS communicates?  I put wireshark on the RIS and appears the laptop tries to load OSCchooser\i386\startrom.com - which means it is not even getting the bootfilename of undionly.kpxe to run.
> 
> 
> 
> If my hunch is correct - is there any way to get this to work using RIS as the PXE or do I need a different PXE server for this?   If so - I am not sure we can have dual PXE's on a network - but cannot say for sure.
> 
> 
> 
> Ron
> 
> 
> 
> -----Original Message-----
> 
> From: Michael Brown [mailto:[email protected]]
> 
> Sent: Wednesday, August 12, 2009 6:28 AM
> 
> To: [email protected]
> 
> Cc: Ron Jameson
> 
> Subject: Re: [Etherboot-discuss] Cannot chain load gPXE to Windows 2003 DHCP
> 
> 
> 
> On Wednesday 12 August 2009 07:08:10 Ron Jameson wrote:
> 
> > 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.
> 
> 
> 
> It would help if you could provide some indiciation of the error messages that
> 
> you are seeing.  From your description, I can't tell if you are even getting
> 
> as far as loading gPXE in the first place.
> 
> 
> 
> 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
> 
> _______________________________________________
> 
> Etherboot-discuss mailing list
> 
> [email protected]
> 
> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>

------------------------------------------------------------------------------
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