ARP Timeout

[mrforgetful]

Ok so after adding a new DHCP server, clients that get served by that server can no longer PXE boot, I get an ARP Timeout error.

 

The DHCP settings are identical on both Windows Servers, do I need to configure something on the switches? Or something else I've missed?

[Geoff]

Is the new server configured to allow BOOTP clients?

[mrforgetful]

Nope, both set to DHCP only.

[Guest frankybaloney]

Are you using thin clients?

[mrforgetful]

Nope.

 

Do I need Routing and Remote Access enabled on the new DHCP server?

 

Clients are working ok, it's just the PXE error I seem to be getting.

[Kyle]

Have you tried manually deleting all your leases and then let the machines log back ina recreate their lease?

[mrforgetful]

I've tried it with one of them, it's getting an address from the new server fine, it's just the PXE error.

 

Looking around on the web the possible causes and fixes don't seem to apply:

 

# PXE-E11: ARP timeout.

 

* The PXE ROM will retry the ARP request four times, if it does not get any valid ARP replies, this message is displayed. This error can be caused by a number of network and service configuration errors. The most common are: Setting the DHCP Class Identifier (option 60) on the DHCP server and installing the proxyDHCP on a separate machine.

* Using routers that do not respond to ARP requests.

 

Nothing has changed to do with Routers, the points/hardware that I'm using are the same as when it worked.

I do not even have the choice to set Option 60 in the DHCP settings nevermidn have it set to anything.