DHCP stopped working for wired clients (possibly due to new Windows 8 machine on network?)
My home office network has always been rock solid but has suddenly stopped allocating DHCP addresses to wired clients (wireless still works). The only thing that has changed has been the introduction of 2 Windows 8.1 laptops for my children over Christmas, and I wonder if these are the cause?
My network set-up is as follows...
I have a fibre broadband connection into the home office which plugs into my Airport Extremes WAN port. I then have a single ethernet cable going from one of the LAN ports on the AE to a gigabit ethernet hub, into which I have 10+ machines. The AE is set to use PPPoE to get the net connection and the network setting is to use DHCP to sign addresses. The IP addresses are assigned to the wired clients, plus a couple of airport expresses, and a number of iPhones, iPads etc. This has all worked fine for a couple of years, and any device just gets an address and works.
At Christmas both my children got Windows 8 laptops (don't ask!). I connected them to the wifi network (served by the Airport Extreme) and they got assigned an IP address correctly. They can browse fine, and also auto-updated to 8.1 at the same time.
I wasn't working in the home office at that time but did notice a few things not connecting and when I did check, none of the wired devices was receiving an IP address. They all come up as self-assigned. Nothing has changed on the network itself, the cables are still plugged in (the machines haven't moved!). I think somewhere on the network a second DHCP server is running, but I cannot see where. The only new thing are the Windows 8 laptops. Could they be the problem?