You have 5 different subnets... I'm assuming you are still servicing them
from a single DHCP Server?
If so, are you using a Superscope? Are you also using DHCP/BOOTP Relay
Agents?
A superscope is >not< needed in the case where DHCP/BOOTP Relay Agents are
used to forward traffic from each subnet to the central DHCP Server. See
http://www.microsoft.com/resources/d...uperscopes.asp
for more information on using Superscopes...
If you are using Relay Agents to direct traffic at the DHCP Server, remove
the superscope from the DHCP Server. What the superscope is doing is making
all the individual scopes work together as one large scope, so any client
coming in on Subnet B with an IP from subnet A will be given an Ack, because
the DHCP Server is being told that they are all one big subnet (a supernet),
so any address works anywhere. If this is not the case, then you'll need to
remove the superscope tying the scopes together.
Once removed, when a client comes in on Subnet B with an IP from subnet A,
it will receive a Nack (as the DHCP Server will now be able to distinguish
the two subnets), and then the client will acquire an IP on the correct
subnet.
-Chris
--
==============================
Chris Edson
(E-Mail Removed)
This posting is provided "AS IS" with
no warranties, and confers no rights.
===============================
"Marvin Bordelon" <(E-Mail Removed)> wrote in message
news:504b01c49108$83867710$(E-Mail Removed)...
> We have a 5 story building here. We have each floor set up
> on a different subnet.(i.e. floor 5 uses 10.100.105.x and
> floor 4 uses 10.100.104.x) When moving from one floor to
> another the workstation retains the ip address from the
> original floor. If I release the ip address before
> disconnecting from the original floor and then bring it to
> the other floor and renew the ip address, it pulls an ip
> address in the correct subnet. Any ideas?