Jump to content











Photo

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

pxe network boot

  • Please log in to reply
823 replies to this topic

#251 erwan.l

erwan.l

    Platinum Member

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

Posted 19 January 2015 - 09:32 PM

About usability...

 

A nice feature addition would be some control from command line

for example, launch application and start server

(a must if we use it in a batch file)

 

I'd suggest the implementation of a command line feature like:

pxeserv.exe        --> no parameters will launch just as is working now

pxeserv.exe /?    -->  will show all command line options

pxeserv.exe /on  -->  will launch and put online (same as press the online button, if instance exist put online)

pxeserv.exe /off  -->  will stop server (if instance exist, else show alert message)

 

:( ZEE ):

 

Actually the /start command line is already there (but not documented :) ).

 

I could think of an on/off feature (or start/stop ...).

Altough from a batch file you can probably easily "kill" (not as clean as a stop thus) the process.


  • ZEE likes this

#252 Sfor

Sfor

    Newbie

  • Members
  • 24 posts
  •  
    Poland

Posted 27 January 2015 - 10:30 AM

All text fields have been tab re ordered.

Ctrl+O will trigger the online button.

Ctrl+F will trigger the offline button.

 

Should facilitate the use of TinyPXE Server without a mouse.

 

Thank You.

 

Works as described.



#253 ZEE

ZEE

    Member

  • Members
  • 99 posts
  •  
    Portugal

Posted 29 January 2015 - 03:09 PM

Actually the /start command line is already there (but not documented :) ).

 

I could think of an on/off feature (or start/stop ...).

Altough from a batch file you can probably easily "kill" (not as clean as a stop thus) the process.

 

Ahhhhhhhhhhhh...

the old "undocumented switch" trick... OOooohhh....

What else mr. Bond.. ???

 

;)



#254 mrreload

mrreload
  • Members
  • 9 posts
  •  
    United States

Posted 06 February 2015 - 03:10 PM

Thanks for the feedback, opt66 mixed up with opt60 was a indeed a bug.

Nice catch !

 

Please download latest version, delete your config.ini and try again and then let me know.

For the second dns entry, let me review the DHCP rfc and think about it.

 

EDIT : note that in proxydhcp, the dns settings are provided by the DHCP server not by the proxydhcp.

 

Regards,

Erwan

 

The clients getting randomly ignored at PXE boot is still happening. Below is all I see when it starts failing. Taking PXESRV Offline then Online resolves it.

 

10:12:40 AM ROOT=D:\PXEBoot\files\

