<p><a href="http://wincert.net/wp-content/uploads/2015/01/networking.jpg"><img class="alignnone size-full wp-image-562" src="http://wincert.net/wp-content/uploads/2015/01/networking.jpg" alt="networking box" width="720" height="340" /></a></p>
<p>Here&#8217;s one of the issues which caused me a lot of headaches until we finally resolved it.</p>
<p>We have 4 vlans, one DHCP that has configured one superscope and a scope for each vlan (different subnet). When someone connects the laptop to VLAN3 for instance, the user gets the proper IP, but if he switches vlan to vlan1, he will get an address from vlan3.</p>
<p>If I release the IP address and renew it, I will again get the wrong VLAN3 address when physically connected to vlan1.</p>
<p><!--more--></p>
<p>If I just type <b>ipconfig /renew</b>, I get an error message: <b>Unable to contact the DHCP server</b>.</p>
<p>We we&#8217;re investigating a lot but haven&#8217;t find the solution. It usually helped if if I made a DHCP reservation on vlan3 and remove the lease from vlan1.<br style="padding: 0px; margin: 0px;" /><br style="padding: 0px; margin: 0px;" />Also, if I have changed the network adapter to static IP address and then trie to get a DHCP address, I usually got a proper IP address, in this case from vlan1.<br style="padding: 0px; margin: 0px;" /><br style="padding: 0px; margin: 0px;" />Just to mention, that everything was working fine when we had DHCP server on each VLAN, but once we&#8217;ve consolidated our servers and started using only one DHCP server, this issues started to emerge.</p>
<p><span style="color: #008000;">Solution:<br />
</span>Remove the Scopes from the Superscope.</p>
<p>Solution I got was to remove the superscope and to recreate the scopes, but that wasn&#8217;t necessary. You only need to remove the scopes from the superscope. When the last scope is removed from the superscope, the superscope will automatically be deleted.</p>