I've just installed FOG on Ubuntu to try it out. It sounds cool! I didnt enable FOGs DHCP service as we're already running Win 2003 DHCP. I followed the FOG documentation for Win DHCP and did the following...
Highlight the Scope Options for the subnet Scroll down the list of options to 066 "Boot Server Host Name". Check the box next to option 066. Enter your tftp server's ip address check option 067 "Bootfile Name" and enter the name of the bootimage "pxelinux.0"
However when I boot any client via network boot the client spends ages on the DHCP section, gets an IP address then I get the message PXE-E55: ProxyDHCP: No reply to request on port 4011.
I tried removing the 066 and 067 entries and booting a client via LAN, the same error message.
We only have 1 subnet, on VLAN1, a couple of HP Procurve 1800gs (on the servers and core switch) and the rest HP Procurve 1400s. Around 100 clients. I've tried a client on the same switch as the servers. Nothing.
Any ideas? I tried googling but most responses are WDS / Ghost / etc specific.
Intresting, if your getting the error when the options arent set it implies that the problem isnt with FOG.
Is there any firewalls on your network? on the DHCP server thats blocking that port?
Windows firewall is disabled. No hardware firewalls internally.
Port 4011 is for proxyDHCP right? Does this need to be setup on the DHCP server also?
The Proxy DHCP service may also be run on the same host as the standard DHCP service. Since both services cannot share port 67/UDP, the Proxy DHCP runs on port 4011/UDP and expects the extended DHCPDISCOVER packets from PXE Clients to be DHCPREQUESTs. The standard DHCP service has to send a special combination of PXE options in its DHCPOFFER, so the PXE client knows to look for a Proxy DHCP on the same host, port 4011/UDP
what other options do you have confgiured on the server. My server here only has options 3,6,15,44,46,66,67 configured.
My server has 3,6,15,44,46 and I've tried it with and without 66 / 67. Same error.
how about server options instead of scope options? whats set in there?
Nothing is set in server options only scope options. I'll give 66 / 67 a go in there...
No. Same error when 66 and 67 are set in both server options and scope options.
because it happens when the options arent set its not a problem with the FOG Machine, if it was it would come with an error about not being able to find the FOG Machine.
How long does it take to get an IP? my clients tend to pick up an IP almost instantly, is the IP it picks up on your range?
I THINK its WDS interfering as it uses pxe booting aswell, i had the same issue here and turned it off and heypresto fog worked fine...
On the client I select PXE boot from the boot selection menu,
enters PXE boot screen,
Client MAC.... (MAC Address) GUID... (GUID)
DHCP.... (about 1min 30sec here)
Client IP... 192.168.43.91 Mask 255.255.255.0 DHCP IP 192.168.43.253 (Correct from our scope)
PXE-E55 ProxyDHCP: No reply to request on port 4011
PXE-MOF: Exiting Bootmanage PXE ROM
I've never installed or have any experience of WDS. I can't see a service / server role / Administrative Tool for it. Could it be hiding elsewhere or can I assume that's not the problem?
I've also tried querying the ports of both the DHCP and FOG server.
Neither DHCP Server or FOG is listening on 4011 UDP
FOG is listening on 69, DHCP Server is not
DHCP Server is listening on 67 & 68, FOG is not.
Any one any clues why it's not working??
I'm testing FOG as we are looking to get rid of ghost but I'm getting the same PXE-E55 problem when trying to get a host to connect. Has anyone managed to resolve this problem?
Sadly Fatmas I never solved this one. Ran out of time in the end.
We just use Clonezilla on a USB drive pulling images from a fileserver at the minute. I'm sure, by far, not as efficient as Fog but it still saves hours / days on manual installs!
If you find a solution be sure to let us know!
I was also experiencing this issue, as FOG instructed I had 066,067 set correctly, and 060 was unticked in the Scope Options.
However, PXE only works when I delete 060 from the Server Options too.