10:12:40 AM DHCPd:67 started...
10:12:40 AM DHCPd:4011 started...
10:12:40 AM TFPTd started...
10:12:40 AM HTTPd started...
10:12:40 AM PXE share added
10:12:43 AM DHCPd:RELEASE received, MAC:18-03-73-40-F6-98, XID:7640F698
10:12:43 AM DHCPd:DISCOVER received, MAC:18-03-73-40-F6-98, XID:7740F698
10:12:44 AM DHCPd:OFFER sent, IP:0.0.0.0, XID:7740F698
10:12:59 AM DHCPd:REQUEST discarded, MAC:18-03-73-40-F6-98, XID:7740F698
10:12:59 AM PDHCPd:REQUEST received, MAC:18-03-73-40-F6-98, IP:192.168.3.179, XID:7740F698
10:13:00 AM Proxy boot filename empty?
10:13:00 AM PDHCPd:DHCP_ACK sent, IP:192.168.3.179:68, xid:7740F698
10:13:00 AM TFTPd:DoReadFile:ipxe.pxe B:1456 T:0
10:13:00 AM DHCPd:4011 stopped...
10:13:02 AM DHCPd:DISCOVER received, MAC:18-03-73-40-F6-98, XID:A2F3A75C
10:13:04 AM DHCPd:iPXE user-class detected
10:13:04 AM DHCPd:OFFER sent, IP:0.0.0.0, XID:A2F3A75C
10:13:04 AM DHCPd:DISCOVER received, MAC:18-03-73-40-F6-98, XID:A2F3A75C
10:13:04 AM TFTPd:DoReadFile:datcard.ipxe B:1432 T:5419
10:13:04 AM TFTPd:DoReadFile:/art/Dat1.png B:1432 T:263150
10:13:05 AM DHCPd:iPXE user-class detected
10:13:05 AM DHCPd:OFFER sent, IP:0.0.0.0, XID:A2F3A75C
10:13:05 AM DHCPd:REQUEST discarded, MAC:18-03-73-40-F6-98, XID:A2F3A75C
10:13:26 AM HTTPd:Connect: 192.168.3.179, TID=2564
10:13:26 AM HTTPd:Client: 192.168.3.179 [GET] /images/clonezilla/live/vmlinuz
10:13:26 AM HTTPd:Server : Returning /images/clonezilla/live/vmlinuz
10:13:28 AM HTTPd:DisConnect: TID=2564
10:13:28 AM HTTPd:Connect: 192.168.3.179, TID=2960
10:13:28 AM HTTPd:Client: 192.168.3.179 [GET] /images/clonezilla/live/initrd.img
10:13:28 AM HTTPd:Server : Returning /images/clonezilla/live/initrd.img
10:13:47 AM HTTPd:DisConnect: TID=2960
10:13:55 AM DHCPd:DISCOVER discarded, MAC:18-03-73-40-F6-98, XID:11A7F40
10:13:55 AM DHCPd:REQUEST discarded, MAC:18-03-73-40-F6-98, XID:11A7F40
10:13:55 AM HTTPd:Connect: 192.168.3.179, TID=3028
10:13:55 AM HTTPd:Client: 192.168.3.179 [GET] /images/clonezilla/live/filesystem.squashfs
10:13:55 AM HTTPd:Server : Returning /images/clonezilla/live/filesystem.squashfs
10:13:56 AM HTTPd:DisConnect: TID=3028
10:14:07 AM DHCPd:DISCOVER discarded, MAC:18-03-73-40-F6-98, XID:8962010
10:14:07 AM DHCPd:REQUEST discarded, MAC:18-03-73-40-F6-98, XID:8962010
10:14:10 AM TFTPd:DoReadFile:images/clonezilla/live/pacscube-cloner B:0 T:8368
10:29:09 AM DHCPd:DISCOVER received, MAC:98-90-96-B1-CF-AE, XID:96B1CFAE
10:29:10 AM DHCPd:OFFER sent, IP:0.0.0.0, XID:96B1CFAE
10:29:13 AM DHCPd:REQUEST discarded, MAC:98-90-96-B1-CF-AE, XID:96B1CFAE
10:29:17 AM DHCPd:RELEASE received, MAC:98-90-96-B1-CF-AE, XID:96B1CFAE
10:29:17 AM DHCPd:DISCOVER received, MAC:98-90-96-B1-CF-AE, XID:97B1CFAE
10:29:18 AM DHCPd:OFFER sent, IP:0.0.0.0, XID:97B1CFAE
10:29:21 AM DHCPd:REQUEST discarded, MAC:98-90-96-B1-CF-AE, XID:97B1CFAE
10:29:25 AM DHCPd:RELEASE received, MAC:98-90-96-B1-CF-AE, XID:97B1CFAE
10:29:25 AM DHCPd:DISCOVER received, MAC:98-90-96-B1-CF-AE, XID:98B1CFAE
10:29:26 AM DHCPd:OFFER sent, IP:0.0.0.0, XID:98B1CFAE
10:29:29 AM DHCPd:REQUEST discarded, MAC:98-90-96-B1-CF-AE, XID:98B1CFAE
10:29:33 AM DHCPd:RELEASE received, MAC:98-90-96-B1-CF-AE, XID:98B1CFAE
10:29:33 AM DHCPd:DISCOVER received, MAC:98-90-96-B1-CF-AE, XID:99B1CFAE
10:29:34 AM DHCPd:OFFER sent, IP:0.0.0.0, XID:99B1CFAE
10:29:37 AM DHCPd:REQUEST discarded, MAC:98-90-96-B1-CF-AE, XID:99B1CFAE
10:29:41 AM DHCPd:RELEASE received, MAC:98-90-96-B1-CF-AE, XID:99B1CFAE
10:29:41 AM DHCPd:DISCOVER received, MAC:98-90-96-B1-CF-AE, XID:9AB1CFAE
10:29:42 AM DHCPd:OFFER sent, IP:0.0.0.0, XID:9AB1CFAE
10:29:45 AM DHCPd:REQUEST discarded, MAC:98-90-96-B1-CF-AE, XID:9AB1CFAE
10:29:49 AM DHCPd:RELEASE received, MAC:98-90-96-B1-CF-AE, XID:9AB1CFAE
10:29:49 AM DHCPd:DISCOVER received, MAC:98-90-96-B1-CF-AE, XID:9BB1CFAE
10:29:50 AM DHCPd:OFFER sent, IP:0.0.0.0, XID:9BB1CFAE
10:29:53 AM DHCPd:REQUEST discarded, MAC:98-90-96-B1-CF-AE, XID:9BB1CFAE
10:29:57 AM DHCPd:RELEASE received, MAC:98-90-96-B1-CF-AE, XID:9BB1CFAE
10:29:57 AM DHCPd:DISCOVER received, MAC:98-90-96-B1-CF-AE, XID:9CB1CFAE
10:29:58 AM DHCPd:OFFER sent, IP:0.0.0.0, XID:9CB1CFAE
10:30:01 AM DHCPd:REQUEST discarded, MAC:98-90-96-B1-CF-AE, XID:9CB1CFAE
10:30:05 AM DHCPd:RELEASE received, MAC:98-90-96-B1-CF-AE, XID:9CB1CFAE
10:30:05 AM DHCPd:DISCOVER received, MAC:98-90-96-B1-CF-AE, XID:9DB1CFAE
10:30:06 AM DHCPd:OFFER sent, IP:0.0.0.0, XID:9DB1CFAE
10:30:09 AM DHCPd:REQUEST discarded, MAC:98-90-96-B1-CF-AE, XID:9DB1CFAE
10:30:13 AM DHCPd:RELEASE received, MAC:98-90-96-B1-CF-AE, XID:9DB1CFAE


