Unfortunately for us, this is working as designed, designed like #&!%.
Superscopes override individual scopes. You will need to create individual scopes for each VLAN subnet. I had the same problem. I wanted to use superscopes to try and make management easier but it creates the problem that you described. Once I created individual scopes for each VLAN subnet, my problems went away.
Take a look at the following MS KB articles
169290 – DHCP reservations do not get assigned from a superscope – notice the line: This is happening because a DHCP server normally hands out addresses from a superscope starting with the first scope. After that scope is full, the server starts handing out addresses from the second scope, third scope, and so on.
186341 – Superscoping vs supernetting
I had been advise that I also need to add option 82 (DHCP-Relay support) to my DHCP server in predefined options:
To enable DHCP-relay support:
Using DHCP Server Management console (dhcpmgmt.msc) -> -> Right Click -> Set Predefined Options…, you can add option 82 as a customized option for DHCP Server
Does anyone know what to select?
Hello thanks for all your inputs;
I have just gone to my DHCP server which is connected to port 1/g1 Vlan10 and disabled the scope for 192.168.2.0 subnet, as this is mainly used for servers with fixed IP addresses and isn’t really necessary, now when I plug my client PC into port 1/g4 I receive a 192.168.20.0 address and when I plug it into port 1/g8 I receive a 192.168.30.0 address. Its working a treat. 🙂
One last thing, I cannot access the internet once I received a 192.168.20.0 or 192.168.30.0 IP address can you please tell me where I have gone wrong, must be something to do with my routes.