Darylrese Posted October 14, 2013 Posted October 14, 2013 (edited) Hi Guys, Just started in a new school and at the moment WDS only works from the ports in the ICT office and the technician has to bring the PC down and build them in the office!!! I had a look in DCHP and can't see the scope options for WDS configured on any VLAN's including the one that the ICT office sit on. The error i get when trying to network boot is no DHCP offering or Proxy DHCP. Any ideas? I want WDS to work on all VLAN's, theres no way im bringing every pc down into the office! I can ping the WDS server from the PC's Edited October 14, 2013 by Darylrese
ADMaster Posted October 14, 2013 Posted October 14, 2013 Hello, Try enabling option 60 PXEClient on one of the DHCP scopes.
TronXP Posted October 14, 2013 Posted October 14, 2013 We put in a dhcp helper on each vlan pointing to the wds server. That worked for us.
Darylrese Posted October 14, 2013 Author Posted October 14, 2013 We put in a dhcp helper on each vlan pointing to the wds server. That worked for us. Any ideas how to do that on an HP Switch?
glennda Posted October 14, 2013 Posted October 14, 2013 Any ideas how to do that on an HP Switch? What Model? Some of the newer ones run Comware not the HP software so might be different.
Darylrese Posted October 14, 2013 Author Posted October 14, 2013 No worries. Would this be it? Example to configure the "ip helper-address" on vlan 10: ProCurve# configure ProCurve(config)# vlan 10 ip helper-address 1.1.1.1 Trying on the core at the moment which is a HP 8212 zl Switch
CyberNerd Posted October 14, 2013 Posted October 14, 2013 comware is dhcp relay server-group 1 ip XXX.XXX.XXX.XXX
Darylrese Posted October 14, 2013 Author Posted October 14, 2013 my code above added an iphelper address but just tried a machine and still no DHCP offering
glennda Posted October 14, 2013 Posted October 14, 2013 No worries. Would this be it? Example to configure the "ip helper-address" on vlan 10: ProCurve# configure ProCurve(config)# vlan 10 ip helper-address 1.1.1.1 Trying on the core at the moment which is a HP 8212 zl Switch You need to enter the IP routing section I think off the top of my head - HP ProCurve Switch 5304XL>enable HP ProCurve Switch 5304XL# config term HP ProCurve Switch 5304XL(config)# ip routing HP ProCurve Switch 5304XL(config)# vlan XX HP ProCurve Switch 5304XL(vlan-xx)# ip helper-address xx.xx.xx.xx HP ProCurve Switch 5304XL(vlan-xx)# write mem
cpjitservices Posted October 14, 2013 Posted October 14, 2013 Juniper here too We put in a dhcp helper on each vlan pointing to the wds server. That worked for us.
Darylrese Posted October 14, 2013 Author Posted October 14, 2013 (edited) You need to enter the IP routing section I think off the top of my head - Thanks! It says record already exists so it must have saved when i did it from the code above. Just to confirm i have Option 60 = PXECLIENT Option 66 = WDS IP Address Option 67=boot\x86\wdsnbp.com Ip Helper Address on VLAN = WDS Server IP Is this correct? Edited October 14, 2013 by Darylrese
IrritableTech Posted October 14, 2013 Posted October 14, 2013 (edited) To get it deploying across the all the vlans you'll need the iphelper configured, routing correctly working over your core switch (which we assume it is) and the correct options set in each DHCP scope. I think for WDS it's Option 66: IP of WDS Server Option 67: boot\x86\wdsnbp.com but I don't use WDS - we still use fog. You may also need to forward the udp protocol to your vlans broadcast address for the tftp server to work correctly. Off the top of my head... ip routing vlan 11 name "Client VLAN" untagged A1-24 ip address 10.0.11.254 255.255.255.0 ip helper-address 10.0.100.1 vlan 100 name "Servers VLAN" untagged B1-24 ip address 10.0.100.254 255.255.255.0 ip forward-protocol udp 10.0.11.255 tftp exit write mem Edited October 14, 2013 by IrritableTech
ADMaster Posted October 14, 2013 Posted October 14, 2013 I don’t have option 66 or 67 set in my DHCP and it works fine. Also is your WDS running on the same machine as DHCP. There is a tick box that needs ticking if you are.
Darylrese Posted October 14, 2013 Author Posted October 14, 2013 The vlan im trying it on is vlan 10 ip helper addresses are: 192.168.0.10 192.168.0.217 (wds server)
Darylrese Posted October 14, 2013 Author Posted October 14, 2013 I don’t have option 66 or 67 set in my DHCP and it works fine. Also is your WDS running on the same machine as DHCP. There is a tick box that needs ticking if you are. Nope, its a dedicated WDS Server.
ADMaster Posted October 14, 2013 Posted October 14, 2013 Here is a bit of info for you, but I think you have covered all these options. Configuring DHCP and WDS | Networking content from Windows IT Pro
Darylrese Posted October 14, 2013 Author Posted October 14, 2013 I have indeed but thanks for the link
Darylrese Posted October 14, 2013 Author Posted October 14, 2013 It gets stranger....theres only 1 port in our office that works with WDS and i have checked the tagging on the port and its exactly the same as the other ports in our office which dont work. Am i right in thinking something must have been configured on just that port that does work on the switch?
themightymrp Posted October 14, 2013 Posted October 14, 2013 Maybe some kind of port security? MAC filtering or some such? Would be a very odd setup if it was though. Literally, all you should need is the ip helper-address bit in your core switch and options 66 and 67 configure in your DHCP server (I set them in server options rather than scope options, that way they get passed down into each vlan scope of addresses). Option 66 is the IP of DHCP server, option 67 is boot\x86\wdsnbp.com What are you getting on screen when you try to network boot from other ports in your office?
Darylrese Posted October 14, 2013 Author Posted October 14, 2013 (edited) I dont think it can be MAC auth as it will literally work on any device connected to that 1 port in the office. I just tried setting the DHCP settings and will check again in the morning. The other ports in the office give the same error, no DHCP or ProxyDHCP offering Edited October 14, 2013 by Darylrese
Darylrese Posted October 14, 2013 Author Posted October 14, 2013 Maybe some kind of port security? MAC filtering or some such? Would be a very odd setup if it was though. Literally, all you should need is the ip helper-address bit in your core switch and options 66 and 67 configure in your DHCP server (I set them in server options rather than scope options, that way they get passed down into each vlan scope of addresses). Option 66 is the IP of DHCP server, option 67 is boot\x86\wdsnbp.com What are you getting on screen when you try to network boot from other ports in your office? The DHCP server? I thought 66 was supposed to be the IP of the WDS Server?
IrritableTech Posted October 15, 2013 Posted October 15, 2013 Yep it's the IP of the WDS server - probably a typo. Could you post the config of the switch with the port that works over WDS? Mask IP addresses and Names if you don't want us to see them.
Darylrese Posted October 15, 2013 Author Posted October 15, 2013 No problem. I have set the options on the server options and its still saying the same error. When it does work this is the screen: I will screenshot a machine that does not and will report back
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now