Bug Reports, Requests, HowTo's about Tiny PXE Server

Hi Erwan ,In DHCP mode , and the TinyPXE server vertion is 1.0.0.19 , is there much newer version ?

Hi Erwan ,In DHCP mode , and the TinyPXE server vertion is 1.0.0.19 , is there much newer version ?

Hi,
If you downloaded from reboot.pro a few days ago it should be fine.
Tiny Pxe Server will provide an IP if this IP is free (does not respond to ping).
Would you be able to run a wireshark capture on the server side and share it with me?

I have introduced a change lately (see changelog) around dhcp provisionning and i want to make sure i did not introduce a bug.

Thanks,
Erwan.

Hi Erwan, I have mailed to your gmail , thanks very much!!

Hi Erwan, I have mailed to your gmail , thanks very much!!

 

Thanks, got it !

 

Normal dhcp process is : Discover -> Offer -> Request -> Ack (D.O.R.A).

In your case, the client does not seem to care about the offer and sends another discover (using the same transaction ID).

On the second discover, I send a new ip (since the previous one is "locked" for 60 seconds").

The client then sends a request but with a 0.0.0.0 ip in ciaddr field (but opt 50 - requested ip is correct).

I finally send a ack and we may think it is done at this point but the client goes back to the discover phase

 

I need to check if sending a discover twice is a to be expected behavior in which case I need to patch Tiny PXE Server : if a second discover comes in with a known transaction ID, I need to re offer the same ip.

If so (to be expected), that could mean that the dhcp server is currently broken (but not the pxe server).

If not (to be expected), that could be a bug with your nic driver, operating system, etc ...

 

I am away on holidays right now and wont be able to code until next week.

 

In the meantime thus a few things could help :

-make sure your firewall is not interfering on the server side (disable it temporarily?)

-which version of winpe is it?

-provide me your TPS setup (screenshot of the main window and/or config.ini)

-provide me a screenshot of the main window so that I can see the log window.

-if you have multiple interfaces (on the server) make sure you tick the bind checkbox

 

Regards,

Erwan

 

EDIT : also found a bug in the dhcp ack -> i am using the first offered ip, not the last one...

that is probably the issue and why the client goes back to discover after my ack.

Hi Erwan, sorry for trouble U and Enjoy your holidays

 

For your question:

1. firewall is disabled

2. winpe is win8PE

3. for screenshoot, I don't know how to attached image ,sorry , I'll mail U

4, I just use my PC and install server2008 as server,haha!

Hi Erwan, sorry for trouble U and Enjoy your holidays

 

For your question:

1. firewall is disabled

2. winpe is win8PE

3. for screenshoot, I don't know how to attached image ,sorry , I'll mail U

4, I just use my PC and install server2008 as server,haha!

 

Hi MickeyXM,

 

Thanks for your patience and detailed reports.

I believe the issue is fixed (when 2 discovers were sent from the same client host/transaction id, TPS would mess up the DHCP ACK).

Download latest version and let me know.

 

Regards,

Erwan

Hi Erwan:

     How to get the latest version? I just saw the 1.0.0.19

Erwan does not change the version number every minor update.

 

You should just download the current version again. The version number is the same, but the application was certainly updated.

how can i get your TinyPXE for X64

Hi Sfor:

Gotit ,thanks very much!

how can i get your TinyPXE for X64

 

Hi hhh333,

I did not plan a 64bits version as I did not see a benefit for it.

The 32bits version will work fine on a x64 platform.

 

What are your needs?

 

Regards,

Erwan

Please compile a version for x64,because my win10pe64 can'nt run any 32-bit application program.(at present,not found a method to let Wow64 working)

Please compile a version for x64,because my win10pe64 can'nt run any 32-bit application program.(at present,not found a method to let Wow64 working)

 

I'll do my best (I initiated the project today).

 

However, because I am using a component (indy 9.x) meant for delphi 7 it will take some time as I can only compile x64 with delphi xe 5 (which supports only indy 10.x).

@erwan
No rush - enjoy the holidays.

Misty

P.s. not 100% sure this is the only issue as using nics.txt also failed - albeit later in the boot process.

 

I believe this issue should be fixed in latest version.

@erwan.l
Thanks. I'll test over the next few days and report back.

Thank you very much! I'm waiting...........very much looking forward to use your x64 version.

erwan.l - your TPS file pxesrv.zip is damaged:

 Windows_build-in_Unzip.png   12.46KB   0 downloads  WinRAR.png   18.15KB   0 downloads  7-Zip.png   25.72KB   0 downloads

erwan.l - your TPS file pxesrv.zip is damaged:

Windows_build-in_Unzip.png WinRAR.png 7-Zip.png

 

Thanks for letting me know !

Now fixed !

 

Regards,

Erwan

Hi Erwan.

Please update the download page. The current Download (Contributed Files) states the download file size is 4.18MB - it's actually 502 KB and is missing the files directory and some other files.

The Download (Mirrors) states the download file size is 3.71MB - it's actually 4.17 MB.

There's no easy way to differentiate between the recent 1.0.0.19 versions so I tested both.

When using the pxesrv.exe included in the Download (Mirrors) package, RIS failed with -

19:40:19 NCR:requested VID:0x1022 PID:0x2000 Subsys:0x20001022
19:40:20 NCR:could not find parse driver informations

Using nics.txt I received the 0xBB error.

The version of pxesrv.exe included in the Download (Contributed Files) package has a file size (when unpacked) of 926 KB (948,736 bytes) with the following checksums -

• 3CC8D0C4E9B99B70DEFC29A384BDD0C1 - MD5
• 68A1436C0F49F87301B177D6247A1A37F9BC0EA9 - SHA-1

Tested this version and managed to complete the initial stages of a Windows XP RIS installation when using nics.txt and the built in inf parse function. Great work Haven't completed the installation due to time restrictions. Will try this tomorrow and will report back if there are any issues.



Regards,

Misty

P.s. Noticed a minor bug - the poolstart in config.ini appears to be ignored in the recent builds.

Hi Misty,

 

Thanks for this update.

 

The zip files has been updates and the "files" folder is back.

 

About the zip size, I believe this reboot.pro interface giving this (erroneous) information.

 

About the poolstart, sounds like a regression bug after the dhcp changes I introduced lately : will check it out !

 

Regards,

Erwan

Fixed : poolstart bug.

 

Thanks Misty !

what progress about 64bit version? I'm waiting......

what progress about 64bit version? I'm waiting......

I would be curious to understand what would you expect from a 64 bit version (in terms of "betterings").

 

I mean, do you expect it to be "faster" or to serve "better IP's"?

 

Wonko

Please compile a version for x64,because my win10pe64 can'nt run any 32-bit application program.(at present,not found a method to let Wow64 working)

Please upload your win10pe64 to test Tiny PXE x86. This is strange because x64 systems should support x86 programs.

Please upload your win10pe64 to test Tiny PXE x86. This is strange because x64 systems should support x86 programs.

 

No,

Without WoW64, WinPE x64 cannot run any 32bit app.

However, there are a couple of WinPE projects by Wimb and by CHrisR that do have WoW64 support in a 64bit WinPE.

It requires adding a lot of files and registry keys to WinPE x64 in order to make 32bit apps work.