#255 erwan.l

erwan.l

    Platinum Member

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

Posted 06 February 2015 - 03:40 PM

Hi,

 

What do mean by randomly ignored?

You mean pxesrv does not serve leases anymore (at all) or it will server leases sometimes yes / sometimes no?

 

In first case, that would mean the dhcp thread/server has crashed.

In second case, I am clueless for now (but would eventually come with ideas).

 

DHCPd:REQUEST discarded is normal behavior in proxy dhcp mode.

 

10:13:00 AM DHCPd:4011 stopped... is worrying : that would assert the first case mentionned above.

This would require a restart.

 

Regards,

Erwan

 

EDIT:

-share your config.ini

-share a screenshot of TPS running at your end



#256 mrreload

mrreload
  • Members
  • 9 posts
  •  
    United States

Posted 06 February 2015 - 04:22 PM

pxeserv does not serve leases anymore.

 

Not sure how to attach screenshot but here's my config:

 

[arch]
;will over rule the bootp filename or opt67 if the client arch matches one of the below
00006=bootia32.efi
00007=bootx64.efi
[dhcp]
start=1
binl=0
proxydhcp=1
httpd=1
dnsd=0
bind=1
smb=1
root=D:\PXEBoot\files\
filename=ipxe.pxe
altfilename=datcard.ipxe
opt1=255.255.255.0
opt3=192.168.3.1
opt6=10.0.0.0
opt43=0.0.0.0
opt51=86400
opt54=192.168.3.20
opt66=
poolstart=192.168.3.100
poolsize=100
optextra=175.6.1.1.1.8.1.1
opt60=PXEClient
[frmDHCPServer]
top=53
left=897


#257 erwan.l

erwan.l

    Platinum Member

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

Posted 06 February 2015 - 05:26 PM

opt6 is strange.

 

can you run http://erwan.labalec...ver/Dbgview.zipwhile executing pxesrv and send me the log?



#258 mrreload

mrreload
  • Members
  • 9 posts
  •  
    United States

Posted 11 February 2015 - 05:27 PM

Erwan,

here is the collected log since 2/6/15

https://dl.dropboxus...095/TINYPXE.LOG

Interestingly, my guys state that since i put the debugger on it has failed only twice.

 

Could it be these 2 errors I see?

 

SQLite error (5): database is locked 


Edited by mrreload, 11 February 2015 - 05:33 PM.


#259 erwan.l

erwan.l

    Platinum Member

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

Posted 11 February 2015 - 05:39 PM

Erwan,

here is the collected log since 2/6/15

https://dl.dropboxus...095/TINYPXE.LOG

Interestingly, my guys state that since i put the debugger on it has failed only twice.

 

Could it be these 2 errors I see?

 

SQLite error (5): database is locked 

 

thanks for the log : will now have a look at it.

 

the debugger will log anything/everything from all programs on your computer having a debug output.

SQLite error (5): database is locked is not coming from TinyPXE Server but from another software on your system.



