similar to: Cannot chain to another PXE server on the same subnet

Sorry for top-posting but my webmail forces me to. I added -W to the APPEND line as suggested but I'm still getting the same result: Booting... Altiris, inc. X86PC PreBoot, PXE-2.x Enhanced Build ID=402 PXEPreZero: Invalid PXE Server list format. and the client PC freezes right there. Here's the full content of my dhcp.conf: max-lease-time 86400; ddns-update-style interim;

On Fri, Mar 7, 2014 at 2:33 AM, Vieri <rentorbuy at yahoo.com> wrote: > So I take it it's more of a DHCP hack in which: > 1- client boots and gets DHCP response from 10.215.144.7 with PXE syslinux info > 2- client loads pxelinux.0 menu and selects menu that chains to Altiris PXE menu except, instead of calling pxechain.com or pxechn.c32 with the Altiris server's IP address,

On Wed, Mar 5, 2014 at 1:55 AM, Vieri <rentorbuy at yahoo.com> wrote: > Sorry for top-posting but my webmail forces me to. Odd. It's been a while since I used Yahoo but I didn't think I had that issue. GMail does default to top-posting but clicking the ellipsis to look at the previous email is enough. > I added -W to the APPEND line as suggested but I'm still getting

----- Original Message ----- From: Gene Cumm <gene.cumm at gmail.com> > It's been a while since I used Yahoo but I didn't think I had > that issue.? GMail does default to top-posting Doing it manually... didn't find that option. > Perhaps also try -o 43.x=01:04:0a:d7:90:3c:ff (which will set the > mtftp option) in addition to -W. Tried it but still the same error.

On Tue, Mar 4, 2014 at 12:52 PM, Vieri <rentorbuy at yahoo.com> wrote: > Hi, > > > I have a Linux server at ip address 10.215.144.7 running DHCP, TFTP and syslinux. > > DHCP config contains the following: > > next-server 10.215.144.7; > filename "/pxe/syslinux/pxelinux.0"; > > and the 'default' pxelinux.cfg contains: > > LABEL altiris

This is what I'm seeing on my DHCP server: # tcpdump -i eth0 -vvv -s 1500 '(port 67 or port 68)' tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 1500 bytes 13:24:05.679950 IP (tos 0x0, ttl? 20, id 0, offset 0, flags [none], proto: UDP (17), length: 576) 0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:24:54:d9:d4:2f (oui

On Wed, 2014-03-05 at 13:18 -0500, Gene Cumm wrote: > Second, I notice the Altiris server specifies _3_ options of code 43, > including one of length 253. The pack/unpack _should_ handle this but > may split it differently. That's legal, and treated as if the values had been concatenated. See RFC2131, section 4.1, and particularly the second paragraph on page 24. Unfortunately, a

On Thu, 2014-03-06 at 16:52 -0500, Gene Cumm wrote: > > RFC2131, section 4.1, and particularly the second paragraph on page 24. > > Conditionally. "Options may appear only once, unless otherwise > specified in the options document." I don't see any indication of any > options that DO allow it unless "The information is an opaque object > of n

Hello All. I have few networks with Tivoli Provision Manager (http://www.ibm.com/developerworks/downloads/tiv/pmfos/?S_TACT=105AGX28&S_CMP=TRIALS ), Altiris (http://www.symantec.com/business/deployment-solution) and WDS (on W2008Stdx32). I successfully expand WDS functionally with pxelinux (4.03).I really like how pxelinux working. Server who respond on client request is on Windows 2008

On Fri, Mar 7, 2014 at 4:00 PM, Jeffrey Hutzelman <jhutz at cmu.edu> wrote: > On Fri, 2014-03-07 at 05:49 -0500, Gene Cumm wrote: >> 1) Thinking about the responses again, I'm absolutely surprised that >> you can even boot PXELINUX. I would have expected the response from >> the Altiris server to override your attempts to block it. > > Nope. The PXE spec

Hi, I finally got it working and it was just as Gene said except that option 43 didn't have the right value. I downloaded a utility called PXEForcedMode that gave me the binary string I had to use as option 43. In my case the utility reported the following data: dhcp server set optionvalue 43 BINARY 06010B0807AAAA010AD7903C00 dhcp server set optionvalue 60 STRING PXEClient dhcp server set

----- Original Message ----- From: Jeffrey Hutzelman <jhutz at cmu.edu> > The "bstrap.0" file is a small NBP that > handles the menu when booting from old PXE clients that don't implement > the menu-related parts of the protocol.? But even with bstrap.0, the > menu stuff doesn't work if the menu-related options weren't in whichever > DHCP response gets

On Fri, 2014-03-07 at 05:49 -0500, Gene Cumm wrote: > On Fri, Mar 7, 2014 at 2:33 AM, Vieri <rentorbuy at yahoo.com> wrote: > > > So I take it it's more of a DHCP hack in which: > > 1- client boots and gets DHCP response from 10.215.144.7 with PXE syslinux info > > 2- client loads pxelinux.0 menu and selects menu that chains to Altiris PXE menu except, instead of

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

Hey guys, We are going with WDS to fire up first to get the benefits of targeted M$ deployments. If you have the "handle unknown computers" off on your M$ Distribution point, then you can still use regular WDS which runs next as a PXE filter (DLL linked into WDS) to fire off anything you want to including PXELinux. The stuff I was talking about before with PXELinux not working in

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 TITLE Main Menu LABEL CentOS-7-x86_64 KERNEL CentOS-7-x86_64/vmlinuz APPEND initrd=CentOS-7-x86_64/initrd.img

On Fri, Mar 7, 2014 at 6:01 PM, Jeffrey Hutzelman <jhutz at cmu.edu> wrote: > On Fri, 2014-03-07 at 17:46 -0500, Gene Cumm wrote: >> On Fri, Mar 7, 2014 at 4:00 PM, Jeffrey Hutzelman <jhutz at cmu.edu> wrote: >> > On Fri, 2014-03-07 at 05:49 -0500, Gene Cumm wrote: >> >> >> 1) Thinking about the responses again, I'm absolutely surprised that

On Dec 25, 2014 2:11 AM, "Luke Ledgerd" <luke.ledgerd at niteco.se> wrote: > > Hey guys, > > We are going with WDS to fire up first to get the benefits of targeted M$ deployments. If you have the "handle unknown computers" off on your M$ Distribution point, then you can still use regular WDS which runs next as a PXE filter (DLL linked into WDS) to fire off

Hi, ________________________________________ From: Gene Cumm <gene.cumm at gmail.com> Sent: Wednesday, March 16, 2016 00:56 To: Jan Frode J?ger Cc: syslinux at zytor.com Subject: Re: [syslinux] Updated status on UEFI compliant version of the pxechn-module On Tue, Mar 15, 2016 at 9:32 AM, Jan Frode J?ger <jan.frode.jaeger at ntnu.no> wrote: Without trying to figure out where data is

Hi, Ok, when can we then anticipate pxe-chaining to be possible with syslinux under the UEFI architecture? Are there any plans to implement both correct interfacing to UEFI as well as the issue of arbitrary UEFI images? Haven't tried to read the UEFI-specification as it is sub 3000-pages long, so I am a bit in the dark as to the changes in architecture from BIOS to UEFI. It has been