similar to: windows tftp/dhcp/pxe server

Displaying 20 results from an estimated 12000 matches similar to: "windows tftp/dhcp/pxe server"

2003 Aug 28
0
Using PXELINUX with Windows 2000 DHCP and TFTP
I noticed some links and suggestions on the SYSLINUX web site that reference how to run TFTP on Windows 2000 Server. Two of them suggest installing RIS, and one of them points to a third-party utility. I don't need to install RIS, because I don't want to run Windows setup over PXE. (In fact, I want to use PXELINUX to boot a DOS floppy and run Symantec Ghost to deploy an image.) Also, I
2005 Jun 21
1
PXElinux and tftp path prefix
I want to chain multiple servers with pxelinux initiated from a ris server. (Correct me if i'm wrong) The Ris server sends a tftp-path-prefix location where the pxelinux.cfg is searched. On the ris server I have entries like: label server2 kernel 192.168.1.2::pxelinux.0 This fetches the pxelinux from server2 but the pxeconfig.cfg from server1 is used. Can I overrule this with an
2014 Sep 25
1
UEFI PXE / split config / TFTP attempted to DHCP server, not TFTP server
>Date: Sun, 21 Sep 2014 22:19:12 -0400 >From: Gene Cumm <gene.cumm at gmail.com> >To: Spike White <spikewhitetx at gmail.com> >Cc: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com> >Subject: Re: [syslinux] UEFI PXE / split config / TFTP attempted to > DHCP server, not TFTP server >Message-ID: >
2004 Jan 15
2
PXELINUX with all-Windows DHCP/TFTP servers?
Hello... I have PXELINUX working nicely on FreeBSD, but I have exactly zero experience with Windows Server. What I would like to do is: Have PXE client connect to Windows DHCP server to get value "filename pxelinux.0" Have PXE client connect to Windows TFTP server to download pxelinux.0, display, pxelinux.cfg/default, memdisk, and appropriate initrd files (really bootable floppy
2002 Oct 25
1
pxelinux and tftp server
We are trying to network boot a IBM PC with Linux using PXE. PXELINUX.0 gets downloaded properly. But when PXELINUX tries to get the /tftpboot/pxelinux.cfg/<xyz> config file, it keeps on rebooting. We found that the tftp server that we are using does not support tsize option. Could this be a problem. Thanks in advance for your help. Regards Arun
2013 Jun 07
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Wed, 05 Jun, at 09:29:58PM, Gerardo Exequiel Pozzi wrote: > dnsmasq-tftp: file /run/archiso/bootmnt/arch/libcom32.c32 not found > dnsmasq-tftp: file /run/archiso/bootmnt/arch//libcom32.c32 not found > dnsmasq-tftp: file /run/archiso/bootmnt/arch/libcom32.c32 not found > dnsmasq-tftp: file > /run/archiso/bootmnt/arch//arch//boot/syslinux/libcom32.c32 not found OK, here's the
2013 Jun 07
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
> > Right, basically the internal PATH variable that keeps a list of > directories in which to search for files doesn't play well when it > encounters TFTP-style paths. > > The entire problem stems from the fact that colons (':') are used to > separate entries in the PATH directive and they're also used in > TFTP-style paths. While I see that you don't
2013 Jun 08
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Jun 8, 2013 11:48 AM, "H. Peter Anvin" <hpa at zytor.com> wrote: > > On 06/07/2013 03:34 PM, Ady wrote: > > > > If I may... > > > > Most Linux distros are not using 5.xx yet. From the point of view of > > the final user, there are still few new features in 5.xx in > > comparison with 4.xx. Before this issue affects more users, and >
2013 Jun 12
1
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Wed, 2013-06-12 at 16:31 +0100, Matt Fleming wrote: > Switch to using the space character to separate PATH entries instead, > which not only allows TFTP-style paths but also http and ftp urls. If we > ever support filenames containing spaces in config files, then we'll > have to introduce some means of quotation, to distinguish filenames > containing spaces from separate
2014 Sep 21
1
UEFI PXE / split config / TFTP attempted to DHCP server, not TFTP server
All, I realize this is not strictly a PXELINUX question. So I hope you'll indulge me; hopefully some of these PXELINUX experts have seen this before. And can tell me what I'm doing wrong. Or confirm my suspicions. I have a test lab server at work. Split config. The network team manages the DHCP servers, points to our TFTP server. Test subnet has 3 DHCP pools. BIOS PXE, UEFI PXE and
2013 Jun 06
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Wed, Jun 5, 2013 at 8:29 PM, Gerardo Exequiel Pozzi <vmlinuz386 at yahoo.com.ar> wrote: > Hello, > > First, this setup works fine without any error in syslinux 4.06 as show > below. > > For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2] > directories (~2MB each) are uploaded ready for test. > > As said before, this is tested on qemu-1.5.0 +
2013 Jun 06
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
Am 06.06.2013 07:00, schrieb Gene Cumm: > iPXE details. My testing was with an Intel PXE OROM in a VMware > hosted platform with 0 issues. > >> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0" 200 26813 >> "" "iPXE/1.0.0+ (09c5)" This is the iPXE version that comes bundled with qemu as the default qemu boot rom. -------------- next
2013 Jun 06
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On 06/06/2013 01:25 AM, Thomas B?chler wrote: > Am 06.06.2013 07:00, schrieb Gene Cumm: >> iPXE details. My testing was with an Intel PXE OROM in a VMware >> hosted platform with 0 issues. >> >>> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0" >>> 200 26813 "" "iPXE/1.0.0+ (09c5)" > > This is the iPXE
2013 Jun 06
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
Am 06.06.2013 22:42, schrieb H. Peter Anvin: > On 06/06/2013 01:25 AM, Thomas B?chler wrote: >> Am 06.06.2013 07:00, schrieb Gene Cumm: >>> iPXE details. My testing was with an Intel PXE OROM in a VMware >>> hosted platform with 0 issues. >>> >>>> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0" >>>> 200 26813
2013 Jun 06
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On 06/06/2013 01:56 PM, Thomas B?chler wrote: >> >> With *which version* of Qemu? > > As Gerardo posted already, 1.5.0. > OK. Sorry, that came across stronger than I meant it to. -hpa
2013 Jun 06
1
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On 06/06/2013 02:00 AM, Gene Cumm wrote: > On Wed, Jun 5, 2013 at 8:29 PM, Gerardo Exequiel Pozzi > <vmlinuz386 at yahoo.com.ar> wrote: >> Hello, >> >> First, this setup works fine without any error in syslinux 4.06 as show >> below. >> >> For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2] >> directories (~2MB each) are uploaded
2013 Jun 07
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Wed, Jun 5, 2013 at 8:29 PM, Gerardo Exequiel Pozzi <vmlinuz386 at yahoo.com.ar> wrote: > [#1] > https://dl.dropboxusercontent.com/u/88891866/archiso_syslinux_406.tar.xz > https://dl.dropboxusercontent.com/u/88891866/archiso_syslinux_406.tar.xz.sig > > [#2] > https://dl.dropboxusercontent.com/u/88891866/archiso_syslinux_510.tar.xz >
2013 Jun 10
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Sat, 08 Jun, at 11:57:34AM, Gene Cumm wrote: > To minimize impact and convey the extent of the change, perhaps change to > ';' immediately and make another release, probably 5.20 and this week. This chunk of ftp_readdir() caught my eye, } else if ((p = strchr(buf, ';'))) { /* VMS/Multinet format */ if (p > buf+4 && !memcmp(p-4, ".DIR",
2013 Jun 10
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On 06/10/2013 06:35 AM, Matt Fleming wrote: > On Sat, 08 Jun, at 11:57:34AM, Gene Cumm wrote: >> To minimize impact and convey the extent of the change, perhaps change to >> ';' immediately and make another release, probably 5.20 and this week. > > This chunk of ftp_readdir() caught my eye, > > } else if ((p = strchr(buf, ';'))) { > /*
2013 Jun 10
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Mon, 10 Jun, at 07:24:21AM, H. Peter Anvin wrote: > VMS pathnames with semicolons are the same as in iso9660 -- version > numbers that are extremely rarely used. However, since file listings > display them, they have to be stripped off. > > So it is probably OK for the four people in the world that might have a > VMS server. Next thing I see is HTTP paths. Problem? We