#260 mrreload

mrreload
  • Members
  • 9 posts
  •  
    United States

Posted 11 February 2015 - 05:59 PM

Log cleared and then Another error since. 

https://dl.dropboxus...95/TINYPXE1.LOG



#261 erwan.l

erwan.l

    Platinum Member

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

Posted 11 February 2015 - 06:20 PM

Log cleared and then Another error since. 

https://dl.dropboxus...95/TINYPXE1.LOG

 

would you be able to point where in this log you encountered errors (time wise) ?



#262 mrreload

mrreload
  • Members
  • 9 posts
  •  
    United States

Posted 11 February 2015 - 11:35 PM

Unfortunately no. 

 

What we see is sometimes it will respond with the boot file (ipxe.pxe) for random number of PC's booted. Then PXE will not get an IP at all. During this we only see the below type items in TinyPXE:

 

10:30:06 AM DHCPd:OFFER sent, IP:0.0.0.0, XID:9DB1CFAE
10:30:09 AM DHCPd:REQUEST discarded, MAC:98-90-96-B1-CF-AE, XID:9DB1CFAE
10:30:13 AM DHCPd:RELEASE received, MAC:98-90-96-B1-CF-AE, XID:9DB1CFAE
 
Could it be the the DHCP server is to blame? 


#263 erwan.l

erwan.l

    Platinum Member

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

Posted 14 February 2015 - 04:50 PM

Version 1.0.0.19 out.

 

This one brings 2 extra features :

 

1/ The ability to boot directly from the internet (to install a linux distro for example).

 
Example (in config.ini) :
[dhcp]
root=http://archive.ubuntu.com/ubuntu/dists/utopic-updates/main/installer-i386/current/images/netboot
filename=pxelinux.0
 
All files will be directly downloaded from the internet. No files needed locally.
 
This is experimental fow now (and is also depending a lot on your internet speed) but so far it proves to work ok.
I had to use the internet cache thus as first download sometimes takes too much time and the tftp client will timeout and will request the file a second time (this time from cache which is mostly instantaneous).
Also, I load http files in memory for now so TPS can be a bit needy at some point.
 
Edit : if you know any other linux netboot url's, please share.
 
2/ Syslog : if you run TinyPXE Server for a long time, it is better to log to syslog rather to a local file.
[dhcp]
syslog=x.x.x.x
 
Cheers,
Erwan


#264 hason

hason

    Member

  • Members
  • 50 posts
  •  
    Vietnam

Posted 15 February 2015 - 06:28 AM

I was read on this blog

http://labalec.fr/erwan/?p=791

Can you make a video clip? Thank you so much!



#265 mamiller

mamiller
  • Members
  • 3 posts
  •  
    United States

Posted 21 April 2015 - 05:37 PM

I've configured Tiny PXE Server to the point where it works on our network decently, I believe I'm having the same issue that a few others have posted here.

 

After a certain amount of time, DHCP will start timing out on clients. It doesn't matter what kind of computer, I've verified the same issue on VMs, and multiple machines of different types. 

 

All seems to run well for an hour or two, but eventually Clients start receiving a DHCP timeout error. Here is the portion of my log that I believe shows where the error is happening: 

 

