Reputation
1,067
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
4 10
Newest
 Nice Answer
Impact
~26k people reached

  • 0 posts edited
  • 0 helpful flags
  • 23 votes cast
Apr
18
answered What do I need to send an Extended DHCPOFFER with multiple boot options?
Apr
14
comment TFTP (for PXE purposes) Server running Debian, problems with Samba
In order to minimize the guesswork I'd run wireshark on let say the Windows client while trying to map the share and try to see on the traffic capture why the map "really" fails. This way you can confirm if this is a problem of SMB protocol version, a permission issue, or whatever.
Apr
13
revised TFTP (for PXE purposes) Server running Debian, problems with Samba
deleted 1 character in body
Apr
13
revised TFTP (for PXE purposes) Server running Debian, problems with Samba
added 136 characters in body
Apr
13
answered TFTP (for PXE purposes) Server running Debian, problems with Samba
Apr
12
answered Custom Live Boot PXE ISO Script
Mar
27
comment PXE or other : deploy images on single board computers (SBC)
Some SBC include minimally the ability to boot from USB when present (code included in the mask). If not your safest bid is Jtag; and it is not a complicated option. It is the industry standard.
Mar
26
answered PXE or other : deploy images on single board computers (SBC)
Mar
16
comment WDS 2012 R2 Server
the firewall has to be open to DHCP but also to TFTP ! it is TFTP the one that uses that random port. If the firewall only partially blocks the segment of possible TFTP ports then you can randomly get TFTP transfers that go OK and others that fail.
Mar
16
comment WDS 2012 R2 Server
See the edit at the answer
Mar
16
revised WDS 2012 R2 Server
added 328 characters in body
Mar
16
answered WDS 2012 R2 Server
Mar
2
answered Downloading with U-Boot's tftp randomly times out
Feb
4
comment WDS PXE Server occasionally returning bad IP
OK that MASK explains this point.
Feb
3
comment WDS PXE Server occasionally returning bad IP
But do you have a router between the client and the DHCP server yes or no? if the DHCP interface is 192.168.0.5 and the client is assigned 192.168.4.64 then there must be a router joining both networks and that router must have enabled the DHCP relay services. Are you doing that???
Feb
2
comment WDS PXE Server occasionally returning bad IP
1) why a 192.168.0.5 DHCP server assigns an 192.168.4.64 address?; is there a router between the DHCP Server and the Client? 2) 192.168.0.5 DHCP server is not providing PXE parameters. 3) I agree with you the erratic side of your problem makes me think of a bug on the "Choose a boot server" code
Jan
30
comment WDS PXE Server occasionally returning bad IP
There's also something weird all the WDS servers offer IPs belonging to 192.168.0.x but the WDS at 192.168.0.5 offers 192.168.4.x and in the considered run the IP accepted is 192.168.4.64...check that out.
Jan
30
comment WDS PXE Server occasionally returning bad IP
1) you have to check the versions of the first instance NBP ( wdsnbp and wdsmgfw.efi) those are the ones that display the menu and probably do not behave correctly 2) if you see the packet# 2800 of your capture you will find a DHCK ACK that does not offer a NBP while all the other ACKs include one. then you have a WDS server not correctly configured; its IP = 192.168.0.5
Jan
30
revised WDS PXE Server occasionally returning bad IP
edited body
Jan
30
revised WDS PXE Server occasionally returning bad IP
added 90 characters in body