DHCP Rule 60 For PXE Booting

Toggle sidebar Toggle sidebar
M

matiasht

Distinguished
Oct 17, 2011
103
0
18,680
So I was just trying to deploy a WDS Server on my network using my Domain Controller. So in AD Server I have WDS, DHCP, and DNS installed.

At first when booting from one of the PC, I could get an IP but was not able to retrieve the image file from the server.

So googling a little bit I found out that the DNS Server was interfering with the ports that the WDS Service listens to, so I just changed the ports and was able too Boot succesfully. In order to achieve this I had to set up a rule 60 DHCP on the DHCP role on the server.

So now I'm up to this: I want to be able too boot from my LAN without having to depend on that DHCP role installed on the server, I want to use the DHCP role that I have on my router which is also the gateway.

So basically what Im trying to find out is how to add this famous DHCP 60 option/rule for PXE on my router which is model WR941ND v5 00000000 Firmware Version: 3.13.31 Build 130105 Rel.66489n brand TP-Link.

Do you guys have any ideas on how to set this up on this kind of routers?
 
Solution
B


Personally when I've done it, granted this was with SCCM, but WDS gets involved all the same, I've used options 66 and 67. I put in the IP address of the WDS/Distribution Point server for option 66, and for option 67 here's how mine looks for a 64-bit boot image:

smsboot\x64\wdsnbp.com

You probably will have to change your path, to reference the WDS folder that contains your wdsbp.com file. BTW - for option 66 you can use the hostname of your server but you're better off forgoing that in...
Sort by date Sort by votes
B

bill001g

Titan
Aug 9, 2012
28,363
2,766
125,640
Even when a router can do this it is simpler to use the server to do it. All these special DHCP options many time times have special formats. I know i have put other dhcp options in a commercial cisco router and had to key it in in hex which was a pain.

You are not going to be able to do that with factory firmware. I know dd-wrt has the ability to set some dhcp options, likely you can set any of them if you are willing to edit the underling unix files. I know it can pass the pxe boot server address but I thought PXE used the TFTP server ip which is option 66 I think but it has been a long time since I did this.
 
Upvote 0 Downvote
B

bill001g

Titan
Aug 9, 2012
28,363
2,766
125,640
Yup those are your options. Consumer routers are designed so the stupid people can have internet. These people are lucky if they can run their toaster and never read the instructions so manufactures do not include many feature that may hurt their little brains.
 
Upvote 0 Downvote
Ralston18

Ralston18

Titan
Moderator
Oct 11, 2014
35,019
3,351
146,290
Or, in further agreement with bill001g, provide the basis for a lawsuit against the manufacturer, the distributor, the ISP, the installer, and anyone who can be construed as culpable.

Plus I fear the day when some cheap router (or other IOT device) overheats, causes a fire, and the insurance company withholds payment because the router may have been hacked by some terrorist. Doesn't have to be true anymore - just possible..... [End of cynical sidebar.]

 
Upvote 0 Downvote
M

matiasht

Distinguished
Oct 17, 2011
103
0
18,680
Hahahaha ok I understand, that's fine I'll just use the DHCP role on Windows whenever I want to boot from LAN, in any case, what are these "DHCP Options" can you guys tell me in general what they are, and what is exactly this "Rule 60" ?
 
Upvote 0 Downvote
B

Bowmaster

Reputable
Sep 27, 2014
8
0
4,520


Personally when I've done it, granted this was with SCCM, but WDS gets involved all the same, I've used options 66 and 67. I put in the IP address of the WDS/Distribution Point server for option 66, and for option 67 here's how mine looks for a 64-bit boot image:

smsboot\x64\wdsnbp.com

You probably will have to change your path, to reference the WDS folder that contains your wdsbp.com file. BTW - for option 66 you can use the hostname of your server but you're better off forgoing that in favor of straight IP - less issue of DNS resolution problems that way.

Here's a couple of blogs (keep in mind they are SCCM-centric, but the same principles will apply because SCCM uses WDS for PXE):

http://myitforum.com/cs2/blogs/jmassardo/archive/2011/05/17/sccm-pxe-without-an-ip-helper.aspx
http://gerryhampsoncm.blogspot.com/2013/02/sccm-2012-sp1-step-by-step-guide-part_9487.html (Also discusses IP helper which is what Microsoft typically prefers)

Best of luck!
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom