DHCP issue when changing subnets

I have DHCP and DNS set up on a W2K3 server, with several scopes configured.
All works fine, except when a client moves from one subnet to another. When
the client connects to the network on the new subnet, it is issued the same
address from the previous subnet. Even when manually releasing/renewing, the
same address is issued. The only way we can get the server to issue an
address on the new subnet is by deleting all references to the old address in
the client's registry, then deleting the lease on the server, and rebooting
the client. There has to be a way to correct this behavior, but I haven't
been able to find it. Any help would be much appreciated, thank you!

Is anyone willing to take a stab at this issue? I've still not been able to
solve this, maybe someone could point me in the right direction?

Can you explain the server configuration here please?
like
Server Ipaddresses
Scope IDs
and subnet ids of both which from client is move and also the subnet to
which client is moved.

-RamaSubbu SK

"David Goldsmith" <(E-Mail Removed)> wrote in
message news:6F82ED57-7C17-4D58-AEE0-(E-Mail Removed)...
>I have DHCP and DNS set up on a W2K3 server, with several scopes
>configured.
> All works fine, except when a client moves from one subnet to another.
> When
> the client connects to the network on the new subnet, it is issued the
> same
> address from the previous subnet. Even when manually releasing/renewing,
> the
> same address is issued. The only way we can get the server to issue an
> address on the new subnet is by deleting all references to the old address
> in
> the client's registry, then deleting the lease on the server, and
> rebooting
> the client. There has to be a way to correct this behavior, but I haven't
> been able to find it. Any help would be much appreciated, thank you!