Menu
' If a DHCP server is running on the Windows Deployment Services server, Windows Deployment Services must be configured to not listen on port 67 and DHCP Option Tag 60 must be added to all DHCP scopes on your DHCP server. Non-Microsoft DHCP servers require manual configuration of DHCP optioin tag 60.
With appropriate UDP helpers in place, I have not had to add 066 or 067 to the DHCP scopes. Here's what WDS has to say: ' If a DHCP server is running on the Windows Deployment Services server, Windows Deployment Services must be configured to not listen on port 67 and DHCP Option Tag 60 must be added to all DHCP scopes on your DHCP server. Non-Microsoft DHCP servers require manual configuration of DHCP optioin tag 60.
![Tftpd32 Dhcp Option 150 Configuration Tftpd32 Dhcp Option 150 Configuration](/uploads/1/2/5/6/125663556/348823674.png)
If Microsoft DHCP is running on this server click the check boxes to set the following options, if non-Microsoft DHCP is running on this server check the first box and manually configure DHCP option 60. Do not listen on port 67 Configure DHCP option 60 to PXE Client' Also, please ensure that the required UDP ports are open on the firewall on the WDS server. If you are still having issues, you may want to fire up NetMon on the WDS server to see if it is recieving the duplicate DHCP requests. That will surely tell you if your IP helpers are working. Kevin Wehnau wrote: Yes.
I installed WDS then did nothing to it. Installed the PXE service role and then distributed the x86 image to the DP. Did I need to do both? I'm just not sure about my DHCP settings. My DHCP server is on a seperate server, do I need to manually setup the scope options? Otherwise, how are my clients going to know to go to the SCCM server? You will need to distribute both the x86 and x64 boot images to the DP.
You will need to talk to your network folks to ask them to configure the UDP helpers on the appropriate subnets/vlans to point to the IP address of your PXE service point. Otherwise, it's possilbe that the DHCP requests will not make it from the clients to the PSP.
You should be able to verify PSP functionality using a machine on the same IP subnet as the PXE service point, unless there are network configuraitons that are explicity blocking the traffic. Hope this helps! With appropriate UDP helpers in place, I have not had to add 066 or 067 to the DHCP scopes. Here's what WDS has to say: ' If a DHCP server is running on the Windows Deployment Services server, Windows Deployment Services must be configured to not listen on port 67 and DHCP Option Tag 60 must be added to all DHCP scopes on your DHCP server.
Non-Microsoft DHCP servers require manual configuration of DHCP optioin tag 60. If Microsoft DHCP is running on this server click the check boxes to set the following options, if non-Microsoft DHCP is running on this server check the first box and manually configure DHCP option 60.
Do not listen on port 67 Configure DHCP option 60 to PXE Client' Also, please ensure that the required UDP ports are open on the firewall on the WDS server. If you are still having issues, you may want to fire up NetMon on the WDS server to see if it is recieving the duplicate DHCP requests. That will surely tell you if your IP helpers are working. I swear I must be an idiot. I am still having no luck at all. I am getting a tftp file not found error.
I checked with netmon, and the DHCP request is coming though, as well as the request to the tftp server. Did I miss something in SCCM? Do I need to do anything else to enable it? Is there a good how-to or step-by-step out there?
![Tftpd32 Tftpd32](http://www.winplat.net/images/archive/image_thumb_69.png)
I see plenty about click this if your DHCP server is on the same box, but nothing about it being seperate, should it just work? I defintely don't need to set anything in DHCP? No 066,067,060, or 150? I have firewalls off on both servers, and it's wide open in between. And I have an IP helper for my DHCP server as well as one for the address of the SCCM server with the PXE service role installed.
I'm sorry to beat a dead horse here, but I'm feeling pretty lost, and none of the docs I find seem to do anything to enlighten me. Here is what my smspxe.log has when it tries to boot.
010.010.014.029:67 Recv From:010.010.024.001:67 Len:548 79571c smspxe 12/4/2007 3:12:42 PM 1864 (0x0748) Executing LookupDevice(013A9E88-8C45-CB11-9B1D-AEFE281DF6F9, 00:0D:60:2C:2F:7B) smspxe 12/4/2007 3:12:42 PM 2424 (0x0978) CDatabaseProxy:: LookupDevice succeeded: 0 0 38 1 smspxe 12/4/2007 3:12:42 PM 2424 (0x0978) MAC=00:0D:60:2C:2F:7B SMBIOS GUID=013A9E88-8C45-CB11-9B1D-AEFE281DF6F9 Device found in the database. MacCount=1 GuidCount=0 smspxe 12/4/2007 3:12:42 PM 2424 (0x0978) 010.010.014.029:67 Recv From:010.010.024.001:67 Len:548 79676c smspxe 12/4/2007 3:12:44 PM 1864 (0x0748) Ignoring req from 010.010.024.001:67 Dest Server:010.010.014.008 smspxe 12/4/2007 3:12:44 PM 1864 (0x0748) 010.010.014.029:4011 Recv From:010.010.028.005:68 Len:548 23fc2c4 smspxe 12.
When I boot a machine on the same subnet after putting up a scope on that subnet, this is what my smspxe log shows. 010.010.014.029:67 Recv From:000.000.000.000:68 Len:548 7a8d0c smspxe 12/4/2007 9:12:57 PM 1864 (0x0748) Executing LookupDevice(84724231-D221-4EF8-A6CD-9678C625C627, 00:03:FF:88:6E:93) smspxe 12/4/2007 9:12:57 PM 2424 (0x0978) CDatabaseProxy:: LookupDevice succeeded: 33 1 33 1 smspxe 12/4/2007 9:12:57 PM 2424 (0x0978) MAC=00:03:FF:88:6E:93 SMBIOS GUID=84724231-D221-4EF8-A6CD-9678C625C627 Device found in the database. If the machine already has the SCCM client it doesn’t need to PXE boot. If you are PXE booting to an SCCM PXE Service Point you need to set option 66 to tell unknown computers where your PXE Service Point is. O DHCP helpers (relay agents) would pass along DHCP traffic but wouldn’t apply to the options DHCP sends. You do not need to specify a file name (Option 67) When troubleshooting: o Make sure your task sequence has “use boot image” on the Advanced properties page. O Make sure your advertisement says “make this task sequence available to boot media”.
O Make sure your workstation is set to boot to the network. O Make sure you remember to press f12 on the workstation when it asks.
TFTPD32 is a fantastic utility- TFTP server and DHCP all in one- this makes it a great recovery/upgrade tool for most models of Cisco Phone with one caveat- DHCP Option 150. When a Cisco phone pulls DHCP it looks to Option 150 for an IP address of a TFTP server to start the boot/upgrade process. TFTPD32's Option field is an ACSII one, and putting an IP address in here is useless and will only confuse the phone as it it will be passed as a string instead of a usable address. Workaround: put the IP address for option 150 into the ascii field as a reverse HEX address like 0xfd01a8c0 192.168.1.253 Works like a charm! Maybe Philippe will one day put some kind of a toggle in (hint, hint) so we can enter IP addresses directly- but until then, use the simple workaround!
Thanks for a great utility Philippe!