I have a 2003 server network and just upgraded all my switches and vlan'd everything out by building. I created the Superscope on my DHCP server and added all the scopes for each building. The problem exists when a computer gets it IP from the correct scope and then I move the computer to another building, it tries to find the DHCP server and cannot and reissues the ip from the existing building. If I delete the lease from the snap-in. It just reissues it again. If I exclude the no longer wanted ip from it existing scope, the computer than dhcps the correct ip from the correct scope. Until I move the computer, it will cause the problem again. How can I get the DHCP server to release the old ip and issue the new ip from the different scope? All clients are XP sp3, all Servers are 2003 SP2.

Hi, Based on your description, it seems normal. Why did you configure superscope? If there is no special requirement, we don’t need superscope. Generally, if you have more than one logical IP network is used on each physical subnet or network or you need to support remote DHCP clients located on the far side of DHCP and BOOTP relay agents, superscope is the solution. Otherwise, it’s not needed. Table 4.3 DHCP Scope for Servers A and B in following article seems explains your problem. If so, we need to disable superscope. Superscopes http://technet.microsoft.com/en-us/library/cc958938.aspx Thanks. This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.