4/21/2015 13:12:08:442,1:12:08 PM DHCPd:DISCOVER received, MAC:3C-97-0E-A6-25-3E, XID:EA6253E
4/21/2015 13:12:08:536,1:12:08 PM DHCPd:OFFER sent, IP:0.0.0.0, XID:EA6253E
4/21/2015 13:12:09:050,1:12:09 PM DHCPd:INFORM received, MAC:1C-C1-DE-33-34-0E, XID:6B71251A
4/21/2015 13:12:12:451,1:12:12 PM DHCPd:REQUEST discarded, MAC:3C-97-0E-A6-25-3E, XID:EA6253E
4/21/2015 13:12:12:467,1:12:12 PM PDHCPd:REQUEST received, MAC:3C-97-0E-A6-25-3E, IP:10.40.55.63, XID:EA6253E
4/21/2015 13:12:12:529,1:12:12 PM Proxy boot filename empty?
4/21/2015 13:12:12:529,1:12:12 PM PDHCPd:DHCP_ACK sent, IP:10.40.55.63:68, xid:EA6253E
4/21/2015 13:12:12:529,1:12:12 PM DHCPd:4011 stopped...
4/21/2015 13:12:12:529,1:12:12 PM TFTPd:DoReadFile:ipxe-undionly.kpxe B:1456 T:0
4/21/2015 13:12:18:161,1:12:18 PM DHCPd:DISCOVER received, MAC:3C-97-0E-A6-25-3E, XID:C34F384A
4/21/2015 13:12:18:535,1:12:18 PM DHCPd:iPXE user-class detected
4/21/2015 13:12:18:535,1:12:18 PM DHCPd:OFFER sent, IP:0.0.0.0, XID:C34F384A
4/21/2015 13:12:18:551,1:12:18 PM DHCPd:REQUEST discarded, MAC:3C-97-0E-A6-25-3E, XID:C34F384A
4/21/2015 13:12:26:522,1:12:26 PM DHCPd:INFORM received, MAC:44-37-E6-56-10-04, XID:4B81F475
4/21/2015 13:12:30:781,1:12:30 PM DHCPd:INFORM received, MAC:28-D2-44-6E-79-96, XID:78885394
4/21/2015 13:12:41:342,1:12:41 PM DHCPd:INFORM received, MAC:3C-97-0E-19-35-6C, XID:6FEFBA37
4/21/2015 13:12:43:432,1:12:43 PM TFTPd stopped...
4/21/2015 13:12:43:432,1:12:43 PM HTTPd stopped...
4/21/2015 13:12:43:698,1:12:43 PM DHCPd:67 stopped...
4/21/2015 13:12:43:900,1:12:43 PM ROOT=C:\Users\ldadmin\Desktop\pxesrv\files\
4/21/2015 13:12:43:900,1:12:43 PM DHCPd:67 started...
4/21/2015 13:12:43:916,1:12:43 PM DHCPd:4011 started...
4/21/2015 13:12:43:916,1:12:43 PM TFPTd started...
4/21/2015 13:12:44:025,1:12:44 PM HTTPd started...
 
I can restart the server and everything works fine again for awhile. Here is how my config.ini looks:
 
[frmDHCPServer]
top=364
left=134
[dhcp]
root=C:\Users\ldadmin\Desktop\pxesrv\files\
filename=ipxe-undionly.kpxe
altfilename=wimboot.ipxe
optextra=175.6.1.1.1.8.1.1
httpd=1
proxydhcp=1
binl=0
dnsd=0
poolsize=252
opt1=255.255.255.0
bind=1
smb=0
opt3=0.0.0.0
opt6=0.0.0.0
opt43=0.0.0.0
opt51=86400
opt54=10.40.55.52
opt60=PXEClient
poolstart=10.40.55.2
log=1
start=1
 
I don't know how relevant it is, but our DHCP server is not on the same subnet. I appreciate any time that you spend looking at this, let me know if there is any other information that may prove useful.

 



#266 erwan.l

erwan.l

    Platinum Member

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

Posted 21 April 2015 - 05:42 PM

I am thinking of implement a watchdog feature as a (temp) workaround.

 

Is the below triggered by you or by the program itself?

4/21/2015 13:12:12:529,1:12:12 PM DHCPd:4011 stopped...

 

if triggered by the program, I might be able to restart it auto when this happen.

Regards,

Erwan
 



#267 mamiller

mamiller
  • Members
  • 3 posts
  •  
    United States

Posted 21 April 2015 - 06:20 PM

It seems to be triggered by the program. The last couple lines from the log that I posted were however triggered from me restarting the server so that it would start working again. Thanks for the quick response!



#268 erwan.l

erwan.l

    Platinum Member

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

Posted 22 April 2015 - 11:41 AM

It seems to be triggered by the program. The last couple lines from the log that I posted were however triggered from me restarting the server so that it would start working again. Thanks for the quick response!

 

I have done a slight modification in current version : download it again and give it a try.

I suspect you encounter a socketerror (like a connection reset by peer) which could be enough to stop the listening thread.

 

Last version will log socketerror (did not before) and will not stop the thread (did before).

 

EDIT:

a socket error should now be displayed like below (when it was not displayed before and would silently stopped the udp listener thread). 

12:55:43 goUDP4011:EIdSocketError,10040

If needed, the socket error codes can be found here.



#269 mamiller

mamiller
  • Members
  • 3 posts
  •  
    United States

Posted 23 April 2015 - 03:14 PM

So far so good, the server has been running for 18 hours now and is still working. I noticed there was a socket error last night when looking through the logs this morning, error 10054: Connection reset by peer. Everything still seems to be working great, I'll update this thread again if the issue persist. Thanks for your work on this!



