similar to: pxechain.com loops back with WDSNBP started using DHCP Referral

Thank you Gene! On 10/07/17 17:54, Gene Cumm wrote: > On Mon, Jul 10, 2017 at 11:25 AM, Jelle de Jong via Syslinux > <syslinux at zytor.com> wrote: >> Windows 2012 WDS server: 10.87.0.202 >> Windows DHCP server: 10.87.0.152 >> 066 (Boot Server Host Name): 10.87.3.19 >> 067 (Bootfile Name): pxelinux.0 >> >> PXELinux CentOS 7 server : 10.87.3.19

On Mon, Jul 10, 2017 at 11:25 AM, Jelle de Jong via Syslinux <syslinux at zytor.com> wrote: > Windows 2012 WDS server: 10.87.0.202 > Windows DHCP server: 10.87.0.152 > 066 (Boot Server Host Name): 10.87.3.19 > 067 (Bootfile Name): pxelinux.0 > > PXELinux CentOS 7 server : 10.87.3.19 > > # cat /srv/tftp/pxelinux.cfg/default > DEFAULT menu.c32 > PROMPT 0 > MENU

On 10/07/17 19:13, Jelle de Jong via Syslinux wrote: > Thank you Gene! > > On 10/07/17 17:54, Gene Cumm wrote: >> On Mon, Jul 10, 2017 at 11:25 AM, Jelle de Jong via Syslinux >> <syslinux at zytor.com> wrote: >>> Windows 2012 WDS server: 10.87.0.202 >>> Windows DHCP server: 10.87.0.152 >>> 066 (Boot Server Host Name): 10.87.3.19 >>>

Hello, We are trying to set up a configuration with pxelinux on a linux machine and WDS, allowing us to be free to boot linux netboot installers from the tftp server. We have validated that pointing our dhcp server to the wds server works perfectly. Our idea was to use pxechain.com to launch the wdsnbp.com kernel as below : label windows KERNEL pxechain.com APPEND <ip

Hi, I have more than one pxe server in my network and I need to chain from one to the other. I used to do that with pxechain.com from old versions of syslinux. With the new version (6.02) I'm trying to achieve this with pxechn.c32. I copied the files ldlinux.c32, libcom32.c32, libutil.c32, pxechn.c32, pxelinux.0 and vesamenu.c32 to the tftp's root in both servers and add this in the menu:

Gene Cumm wrote: > >> > > >> > I am attempting to chainload a file from TFTP. I have the following > >> > lines in the configuration file: > >> > > >> > LABEL WDS1 > >> > Menu LABEL WDS1 > >> > kernel pxechn.c32 > >> > append 10.14.141.150::boot\x86\wdsnbp.com -W -o 66.x=0a:0e:8d:96 -S > >>

Hi, Anyone has tried to use pxechain with Etherboot? Here is my problem: The Etherboot client had no problem to get the list of install servers manual from the pxechain. But didn't matter which server was chosen, Etherboot client always tried to use the first server to do the installation. Etherboot 5.4 was used. What the problem may be? PXEchain or Etherboot? Thanks, Joyce --

Colleagues, I am attempting to chainload a file from TFTP. I have the following lines in the configuration file: LABEL WDS1 Menu LABEL WDS1 kernel pxechn.c32 append 10.14.141.150::boot\x86\wdsnbp.com -W -o 66.x=0a:0e:8d:96 -S The TFTP server at 10.14.141.150 is operational and wdsnbp.com is available at the indicated path. I have tried various combinations of colons, forward and back

Gene Cumm wrote: > > > > I am attempting to chainload a file from TFTP. I have the following > > lines in the configuration file: > > > > LABEL WDS1 > > Menu LABEL WDS1 > > kernel pxechn.c32 > > append 10.14.141.150::boot\x86\wdsnbp.com -W -o 66.x=0a:0e:8d:96 -S > > > > The TFTP server at 10.14.141.150 is operational and wdsnbp.com is

Gene Cumm wrote: [dd] > >> >> > >> >> LABEL WDS1 > >> >> MENU LABEL WDS1 > >> >> COM32 pxechn.c32 > >> >> APPEND 10.14.141.150::boot\x86\wdsnbp.com -W > >> > > >> > Did it send a packet to 10.14.141.150? > >> > >> Sorry, that was "Have you tried just the following:"

