Jump to content











Photo
- - - - -

Horrible transfer rate


  • Please log in to reply
12 replies to this topic

#1 Videogamer555

Videogamer555
  • Members
  • 7 posts
  •  
    United States

Posted 25 May 2015 - 09:20 AM

Not sure if this is something wrong with the Microsoft Loopback Adapter driver that I installed, Microsoft Virtual PC 2007, or with TFTPD32/64. I'm trying to network boot a virtual machine running in Microsoft Virtual PC 2007. So I installed the loopback driver, and assigned it an IP address of 190.0.0.1 and mask of 255.255.255.0 on my host computer. In Virtual PC 2007 I made sure that the machine in question was set to use that network adapter in the Virtual PC settings for that particular virtual machine.

On the TFTPD end of things, I tried both the 64 and 32 bit versions, but I always had way to slow of a transfer rate. At best I only got about 30kbytes/s (but usually it was well under 10kbytes/s). Keep in mind that the Microsoft Loopback Adapter is supposed to support up to 10Mb/s (not sure if this number is supposed to mean 10 MBytes or 10 MBits, but either way, it would be a LOT faster speed than I've been getting). As a result, even booting DOS 6.22 through this technique took at least a minute or two, when it should have only taken a few seconds.

Here's a screencap of the transfer screen showing a horribly low transfer rate of only 1408 bytes/s.



V2rmdXW.png




Any ideas as to what might be wrong? Or how to fix it?

Edited by Videogamer555, 25 May 2015 - 09:20 AM.


#2 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1918 posts
  • Location:Nantes - France
  •  
    France

Posted 25 May 2015 - 10:43 AM

Not sure if this is something wrong with the Microsoft Loopback Adapter driver that I installed, Microsoft Virtual PC 2007, or with TFTPD32/64. I'm trying to network boot a virtual machine running in Microsoft Virtual PC 2007. So I installed the loopback driver, and assigned it an IP address of 190.0.0.1 and mask of 255.255.255.0 on my host computer. In Virtual PC 2007 I made sure that the machine in question was set to use that network adapter in the Virtual PC settings for that particular virtual machine.

On the TFTPD end of things, I tried both the 64 and 32 bit versions, but I always had way to slow of a transfer rate. At best I only got about 30kbytes/s (but usually it was well under 10kbytes/s). Keep in mind that the Microsoft Loopback Adapter is supposed to support up to 10Mb/s (not sure if this number is supposed to mean 10 MBytes or 10 MBits, but either way, it would be a LOT faster speed than I've been getting). As a result, even booting DOS 6.22 through this technique took at least a minute or two, when it should have only taken a few seconds.

Here's a screencap of the transfer screen showing a horribly low transfer rate of only 1408 bytes/s.



V2rmdXW.png




Any ideas as to what might be wrong? Or how to fix it?

 

what boot strap are you using? pxelinux? ipxe? gpxe? ...

the "full" ipxe (i.e not the undi version) gives me the best performance.

 

also, if possible, drop the tftp protocol, and use http.

 

last, although i think the issue is not at the server side, but at the pxe client side, try with another tftp server.



#3 Videogamer555

Videogamer555
  • Members
  • 7 posts
  •  
    United States

Posted 25 May 2015 - 06:59 PM

what boot strap are you using? pxelinux? ipxe? gpxe? ...

the "full" ipxe (i.e not the undi version) gives me the best performance.

 

also, if possible, drop the tftp protocol, and use http.

 

last, although i think the issue is not at the server side, but at the pxe client side, try with another tftp server.

 

I was using the file pxelinux.0, from the absolute latest version of Syslinux (version 6.0.3). Pxelinux.0 is THE standard file for PXE booting. The rest may have more features, but pxelinux.0 is suppost to be guarentied to work and have best performance.

 

As for protocol, TFTP is the protocol that is EXPECTED by a computer that is doing a PXE boot. A computer booting with PXE network boot, is not going to make an HTTP request for a file. It's going to make a TFTP request. I'm not sure where you are getting this idea that TFTP would work.


Edited by Videogamer555, 25 May 2015 - 06:59 PM.


#4 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13497 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 25 May 2015 - 07:27 PM

Pxelinux.0 is THE standard file for PXE booting. The rest may have more features, but pxelinux.0 is suppost to be guarentied to work and have best performance.

As for protocol, TFTP is the protocol that is EXPECTED by a computer that is doing a PXE boot. A computer booting with PXE network boot, is not going to make an HTTP request for a file. It's going to make a TFTP request.

Well, you asked:

Any ideas as to what might be wrong? Or how to fix it?

And some ideas were given to you, but seemingly you know on the specific topic much more than the member that attempted to help you whom BTW is a developer of a IMHO nice alternative to TFTP32 and the actual "resident expert" about network booting :
http://reboot.pro/to...iny-pxe-server/


:duff:
Wonko

#5 Videogamer555

Videogamer555
  • Members
  • 7 posts
  •  
    United States

Posted 25 May 2015 - 09:56 PM

Well, you asked:
And some ideas were given to you, but seemingly you know on the specific topic much more than the member that attempted to help you whom BTW is a developer of a IMHO nice alternative to TFTP32 and the actual "resident expert" about network booting :
http://reboot.pro/to...iny-pxe-server/


:duff:
Wonko

Actually I was going based on everything I read on the net. I've never seen any website which has tutorials for PXE booting mention using anything other than TFTP for protocol and pxelinux.0 for the bootloader.

 

Now after reading your comment and doing some further research, I found there's some alternate version of the bootloader called lpxelinux.0 (that's a lowercase L, not an uppercase i), which natively supports using HTTP boot. However, there's VERY LITTLE documentation on using lpxelinux.0. I am looking for a bare-minimum configuration. No boot menu. Just boot straight to a DOS disk image.

 

By the way, the biggest problem I have right now is getting the file lpxelinux.0 to even be recognized by TFTPD64. It seems that even when I configure DHCP boot file to be lpxelinux.0 that it doesn't even try to send the file, because on the client computer it keeps giving the error "file not found", suggesting that TFTPD64 was unable to send the file to the client PC, thus causing the client to be unable to find the requested file (because the server never sent it).


Edited by Videogamer555, 25 May 2015 - 10:11 PM.


#6 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1918 posts
  • Location:Nantes - France
  •  
    France

Posted 26 May 2015 - 05:58 AM

Pxelinux is not the only pxe boot firmware.

Have a look at ipxe, successor of gpxe.

 

Actually, pxelinux integrates this firmware (which results in ipxelinux and before that gpxelinux).

 

Once the boot firmware has been downloaded (thru tftp), then ipxe can use other protocol (http for example) which is most quicker.

 

Also, the drivers implementation (according to my experience) is better in ipxe which again yield to better performances.



#7 Videogamer555

Videogamer555
  • Members
  • 7 posts
  •  
    United States

Posted 26 May 2015 - 06:19 AM

Pxelinux is not the only pxe boot firmware.

Have a look at ipxe, successor of gpxe.

 

Actually, pxelinux integrates this firmware (which results in ipxelinux and before that gpxelinux).

 

Once the boot firmware has been downloaded (thru tftp), then ipxe can use other protocol (http for example) which is most quicker.

 

Also, the drivers implementation (according to my experience) is better in ipxe which again yield to better performances.

 

 

There's also something called lpxelinux.0 (that's Lpxelinux., with a lowercase L). It supposedly is a replacement for pxelinux.0 in that it integrates the http that is used by ipxelinux.0 and gpxelinux.0 (normally pxelinux.0 has to be used in conjunction with gpxelinux.0 or ipxelinux.0 if you want to use HTTP, but lpxelinux.0 is supposed to be able to work standalone with HTTP). Can you help me get going with lpxelinux.0?

 

