Hello Guys,

i have a strange Problem. First of all we wanted to implement a two scope solution. So one Scope is for our clients who are joined our domain and the second scope is a guest Network for the rest. I created two scopes with two different subnets and created a mac adress policy on our "Domain" Scope and added the mac adresses from all our domain joined clients. Now i get some strange phenomenon. Sometimes our domain joined clients get an adress from the guest scope. I get an event viewer 1342 ID, which says the scope is out of addresses, but this is wrong. The scope isn't full. Only 5 clients have requested an ip and the scope is only 3% full. In the DHCP Log are also only the 5 clients who requested an address. Problem is now that the server thinks for a strange reason the scope is full and so the clients get an adress from our guest scope. I have the same problem on our second location. Another strange thing is that two clients get an Ip from the guest network and only after a /release and /renew they get an ip from the right scope. I tried creating an superscope and also two Nics with the different subnets, but no luck. What would be best practice to implement such a solution? Is this the wrong way?

Thanks

Hi

 You should configure Scope-level link layer filering on scopes for mac policy,

Check the article detailed information for scope layer filtering;

http://blogs.technet.com/b/teamdhcp/archive/2012/09/15/scope-level-link-layer-filtering-using-dhcp-policies-in-windows-server-2012.aspx

Hi Tonire,

Since you are using two scopes for different subnets, I suppose you are using DHCP relay agent. When address requests are sent to DHCP server, the server would choose a corresponding scope according to the IP address of the DHCP relay agent.

For the clients who got wrong IP addresses, we need to ensure their MAC addreses are allowed on the scope. 

For further analysis, we could use Network Monitor. We could analyze the packets to find out the problem.

Here is the guide for Network Monitor:
Network Monitor:
https://technet.microsoft.com/en-us/library/cc938655.aspx

Best Regards,

Leo