On Fri, Jul 12, 2013 at 8:14 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Fri, Jul 12, 2013 at 5:14 AM, Victor Sudakov <vas at mpeks.tomsk.su> wrote: >> Colleagues, >> >> I am attempting to chainload a file from TFTP. I have the following >> lines in the configuration file: >> >> LABEL WDS1 >> Menu LABEL WDS1 >> kernel

On Sat, 20 Jul, at 09:48:38AM, Victor Sudakov wrote: > Negative. > > I have changed the stanza into > > label WDS > menu LABEL ^4. Windows Deployment Service > com32 pxechn.c32 > append 10.14.140.128::boot\x86\wdsnbp.com -W > > and got the following result on VirtualBox: > > pxechn.c32: Attempting to load '10.14.140.128::boot\x86\wdsnbp.com':

On Jul 14, 2013 10:02 PM, "Victor Sudakov" <vas at mpeks.tomsk.su> wrote: > > I have tried replacing the IP address with a DNS name like this: > > LABEL WDS1 > Menu LABEL WDS1 > com32 pxechn.c32 > append ws150.sibptus.transneft.ru::boot\x86\wdsnbp.com -W -o 66.x=0a:0e:8d:96 Did you try without "-o 66..."? Any chance for a packet capture from a

On May 31, 2012 5:23 AM, "Arends, R.R." <r.r.arends at hr.nl> wrote: > > Hello Genec, > > Got a question regarding pxechn.c32 in combination with wds (2k8r2). > > We got (i)pxelinux as our main pxe system, and want to chain to wds with a vesamenu option. > > I tried the latest pxechn.c32 from git. But somehow wds still tries to contact the next-server (main

On Tue, Jul 16, 2013 at 12:51 AM, Victor Sudakov <vas at mpeks.tomsk.su> wrote: > Gene Cumm wrote: >> >> Did you try without "-o 66..."? Any chance for a packet capture from a >> mirrored port or the dhcpd+tftpd-old+tftpd-new+dnsd? > > OK, I have tried the following: > > label WDS > menu LABEL ^4. Windows Deployment Service > com32

On Jul 22, 2013 5:27 PM, "Gene Cumm" <gene.cumm at gmail.com> wrote: > > On Mon, Jul 22, 2013 at 11:36 AM, Matt Fleming <matt at console-pimps.org> wrote: > > On Sat, 20 Jul, at 09:48:38AM, Victor Sudakov wrote: > >> Negative. > >> > >> I have changed the stanza into > >> > >> label WDS > >> menu LABEL ^4.

Hi everybody, I'm facing a issue with the pxelinux when trying to Boot WDS and I run PXELINUX version 4.03 2010-10-22 and trying to chain (pxechain.com is from the same syslinux package as pxelinux) the WDS (that is a windows 2008 R2). $WINDOWS-2K8-R2-IP$ = The IP address to the WDS server and this is the config in the pxelinux.cfg/default $LINUX-PXE-SERVER$ = The server that serves the

As some have noticed, WDS (Windows Deployment Services) on Windows Server 2008R2 can't normally be chained with pxechain.com. Some have also noticed wdsnbp.com doing something resembling another round of DHCP (discover/ack/request/offer). Working on pxechn.c32 I've found the "issue" and incorporated a workaround into pxechn.c32. wdsnbp.com issues a DHCP discover to the IP

To start, I know I need to upgrade SYSLINUX, but since we are using the CMenu's it's not that easy of an upgrade. I have been (slowly) working on a new iPXE/pxelinux 4.04 install that I am migrating to. However, I have an interesting problem. Using any of the examples I have seen, I can not make pxechain.com work. "pxechain.com ::/path/pxelinux.0" "pxechain.com

Hello list, I am trying to prepare a USB disk with syslinux that is meant to be able to offer a choice among many different distributions. The goal is that I should be able to dump each distribution's CD contents into a separate subdirectory, and have a master menu that hands off to each distribution's subdirectory. A while back, when faced with a similar task on a PXE server, I came