DHCP issue - wrong scope responding

I think I have the issue described in
http://support.microsoft.com/kb/867792/en-us :
I have two LANs with a DHCP server in each. Server-A in LAN-A is that LAN's
DHCP server and is also the router between LAN-A and LAN-B Server-B in LAN-B
is that LAN's DHCP server.

I plug my laptop in to LAN-A, and Server-A gives it an IP address. I remove
the laptop and move it to LAN-B, and it retains the LAN-A address, as the
article describes.

Questions: can anybody see a different reason for the behavior? I might be
able to use a different server as the router- will that make a difference?

Also, is there a way to get the hotfix quickly, without MSFT rigamarole?
Thanks
BFH

The correct way to do this is never run DHCP on the same server acting as a
router between the LANs unless that server is supposed to handle both sides
and has a Scope for both sides.

But if you aren't going to do it the right way, then:

1. Go into the DHCP MMC, right-click on the server name node
2. Choose Properties
3. Choose the Advanced tab
4. Click the Bindings Button
5. Make sure the correct Nic for the correct segment is enable, and that the
other one is not.

If that doesn't work, then stop doing it on that machine and run DHCP on
something else.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"BFH" <(E-Mail Removed)> wrote in message
news:F6CBBBF3-EA80-4F7C-8A8E-(E-Mail Removed)...
>I think I have the issue described in
> http://support.microsoft.com/kb/867792/en-us :
> I have two LANs with a DHCP server in each. Server-A in LAN-A is that
> LAN's
> DHCP server and is also the router between LAN-A and LAN-B Server-B in
> LAN-B
> is that LAN's DHCP server.
>
> I plug my laptop in to LAN-A, and Server-A gives it an IP address. I
> remove
> the laptop and move it to LAN-B, and it retains the LAN-A address, as the
> article describes.
>
> Questions: can anybody see a different reason for the behavior? I might
> be
> able to use a different server as the router- will that make a difference?
>
> Also, is there a way to get the hotfix quickly, without MSFT rigamarole?
> Thanks
> BFH

Actually, I did all that already before posting. I will probably end up
moving routing to another PC. Thanks for replying.

"Phillip Windell" wrote:

> The correct way to do this is never run DHCP on the same server acting as a
> router between the LANs unless that server is supposed to handle both sides
> and has a Scope for both sides.
>
> But if you aren't going to do it the right way, then:
>
> 1. Go into the DHCP MMC, right-click on the server name node
> 2. Choose Properties
> 3. Choose the Advanced tab
> 4. Click the Bindings Button
> 5. Make sure the correct Nic for the correct segment is enable, and that the
> other one is not.
>
> If that doesn't work, then stop doing it on that machine and run DHCP on
> something else.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "BFH" <(E-Mail Removed)> wrote in message
> news:F6CBBBF3-EA80-4F7C-8A8E-(E-Mail Removed)...
> >I think I have the issue described in
> > http://support.microsoft.com/kb/867792/en-us :
> > I have two LANs with a DHCP server in each. Server-A in LAN-A is that
> > LAN's
> > DHCP server and is also the router between LAN-A and LAN-B Server-B in
> > LAN-B
> > is that LAN's DHCP server.
> >
> > I plug my laptop in to LAN-A, and Server-A gives it an IP address. I
> > remove
> > the laptop and move it to LAN-B, and it retains the LAN-A address, as the
> > article describes.
> >
> > Questions: can anybody see a different reason for the behavior? I might
> > be
> > able to use a different server as the router- will that make a difference?
> >
> > Also, is there a way to get the hotfix quickly, without MSFT rigamarole?
> > Thanks
> > BFH
>
>
>

"BFH" <(E-Mail Removed)> wrote in message
news:CA8E449D-AAC0-4270-831A-(E-Mail Removed)...
> Actually, I did all that already before posting. I will probably end up
> moving routing to another PC. Thanks for replying.

That is the best way. No sense in just asking for trouble, which the other
method does.

Make sure that the "Router" machine is not configured to forward (relay)
DHCP queries anywhere. None of that should be enabled,...concerning DHCP the
Router needs to just "stay out of it" and not get involved.

Also, do not use Superscopes (incase you thought of doing so). Such things
are not what Superscopes are for and I see people screw their systems up all
the time by tying to use Superscopes.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Well, I did everything right, I think, and it's still misbehaving.

I'm not using a superscope, and I moved the routing service to another
machine. I did not add "DHCP relay agent" to the routing machine- it's
plain-vanilla routing:

LAN A - has server A as DHCP server
server C is dual-homed on both LAN A and LAN B. It's the default gateway
for LAN B; the def. gate. on LAN A is an internet connection, but that
firewall has a route back to server C for LAN B. There are no static routes
or additional protocols on server C.
LAN B - has server B as DHCP server

Still, when I move my laptop from LAN A to LAN B, it keeps the LAN A
address. Both DHCP servers are running, and the event logs have no error
messages from DHCP. Arrgh!

Is there anything else I should be looking at here- anything on the routing
machine, or in DHCP config?

Thanks,
BFH


"Phillip Windell" wrote:

> "BFH" <(E-Mail Removed)> wrote in message
> news:CA8E449D-AAC0-4270-831A-(E-Mail Removed)...
> > Actually, I did all that already before posting. I will probably end up
> > moving routing to another PC. Thanks for replying.
>
> That is the best way. No sense in just asking for trouble, which the other
> method does.
>
> Make sure that the "Router" machine is not configured to forward (relay)
> DHCP queries anywhere. None of that should be enabled,...concerning DHCP the
> Router needs to just "stay out of it" and not get involved.
>
> Also, do not use Superscopes (incase you thought of doing so). Such things
> are not what Superscopes are for and I see people screw their systems up all
> the time by tying to use Superscopes.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>

"BFH" <(E-Mail Removed)> wrote in message
news:51C7F504-16B5-4F0F-B77F-(E-Mail Removed)...
> Well, I did everything right, I think, and it's still misbehaving.

Are you powering the laptop completely off? You can't leave it running and
can not let it hybernate.

I move laptops around here all the time between subnets around here,...never
a problem.

> Is there anything else I should be looking at here- anything on the
> routing
> machine, or in DHCP config?

No, absolutely nothing. If a Client won't release an IP#, the DHCP can't do
anything about it. DHCP Servers are *passive*,...all they do is answer
requests,...and the requests won't cross routers without DHCP Relay enabled.


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Yep, laptop off completely while moved. Rebooted servers just for the hell
of it, too.

Oh, well, hotfix here we come. Thanks for your help.
BFH

"Phillip Windell" wrote:

> "BFH" <(E-Mail Removed)> wrote in message
> news:51C7F504-16B5-4F0F-B77F-(E-Mail Removed)...
> > Well, I did everything right, I think, and it's still misbehaving.
>
> Are you powering the laptop completely off? You can't leave it running and
> can not let it hybernate.
>
> I move laptops around here all the time between subnets around here,...never
> a problem.
>
> > Is there anything else I should be looking at here- anything on the
> > routing
> > machine, or in DHCP config?
>
> No, absolutely nothing. If a Client won't release an IP#, the DHCP can't do
> anything about it. DHCP Servers are *passive*,...all they do is answer
> requests,...and the requests won't cross routers without DHCP Relay enabled.
>
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>