I've recently put together a small office network (around 20 devices) with an attached machine running Windows Server 2012. Our gateway router provided by our ISP was pretty useless and started dropping connections once there were too many devices connected to it.
I managed to solve this issue by turning off the DHCP functionality on the router and off-loading it to the Windows Server machine. This worked for all of the windows devices on the network, but there seems to be a problem getting the windows DHCP to work with *nix devices.
On both android and OSX devices the machines cannot seem to obtain an address from the DHCP. On android devices the wi-fi seems to get stuck on "Obtaining IP address" while the OSX devices seem to give up after a while and self-assign an IP address that is far outside the local address range.
I was just wondering if anyone has come across an issue like this before?
I've done a bit of research on this and it seems that *nix devices want a response from DHCP Option 119 (See: http://blogs.blackmarble.co.uk/blogs/rhepworth/post/2012/06/18/Adding-DHCP-Option-119-(Domain-Search-List)-to-Windows-Server-2008-R2.aspx )
However I went through the steps in this blog and still had no luck.
As a stopgap I have reserved IP addresses on the DHCP and manually set the adapter settings for each OSX and Android device currently on our network, but I would rather not have to do this for every new *nix machine that wants to connect.
Any help would be appreciated...