DHCP Server Options

[Dogers]

After going mad trying to make a Novell server do this, i caved in and decided it would be easier to make a 2003 server do it.. and i was half right!

Im trying to make a DHCP server provide details for a couple of BOOTP clients we have. The Novell server is still issuing ips fine, as its set to only do DHCP, the 2003 server only BOOTP. I've configured options 66 and 67 (Boot Server Host Name and Bootfile Name) to point to the correct server and file, however the bootp clients are still failing. I've been snooping the traffic between server and client, and it seems that the server isnt sending option 66 over to the client, its passing a blank address over! The bootfile is coming over fine, however. The server is also offering a valid address (in the scope) with all the other options detailed - its just this one option i really need!

Has anyone else come across this? I've followed the instructions of a website to the letter, so I think theres something wrong with this option/2003's dhcp server?! I dont have a 2000 server to test this on, unfortunately..

 

[BWilson77080]

there is an option on the server properties in teh dhcp console (i think it was the server properties), simple selection...dhcp only, bootP only, or Both

 

[Dogers]

yeah i've set that, its answering the clients request, but its not passing the server ip of where the client gets its bootfile.. its passing what the bootfiles called, which makes me think theres something wrong with 2003's dhcp server!

 

[BWilson77080]

well you lucked out i jsut happened to have upgraded my test server to win2003...ill have to check the settings out in there and see if i can help you out....cant od it right now though

does it resolve the IP when you click resolve in the options?

BWilson77080
MCSE, MCSA, A+

 

[Dogers]

cool

wheres this resolve, i cant see it?

 

[BWilson77080]

doesnt give the option i was thinkin wrong...

you have WINS installed on this new server....seein as BootP uses broadcasts....and you're using win2003....makes sense youd need win2003 WINS

you probabaly already have it though huh

just never mntioned...

 

[Dogers]

we have a wins server, but im not passing that over..

all the bootp client needs is a dns server, a tftp server (boot server name, option 66) and bootfile name (option 67) - it should then connect to the tftp server, grab the file and procede to boot properly, but the dhcp servers not sending the server name at all

 

[BWilson77080]

gotcha......

i was just looking over an article at this link:

http://www.microsoft.com/technet/tr...r2003/proddocs/deployguide/dnsbc_dhc_jaeu.asp

heres an excerpt......
BOOTP clients download the image file from a TFTP server. Because Windows Server 2003 does not provide a full TFTP file service, you might need to use a third-party TFTP server to support BOOTP clients that must start from an image file (usually diskless workstations).

 

[Dogers]

yep, ive got a third party tftp server running, the clients just plain arent getting the ip address of that server to connect to