By default, when a DHCP client first boots it will try to renew the IP
Address it had the last time it was up. If your environment is Windows 2000
or later, you can configure the clients to release their IP Addresses when
they do a proper shutdown and therefore they would just request an IP
Address the next time they boot. Your other option would be to consider
short term leases however that would generate additional network traffic due
to the quicker renewals.
Although I think you know this, your post did not explicitly state that you
had *deleted the lease and removed registry information*. Which make me
think an ipconfig /release may not have been performed.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
"Jimmy Hogg" <Jimmy
(E-Mail Removed)> wrote in message
news:804BFC6D-C790-424B-95F3-(E-Mail Removed)...
DHCP Superscope problem
I am having an issue with a Windows 2003 DHCP server.
I configured a superscope that encompasses several scopes. One scope
is local to the server, and the remaining are using relay
agents to get packets to the DHCP server. I have tested all subnets
getting appropriate IP addresses from each subnet. The problem
arises when I move a machine between subnets. The server will
issue an IP from the previous subnet not the new subnet the computer has
been moved too.
I have attempted to delete the lease and remove registry information
related to the leased IP on the client machine. It will
still lease the old IP. Any help would be HIGHLY appreciated. Thanks in
advance!!