By the way, when I look in my SysLinux folders, I can't find any file called ipxe or gpxe. I can only find files called lpxelinux.0 and gpxelinux.0. There isn't even anything called ipxelinux.0. I'm looking at the absolute latest release of SysLinux, which is version 6.0.3.

 

By the way, my PC comes with a PXE boot capabilty. Short of flashing the BIOS of my computer with a hacked firmware, my computer doesn't have any gPXE or iPXE capability. I'm not about to take the dangerous step of flashing my computer's BIOS with anything other than official firmware. And by the way, I'm actually testing this on a virtual machine, in Microsoft Virtual PC, so there's absolutely no way to hack its firmware for testing anything as it is a software implementation of a PC (not actual physical hardware).


Edited by Videogamer555, 26 May 2015 - 06:22 AM.


#8 Videogamer555

Videogamer555
  • Members
  • 7 posts
  •  
    United States

Posted 26 May 2015 - 06:30 AM

By the way, here's the log text for loading just pxelinux.0 (which has dependancies of a config file, and a file called ldlinux.c32), which loads memdisk, which loads a DOS disk image (the simplest immaginable network boot procedure). Note that the log is incomplete, because if I waited for the log to be complete, it would have scrolled off the top of the window, preventing retrieval of the earliest parts of the log. So I copied it before it started scrolling the text off the top of the window. One thing I notice, which could be what's slowing it down, is there's a LOT of "Ack block # ignored (received twice)" messages. Not sure why these are occuring.

 

Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:03:FF:F0:63:D8 [25/05 23:26:06.796]
DHCP: proposed address 190.0.0.100 [25/05 23:26:09.909]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:03:FF:F0:63:D8 [25/05 23:26:10.787]
Previously allocated address 190.0.0.100 acked [25/05 23:26:10.787]
Connection received from 190.0.0.100 on port 2070 [25/05 23:26:10.791]
Read request for file <pxelinux.0>. Mode octet [25/05 23:26:10.791]
OACK: <tsize=46909,> [25/05 23:26:10.812]
Using local port 56649 [25/05 23:26:10.812]
Peer returns ERROR <TFTP Aborted> -> aborting transfer [25/05 23:26:10.814]
Connection received from 190.0.0.100 on port 2071 [25/05 23:26:10.815]
Read request for file <pxelinux.0>. Mode octet [25/05 23:26:10.815]
OACK: <blksize=1456,> [25/05 23:26:10.815]
Using local port 56650 [25/05 23:26:10.815]
<pxelinux.0>: sent 33 blks, 46909 bytes in 1 s. 1 blk resent [25/05 23:26:11.879]
Connection received from 190.0.0.100 on port 49152 [25/05 23:26:11.893]
Read request for file <ldlinux.c32>. Mode octet [25/05 23:26:11.894]
OACK: <tsize=122308,blksize=1408,> [25/05 23:26:11.905]
Using local port 56651 [25/05 23:26:11.905]
Ack block 1 ignored (received twice) [25/05 23:26:11.989]
Ack block 1 ignored (received twice) [25/05 23:26:12.099]
Ack block 1 ignored (received twice) [25/05 23:26:12.261]
Ack block 1 ignored (received twice) [25/05 23:26:12.431]
Ack block 1 ignored (received twice) [25/05 23:26:12.649]
Ack block 1 ignored (received twice) [25/05 23:26:12.930]
Ack block 1 ignored (received twice) [25/05 23:26:13.240]
Ack block 1 ignored (received twice) [25/05 23:26:13.631]
Ack block 1 ignored (received twice) [25/05 23:26:14.130]
Ack block 1 ignored (received twice) [25/05 23:26:14.678]
Ack block 1 ignored (received twice) [25/05 23:26:15.327]
Ack block 4 ignored (received twice) [25/05 23:26:15.619]
Ack block 4 ignored (received twice) [25/05 23:26:15.733]
Ack block 4 ignored (received twice) [25/05 23:26:15.900]
Ack block 4 ignored (received twice) [25/05 23:26:16.033]
Ack block 4 ignored (received twice) [25/05 23:26:16.282]
Ack block 4 ignored (received twice) [25/05 23:26:16.543]
Ack block 4 ignored (received twice) [25/05 23:26:16.882]
Ack block 4 ignored (received twice) [25/05 23:26:17.272]
Ack block 4 ignored (received twice) [25/05 23:26:17.769]
Ack block 4 ignored (received twice) [25/05 23:26:18.297]
Ack block 4 ignored (received twice) [25/05 23:26:18.956]
Ack block 4 ignored (received twice) [25/05 23:26:19.786]
Ack block 4 ignored (received twice) [25/05 23:26:20.776]
Ack block 5 ignored (received twice) [25/05 23:26:21.777]
Ack block 18 ignored (received twice) [25/05 23:26:21.891]
Ack block 18 ignored (received twice) [25/05 23:26:21.988]
Ack block 18 ignored (received twice) [25/05 23:26:22.154]
Ack block 18 ignored (received twice) [25/05 23:26:22.315]
Ack block 18 ignored (received twice) [25/05 23:26:22.530]
Ack block 18 ignored (received twice) [25/05 23:26:22.807]
Ack block 18 ignored (received twice) [25/05 23:26:23.137]
Ack block 18 ignored (received twice) [25/05 23:26:23.535]
Ack block 18 ignored (received twice) [25/05 23:26:24.023]
Ack block 18 ignored (received twice) [25/05 23:26:24.577]
Ack block 18 ignored (received twice) [25/05 23:26:25.226]
Ack block 18 ignored (received twice) [25/05 23:26:26.047]
Ack block 18 ignored (received twice) [25/05 23:26:27.040]
Ack block 19 ignored (received twice) [25/05 23:26:28.041]
<ldlinux.c32>: sent 87 blks, 122308 bytes in 17 s. 2 blks resent [25/05 23:26:28.060]
Connection received from 190.0.0.100 on port 49153 [25/05 23:26:28.067]
Read request for file <pxelinux.cfg/f1393b17-2efb-b343-a188-c9ff98267c3a>. Mode octet [25/05 23:26:28.067]
File <pxelinux.cfg\f1393b17-2efb-b343-a188-c9ff98267c3a> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.068]
Connection received from 190.0.0.100 on port 49154 [25/05 23:26:28.069]
Read request for file <pxelinux.cfg/01-00-03-ff-f0-63-d8>. Mode octet [25/05 23:26:28.069]
File <pxelinux.cfg\01-00-03-ff-f0-63-d8> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.072]
Connection received from 190.0.0.100 on port 49155 [25/05 23:26:28.073]
Read request for file <pxelinux.cfg/BE000064>. Mode octet [25/05 23:26:28.074]
File <pxelinux.cfg\BE000064> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.074]
Connection received from 190.0.0.100 on port 49156 [25/05 23:26:28.075]
Read request for file <pxelinux.cfg/BE00006>. Mode octet [25/05 23:26:28.075]
File <pxelinux.cfg\BE00006> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.076]
Connection received from 190.0.0.100 on port 49157 [25/05 23:26:28.077]
Read request for file <pxelinux.cfg/BE0000>. Mode octet [25/05 23:26:28.078]
File <pxelinux.cfg\BE0000> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.078]
Connection received from 190.0.0.100 on port 49158 [25/05 23:26:28.079]
Read request for file <pxelinux.cfg/BE000>. Mode octet [25/05 23:26:28.079]
File <pxelinux.cfg\BE000> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.080]
Connection received from 190.0.0.100 on port 49159 [25/05 23:26:28.081]
Read request for file <pxelinux.cfg/BE00>. Mode octet [25/05 23:26:28.083]
File <pxelinux.cfg\BE00> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.083]
Connection received from 190.0.0.100 on port 49160 [25/05 23:26:28.085]
Read request for file <pxelinux.cfg/BE0>. Mode octet [25/05 23:26:28.085]
File <pxelinux.cfg\BE0> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.086]
Connection received from 190.0.0.100 on port 49161 [25/05 23:26:28.086]
Read request for file <pxelinux.cfg/BE>. Mode octet [25/05 23:26:28.087]
File <pxelinux.cfg\BE> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.087]
Connection received from 190.0.0.100 on port 49162 [25/05 23:26:28.087]
Read request for file <pxelinux.cfg/B>. Mode octet [25/05 23:26:28.087]
File <pxelinux.cfg\B> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.088]
Connection received from 190.0.0.100 on port 49163 [25/05 23:26:28.088]
Read request for file <pxelinux.cfg/default>. Mode octet [25/05 23:26:28.088]
OACK: <tsize=30,blksize=1408,> [25/05 23:26:28.107]
Using local port 59650 [25/05 23:26:28.107]
<pxelinux.cfg\default>: sent 1 blk, 30 bytes in 0 s. 0 blk resent [25/05 23:26:28.108]
Connection received from 190.0.0.100 on port 49164 [25/05 23:26:28.108]
Read request for file <memdisk.c32>. Mode octet [25/05 23:26:28.109]
File <memdisk.c32> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.109]
Connection received from 190.0.0.100 on port 49165 [25/05 23:26:28.109]
Read request for file <memdisk.img>. Mode octet [25/05 23:26:28.110]
File <memdisk.img> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.110]
Connection received from 190.0.0.100 on port 49166 [25/05 23:26:28.110]
Read request for file <memdisk.bss>. Mode octet [25/05 23:26:28.111]
File <memdisk.bss> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.111]
Connection received from 190.0.0.100 on port 49167 [25/05 23:26:28.112]
Read request for file <memdisk.bin>. Mode octet [25/05 23:26:28.112]
File <memdisk.bin> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.112]
Connection received from 190.0.0.100 on port 49168 [25/05 23:26:28.113]
Read request for file <memdisk.bs>. Mode octet [25/05 23:26:28.113]
File <memdisk.bs> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.113]
Connection received from 190.0.0.100 on port 49169 [25/05 23:26:28.114]
Read request for file <memdisk.0>. Mode octet [25/05 23:26:28.115]
File <memdisk.0> : error 2 in system call CreateFile The system cannot find the file specified. [25/05 23:26:28.115]
Connection received from 190.0.0.100 on port 49170 [25/05 23:26:28.119]
Read request for file <memdisk>. Mode octet [25/05 23:26:28.120]
OACK: <tsize=26140,blksize=1408,> [25/05 23:26:28.121]
Using local port 59657 [25/05 23:26:28.121]
Ack block 4 ignored (received twice) [25/05 23:26:28.255]
Ack block 4 ignored (received twice) [25/05 23:26:28.363]
Ack block 4 ignored (received twice) [25/05 23:26:28.516]
Ack block 4 ignored (received twice) [25/05 23:26:28.684]
Ack block 4 ignored (received twice) [25/05 23:26:28.913]
Ack block 4 ignored (received twice) [25/05 23:26:29.174]
Ack block 4 ignored (received twice) [25/05 23:26:29.513]
Ack block 4 ignored (received twice) [25/05 23:26:29.896]
Ack block 4 ignored (received twice) [25/05 23:26:30.386]
Ack block 4 ignored (received twice) [25/05 23:26:30.933]
Ack block 4 ignored (received twice) [25/05 23:26:31.606]
Ack block 4 ignored (received twice) [25/05 23:26:32.416]
Ack block 5 ignored (received twice) [25/05 23:26:33.416]
Ack block 9 ignored (received twice) [25/05 23:26:33.482]
Ack block 9 ignored (received twice) [25/05 23:26:33.581]
Ack block 9 ignored (received twice) [25/05 23:26:33.743]
Ack block 9 ignored (received twice) [25/05 23:26:33.899]
Ack block 9 ignored (received twice) [25/05 23:26:34.133]
Ack block 9 ignored (received twice) [25/05 23:26:34.408]
Ack block 9 ignored (received twice) [25/05 23:26:34.738]
Ack block 9 ignored (received twice) [25/05 23:26:35.112]
Ack block 9 ignored (received twice) [25/05 23:26:35.617]
Ack block 9 ignored (received twice) [25/05 23:26:36.156]
Ack block 9 ignored (received twice) [25/05 23:26:36.830]
Ack block 9 ignored (received twice) [25/05 23:26:37.646]
Ack block 9 ignored (received twice) [25/05 23:26:38.626]
Ack block 10 ignored (received twice) [25/05 23:26:39.626]
<memdisk>: sent 19 blks, 26140 bytes in 11 s. 2 blks resent [25/05 23:26:39.630]
Connection received from 190.0.0.100 on port 49171 [25/05 23:26:39.635]
Read request for file <DOS.img>. Mode octet [25/05 23:26:39.638]
OACK: <tsize=1474560,blksize=1408,> [25/05 23:26:39.663]
Using local port 52486 [25/05 23:26:39.664]
Ack block 9 ignored (received twice) [25/05 23:26:39.797]
Ack block 9 ignored (received twice) [25/05 23:26:39.887]
Ack block 9 ignored (received twice) [25/05 23:26:40.051]
Ack block 9 ignored (received twice) [25/05 23:26:40.218]
Ack block 9 ignored (received twice) [25/05 23:26:40.440]
Ack block 9 ignored (received twice) [25/05 23:26:40.713]
Ack block 9 ignored (received twice) [25/05 23:26:41.050]
Ack block 9 ignored (received twice) [25/05 23:26:41.441]
Ack block 9 ignored (received twice) [25/05 23:26:41.933]
Ack block 9 ignored (received twice) [25/05 23:26:42.478]
Ack block 9 ignored (received twice) [25/05 23:26:43.133]
Ack block 9 ignored (received twice) [25/05 23:26:43.967]
Ack block 9 ignored (received twice) [25/05 23:26:44.961]
Ack block 10 ignored (received twice) [25/05 23:26:45.961]
Ack block 41 ignored (received twice) [25/05 23:26:46.047]
Ack block 41 ignored (received twice) [25/05 23:26:46.155]
Ack block 41 ignored (received twice) [25/05 23:26:46.322]
Ack block 41 ignored (received twice) [25/05 23:26:46.484]
Ack block 41 ignored (received twice) [25/05 23:26:46.707]
Ack block 41 ignored (received twice) [25/05 23:26:46.980]
Ack block 41 ignored (received twice) [25/05 23:26:47.313]
Ack block 41 ignored (received twice) [25/05 23:26:47.696]
Ack block 41 ignored (received twice) [25/05 23:26:48.177]
Ack block 41 ignored (received twice) [25/05 23:26:48.742]
Ack block 41 ignored (received twice) [25/05 23:26:49.391]
 


