DHCP SuperScope

[Peter Barton]

I have a small frame relay network with all routers using
BOOTP Relay agents to talk to a single Microsoft DHCP
Server. I have set up each site with its own IP subnet
and a separate scope inside the SuperScope.

The Problem:

I have a user who goes from site to site with a laptop and
they get their IP address via DHCP. When the user goes to
a new site his computer is sending out a DHCPRequest with
the original IP address, which is not valid at the new
site. However, the Microsoft DHCP Server allows the
requested IP address to be assigned to the laptop even
though the GIADDR field in the packet is for the new site.

Can someone please let me know if there is a way to make
the DHCP Server force the user's laptop to get an IP
address from the configured range for the GIADDR.

Thank you,

Peter Barton

 

[Marc Reynolds [MSFT]]

Hi Peter,

I am not quite clear on how you are using DHCP superscoping in your
scenario. If the DHCP server is simply serving addresses for several
different physical networks, you should not superscope the individual subnet
scope together.

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

I have worked with large scale DHCP servers before, but
this is my first time to use Micorsoft DHCP Server. I was
under the assumption that I needed to add all the ranges
to a superscope so that the DHCP Server would be aware of
each one of the different ranges.

What I am getting from your reply tells me that I should
set up each range independently on the same DHCP Server
and leave them out of the superscope. By doing this the
DHCP server will then only assign IPs from the range that
the BOOTP relay agent is on?

Peter

 

[Marc Reynolds [MSFT]]

You are correct!

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Peter Barton]

Thank you.

Peter

-----Original Message-----
You are correct!

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.





.