#270 erwan.l

erwan.l

    Platinum Member

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

Posted 23 April 2015 - 04:18 PM

So far so good, the server has been running for 18 hours now and is still working. I noticed there was a socket error last night when looking through the logs this morning, error 10054: Connection reset by peer. Everything still seems to be working great, I'll update this thread again if the issue persist. Thanks for your work on this!

 

Thanks for this report!

I thought it was something like this : a non critical socket error was terminating the listener thread.

 

For the record, the listener thread is pretty simple (logic wise). See code below.

What I have added yesterday is an exception handler for socket errors which will not trigger a break.

Any other exception will trigger a break.

 

Sidenote, I see you are logging to a file.

If you use this in production/live environement, I advise you log to a syslog server (which will give you more features like logging to any media, trigger events, etc).

function goUDP4011(unused:dword):dword;stdcall;
var buf: TBuffer;
fromport,NumberBytes:integer;
fromip:string;
begin
log_memo_thread2('DHCPd:4011 started...');

while (udp4011.Active =true)  do
  begin
    try
    NumberBytes:=udp4011.ReceiveBuffer(buf,sizeof(buf),fromip,fromport,3000);
    if (NumberBytes>0) then frmDHCPServer.analysedata4011(buf,fromip,fromport);
    except
    on e:EIdSocketError do
      begin
	log_memo_thread2('goUDP4011:'+e.ClassName+','+inttostr(e.lasterror));
      end;
    on e:exception do
      begin
        log_memo_thread2('goUDP4011:'+e.ClassName+','+e.Message);
        break;
      end;
    end;
  end; //while ...

  try
  udp4011.Binding.CloseSocket();
  except
  on e:exception do ; //nothing 
  end;

  log_memo_thread2('DHCPd:4011 stopped...');
  exitthread(0);
  result:=0;
end;


#271 jurasjo.lol

jurasjo.lol
  • Members
  • 3 posts
  •  
    Poland

Posted 13 May 2015 - 09:47 AM

Is option "root=" for changing SMB share location?

nged.

I have changed it to c:\obraz and nothing has changed.


Edited by jurasjo.lol, 13 May 2015 - 09:48 AM.


#272 erwan.l

erwan.l

    Platinum Member

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

Posted 13 May 2015 - 09:59 AM

Is option "root=" for changing SMB share location?

nged.

I have changed it to c:\obraz and nothing has changed.

 

You should be able to use any location (smb or not, or even HTTP urls).

Note that you need to restart Tiny PXE thus for the change to be effective.

 

Let me know if this helps, if not I'll have a look later this evening.



#273 jurasjo.lol

jurasjo.lol
  • Members
  • 3 posts
  •  
    Poland

Posted 13 May 2015 - 10:40 AM

Ofcourse I have restarted it afrer maiking changes.

 

My config.ini is:

[dhcp]
top=29
left=22
root=files
filename=ipxe.pxe
altfilename=zschie.ipxe
optextra=175.6.1.1.1.8.1.1
opt3=0.0.0.0
httpd=1
start=0
tftpd=1
proxydhcp=1
bind=1
smb=1
root=C:\obraz
[frmDHCPServer]
top=240
left=548
[web]
port=80
 

and in the main window is

 

ROOT=C:\Users\student\Desktop\pxesrv\files\



#274 erwan.l

erwan.l

    Platinum Member

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

Posted 13 May 2015 - 11:58 AM

Ofcourse I have restarted it afrer maiking changes.

 

My config.ini is:

[dhcp]
top=29
left=22
root=files
filename=ipxe.pxe
altfilename=zschie.ipxe
optextra=175.6.1.1.1.8.1.1
opt3=0.0.0.0
httpd=1
start=0
tftpd=1
proxydhcp=1
bind=1
smb=1
root=C:\obraz
[frmDHCPServer]
top=240
left=548
[web]
port=80
 

and in the main window is

 

ROOT=C:\Users\student\Desktop\pxesrv\files\

 

you have indicated two times "root".

 

remove the (first) one with root=files.



#275 jurasjo.lol

jurasjo.lol
  • Members
  • 3 posts
  •  
    Poland

Posted 13 May 2015 - 03:31 PM

Ups. You are right. Now is working fine. THX :clap:







Also tagged with one or more of these keywords: pxe, network boot

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users