Edited by Videogamer555, 26 May 2015 - 06:33 AM.


#9 Videogamer555

Videogamer555
  • Members
  • 7 posts
  •  
    United States

Posted 26 May 2015 - 06:48 AM

By the way, when using an alternate DHCP and TFTP network booting program  simply called "DHCP Server for Windows", I get much better transfer rates, with the entire PXE boot (including of the loading of DOS from the disk image) being completed in less than half a minute. My TFTP root folder's structure (with pxelinux.0 and other files) for this other program being the exact same as the TFTPD64/32 TFTP root folder's structure. Yet with this alternate program I get much better performance. By the way, for comparison, here's the complete log from this other program's network boot. Notice there's not a bunch of "Ack block #" messages in this log, as it performed flawlessly. (oh, and here's the other program's official website http://www.dhcpserver.de/cms/ )

 

[05/25/2015 23:38:28] DHCP Server V2.4.4.0 started as Application
[05/25/2015 23:38:28] NetworkAdapter Initialization returns 0
[05/25/2015 23:38:28] Adapter 0 with IP address 190.0.0.1 found (pAdap=0x0289e528)
[05/25/2015 23:38:28] Adapter 1 with IP address 10.0.0.7 found but not used
[05/25/2015 23:39:18] Adapter 1 has recognized an incoming DHCP request
[05/25/2015 23:39:18] DHCP message = DHCPDISCOVER
[05/25/2015 23:39:18]    requested options: 1 2 3 5 6 11 12 13 15 16 17 18 43 54 60 67 128 129 130 131 132 133 134 135
[05/25/2015 23:39:18] client identifier (option 61) is not recognized
[05/25/2015 23:39:18] Lookup client data for physical address "00-03-FF-F0-63-D8" / client_id "00-03-FF-F0-63-D8"
[05/25/2015 23:39:18] Client 00-03-FF-F0-63-D8 is configured with the IP address 190.0.0.100
[05/25/2015 23:39:18] Response: offer the configured IP address (lease time = 1800)
[05/25/2015 23:39:18] Sending a broadcast response to the client
[05/25/2015 23:39:18] Connection 1: sending top queue packet
[05/25/2015 23:39:22] Adapter 1 has recognized an incoming DHCP request
[05/25/2015 23:39:22] DHCP message = DHCPREQUEST
[05/25/2015 23:39:22]    requested options: 1 2 3 5 6 11 12 13 15 16 17 18 43 54 60 67 128 129 130 131 132 133 134 135
[05/25/2015 23:39:22] client identifier (option 61) is not recognized
[05/25/2015 23:39:22] Lookup client data for physical address "00-03-FF-F0-63-D8" / client_id "00-03-FF-F0-63-D8"
[05/25/2015 23:39:22] Client 00-03-FF-F0-63-D8 is configured with the IP address 190.0.0.100
[05/25/2015 23:39:22] Response: hand out the configured IP address (lease time = 1800)
[05/25/2015 23:39:22] Sending a broadcast response to the client
[05/25/2015 23:39:22] Connection 1: sending top queue packet
[05/25/2015 23:39:22] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:22] TFTP RRQ started on port_index=0: C:\Users\BenHut\Downloads\DHCP Server\tftproot\pxelinux.0
[05/25/2015 23:39:22] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:22] TFTP RRQ started on port_index=1: C:\Users\BenHut\Downloads\DHCP Server\tftproot\pxelinux.0
[05/25/2015 23:39:22] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:22] TFTP RRQ started on port_index=2: C:\Users\BenHut\Downloads\DHCP Server\tftproot\ldlinux.c32
[05/25/2015 23:39:22] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:22] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\pxelinux.cfg\f1393b17-2efb-b343-a188-c9ff98267c3a failed, 0x0
[05/25/2015 23:39:22] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:22] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\pxelinux.cfg\01-00-03-ff-f0-63-d8 failed, 0x0
[05/25/2015 23:39:22] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:22] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\pxelinux.cfg\BE000064 failed, 0x0
[05/25/2015 23:39:22] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:22] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\pxelinux.cfg\BE00006 failed, 0x0
[05/25/2015 23:39:22] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:22] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\pxelinux.cfg\BE0000 failed, 0x0
[05/25/2015 23:39:22] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:22] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\pxelinux.cfg\BE000 failed, 0x0
[05/25/2015 23:39:22] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:22] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\pxelinux.cfg\BE00 failed, 0x0
[05/25/2015 23:39:22] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:22] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\pxelinux.cfg\BE0 failed, 0x0
[05/25/2015 23:39:22] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:22] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\pxelinux.cfg\BE failed, 0x0
[05/25/2015 23:39:22] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:22] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\pxelinux.cfg\B failed, 0x0
[05/25/2015 23:39:22] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:22] TFTP RRQ started on port_index=3: C:\Users\BenHut\Downloads\DHCP Server\tftproot\pxelinux.cfg\default
[05/25/2015 23:39:30] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:30] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\memdisk.c32 failed, 0x0
[05/25/2015 23:39:30] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:30] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\memdisk.img failed, 0x0
[05/25/2015 23:39:30] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:30] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\memdisk.bss failed, 0x0
[05/25/2015 23:39:30] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:30] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\memdisk.bin failed, 0x0
[05/25/2015 23:39:30] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:30] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\memdisk.bs failed, 0x0
[05/25/2015 23:39:30] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:30] TFTP failure: file operation CreateFile C:\Users\BenHut\Downloads\DHCP Server\tftproot\memdisk.0 failed, 0x0
[05/25/2015 23:39:30] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:30] TFTP RRQ started on port_index=4: C:\Users\BenHut\Downloads\DHCP Server\tftproot\memdisk
[05/25/2015 23:39:31] Adapter 3 has recognized an incoming TFTP request
[05/25/2015 23:39:31] TFTP RRQ started on port_index=5: C:\Users\BenHut\Downloads\DHCP Server\tftproot\DOS.img
 


