Which is the actual start file? (Option 67, MS DHCP)

Support
1

Heyho

i've an issue right now: i've a client which should load the discovery
plugins kernel and it just waits for a respond from the tftp server.
We're using a Windows Server 2008 R2 and we've configured a certain vlan to
give out the pxe boot options.

When i sniff the servers incoming port 69 Traffic it seems that the DHCP
server is actually almost working because the client sends requests to the
tftp server with the RRQ Value which is the same as the ms dhcp config
option 67, but i don't know which file is actually needed now so that the
client can load it. (Yes i am really new to all this)

Thanks in advice.

2

> Heyho
>
> i've an issue right now: i've a client which should load the discovery
> plugins kernel and it just waits for a respond from the tftp server.
> We're using a Windows Server 2008 R2 and we've configured a certain vlan
> to give out the pxe boot options.
>
> When i sniff the servers incoming port 69 Traffic it seems that the DHCP
> server is actually almost working because the client sends requests to the
> tftp server with the RRQ Value which is the same as the ms dhcp config
> option 67, but i don't know which file is actually needed now so that the
> client can load it. (Yes i am really new to all this)
>
>
it should be pxelinux.0

Ohad

··· On Wed, Apr 20, 2016 at 2:39 PM, Tim Kopplow wrote:

Thanks in advice.

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

3

Alright so, if i have put that to the dhcp option (which i already did) and
i see that the dhcp server is actually telling the booting client that
option which then trys to contact the tftp server but nothing else
happens… where do i start to debug that?

I mean i've sniffed the servers traffic on port 67, shouldn't there be more
than only the client telling the server this "option 67" information?

··· On Wednesday, April 20, 2016 at 2:05:59 PM UTC+2, ohad wrote: > > > > On Wed, Apr 20, 2016 at 2:39 PM, Tim Kopplow > wrote: > >> Heyho >> >> i've an issue right now: i've a client which should load the discovery >> plugins kernel and it just waits for a respond from the tftp server. >> We're using a Windows Server 2008 R2 and we've configured a certain vlan >> to give out the pxe boot options. >> >> When i sniff the servers incoming port 69 Traffic it seems that the DHCP >> server is actually almost working because the client sends requests to the >> tftp server with the RRQ Value which is the same as the ms dhcp config >> option 67, but i don't know which file is actually needed now so that the >> client can load it. (Yes i am really new to all this) >> >> > it should be pxelinux.0 > > Ohad > >> Thanks in advice. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > >