linkazoid Posted January 8, 2016 Posted January 8, 2016 Hi, We've had issues recently which have required us to move our DHCP service from our WDS Server. This has stopped PXE booting and I can't seem to fix it. PXE Error is PXE-E55: ProxyDHCP service did not reply to request on port 4011 WDS and DHCP services were previously on Server named DHCP - 10.239.32.9 DHCP service has been installed on Server named PRINT and authorised - 10.239.32.10 - This is working correctly for clients. DHCP Service has been unauthorised and role removed from DHCP Server. WDS role is still on DHCP server. Option 60 has been removed from the DHCP. Reading online and I can't seem to if/what other options need to be required in this scenario where DHCP and WDS are on different servers. Thanks, Michael
Steve21 Posted January 8, 2016 Posted January 8, 2016 Did you add your 066 option in DHCP to tell it where the WDS server is? Steve 1
BKGarry Posted January 8, 2016 Posted January 8, 2016 We had this, Had to set option 066 in scope options to your WDS server 10.239.32.10 and then set option 067 to something like boot\x64\wdsnbp.com This made the WDS server worked. I found if I didn't put in option 67 as well it would not work.
Davit2005 Posted January 8, 2016 Posted January 8, 2016 Is your WDS server on a different subnet from your workstations??
BKGarry Posted January 8, 2016 Posted January 8, 2016 yes it is, so I had to set the scope options in each client DCHP scope
linkazoid Posted January 8, 2016 Author Posted January 8, 2016 I get the same error whether Option 66 is set or not.
Steve21 Posted January 8, 2016 Posted January 8, 2016 What about the DHCP options within WDS? Do you have the boxes ticked not to listen on DHCP port etc? Steve
linkazoid Posted January 8, 2016 Author Posted January 8, 2016 What about the DHCP options within WDS? Do you have the boxes ticked not to listen on DHCP port etc? Steve In WDS both options are unticked.
Steve21 Posted January 8, 2016 Posted January 8, 2016 I get the same error whether Option 66 is set or not. 66 and 67? Steve
Steve21 Posted January 8, 2016 Posted January 8, 2016 Oh silly question, but when you deleted 060 did you delete the setting or the whole config? Sometimes it seems to work better when you delete the setting, but not the field e.g. 060 leave blank. Almost like it won't overwrite the old setting otherwise Steve
linkazoid Posted January 8, 2016 Author Posted January 8, 2016 I've removed the option 60 and I've also tried just blanking it out. All have the same outcome. 66 and 67 are set.
Joanne Posted January 8, 2016 Posted January 8, 2016 Do you restart the service each time you make these changes?
linkazoid Posted January 8, 2016 Author Posted January 8, 2016 Yep, Services have been restarted after each change.
Davit2005 Posted January 8, 2016 Posted January 8, 2016 If your workstations are on different Subnet you will need to add the WDS server as a helper address.
linkazoid Posted January 11, 2016 Author Posted January 11, 2016 The workstations are on a different subnet to the new DHCP and original WDS Server. Adding the IP helper address hasn't helped. It still displayed the same message - PXE-E55: ProxyDHCP service did not reply to request on port 4011 The client gets an IP address but doesn't connect to WDS.
BKGarry Posted January 11, 2016 Posted January 11, 2016 just to check, the windows firewall hasn't randomly opened on the server causing it to block port 4011 right?
Steve21 Posted January 11, 2016 Posted January 11, 2016 Take it all your switches/firewalls etc aren't set to block any ports between the VLANs if it has been moved across? Does it work if you put them on the same VLAN temporarily? Steve
linkazoid Posted January 11, 2016 Author Posted January 11, 2016 I have checked the firewall and it is disabled. I have also configured the port to be on the same subnet as the servers and the same message is displayed.
Steve21 Posted January 11, 2016 Posted January 11, 2016 You got any screenshots etc of all these settings? As I thought it started off with them on same VLAN/Subnet etc, WDS and DHCP services were previously on Server named DHCP - 10.239.32.9 DHCP service has been installed on Server named PRINT and authorised - 10.239.32.10 So if it was on a different VLAN etc not really quite sure how you've got this setup now :s Steve
linkazoid Posted January 11, 2016 Author Posted January 11, 2016 The servers are on the same VLAN and have always be from the beginning. I assumed that you asked me to get the workstation on the same subnet to check.
Steve21 Posted January 11, 2016 Posted January 11, 2016 The servers are on the same VLAN and have always be from the beginning. I assumed that you asked me to get the workstation on the same subnet to check. So WDS server hasn't been changed at all apart from DHCP being removed? Client is deffo getting DHCP from the new server (don't have a secondary one installed etc?) Should show the IP it's getting on the DHCP page. WDS set to respond to all clients (not just known ones?) Steve
linkazoid Posted January 11, 2016 Author Posted January 11, 2016 Hi Steve, That is correct. DHCP server is still online but only has WDS role. Clients are getting an IP from new DHCP and this is shown on PXE boot screen. WDS is set to allow all clients to connect.
linkazoid Posted January 15, 2016 Author Posted January 15, 2016 I've had to abandon this. I created a new VM called DHCP and migrated all the services back so that DHCP and WDS are on the same server. PXE booting is now working again.
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