Edited by Videogamer555, 26 May 2015 - 06:50 AM.


#10 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1918 posts
  • Location:Nantes - France
  •  
    France

Posted 26 May 2015 - 07:10 AM

If you are into using another pxe server, then I suggest using my software .

Then I'll be in a better position to troubleshoot with you and go thru logs.

 

Have you checked if you can change the network rom in VirtualPC?

I know this is possible in vmware, could be possible in VPC too.

 

In short we aggree that the sequence is as follows :

-machine pxe -> firmware pxe -> script.

 

Generate your firmware here : advanced / pxe bootstrap (.pxe) / all drivers.

 

Script wise, it would be something like below

#!ipxe
initrd dos622.img
chain memdisk



#11 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13497 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 26 May 2015 - 10:51 AM

Most probably completely unrelated :w00t:, and just as a side note, but personally I would not even THINK of having a path with spaces in it *anywhere* in *any* "booting chain", nor making use of the "Users" folder, most probably it is completely irrelevant in this case :), still when testing I would always use a simple folder name under ROOT, like C:\mynicefolder\ (and yes I am VERY "old school", besides actually old and grumpy).

 

:duff:

Wonko



#12 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1918 posts
  • Location:Nantes - France
  •  
    France

Posted 26 May 2015 - 11:58 AM

Most probably completely unrelated :w00t:, and just as a side note, but personally I would not even THINK of having a path with spaces in it *anywhere* in *any* "booting chain", nor making use of the "Users" folder, most probably it is completely irrelevant in this case :), still when testing I would always use a simple folder name under ROOT, like C:\mynicefolder\ (and yes I am VERY "old school", besides actually old and grumpy).

 

:duff:

Wonko

 

Agreed : i always stick to a simple path as well (c:\pxe, c:\tftproot, etc ...).

 

Side note, the "Ack block x ignored (received twice)" will definitely slow down the transfer.

The tftp client and server seem to talk a slightly different langage (probably down to tftp options).



#13 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13497 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 26 May 2015 - 12:07 PM

Agreed : i always stick to a simple path as well (c:\pxe, c:\tftproot, etc ...). 

Hey, you are even more old school than myself :w00t:, I often exceed the 8.3 for file names  or 11 characters for folder names, but respecting that is even better :).

 

:duff:

Wonko






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users