Re: Need help with Multiple DHCP Scopes

Answers in line.

"Bill Grant" wrote:

Tom,

I can see why Bob doesn't understand the situation. I don't and I
doubt that you do either.

You do not have too many machines for one DHCP server to handle. It can
handle thousands of machines in multiple scopes without any trouble. It can
also handle multiple networks which are linked by routers as long as the
routers can handle DHCP relay.

Your problem seems to be more of a routing problem that a DHCP problem.
Where are these two networks located? How are they linked together?

They are located in separate buildings a few blocks apart and are connected
by a dedicated T1 line with ethernet convertor boxes on each end. I'm
currently connected directly from a switch in one network to a switch in the
other.

Are you trying to tell us that you have two segments which are linked by
one of the servers? If that is the case you can simply run two scopes on the
W2008 server and enable DHCP relay on the machine connecting the two
segments to solve the DHCP problem.

I think this is the answer to my problem. We have one network that has a
192.168.1.x scope of addresses and the other that uses 192.168.2.x addresses.
On the W2008 server do I need to setup a super scope or just 2 normal scopes
- 1 that is serving 192.168.1.x and the other that is 192.168.2.x addresses?

How are you routing the traffic in the 192.168.2.x subnet? Are you using
the W2k3 server as a RRAS router? You will need to make some changes to your
scope and also the your gateway router to get that to work. Here is a setup
which will do that.

Not using RRAS routing. Here is how it is currently setup.

Internet
|
router/firewall
192.168.1.1
|
Content Filter
192.168.1.50
|
WServer 2008 DC
192.168.1.2 (DHCP server with two scopes)
192.168.1.x and (192.168.2.x - superscope)
| |
Switch Switch
| |
LAN1 machines LAN2 machines
192.168.1.x 192.168.2.x
from scope 1 from scope 2

The machines on LAN1 are fine. The machine on LAN2 will only connect the
the W2008 Server, but won't route to the internet. Is that where DHCP
relaying
comes into effect. Thanks for your patiences. I've always dealt with small
networks with only IP scope and am learning as I go.
Tom
.

Relevant Pages

  • Re: Application Hang
    ... Do not run 2 DHCP servers together, that will create conflicts for the client. ... Under DNS management console is the server listed under Forward lookup zone, if yes with how many entries and which ones? ... I hope this is what you were looking for by way of scope options: ...
    (microsoft.public.windows.server.networking)
  • Re: SBS Reinstall
    ... In DHCP when I select the server it shows 192.168.16.2 and when I expand it ... "The wizard cannot set the DHCP scope options" error message when you run ... Ethernet adapter local area connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: ...OS is Win 2003 Std...
    ... Microsoft Small Business Server Support ... >> The scope I have defined is identical to what you have listed, except for>> the range of the scope; ... but the message in the system error log>> indicates that it is not servicing clients because there is no NIC with a>> static IP assigned. ... >> The messages can be produced at will currently by simply restarting the> DHCP>> server service. ...
    (microsoft.public.windows.server.sbs)
  • Re: No DHCP Leases Available - SBS2K3
    ... delete scope 192.168.1.240 dhcpfullforce (command ... scope with two suggested options; stopped DHCP service; ran CEICW again - ... same message as above; started DHCP service; opened Change Server IP Address ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem With Joining XP Computer to Windows 2003 Domain
    ... One, if the DC is connected directly to the Internet, DISCONNECT IT by ... I have assigned the server to Domain Controller ... > seem to be pointing to DHCP scope possibly on the server's configuration ...
    (microsoft.public.windowsxp.network_web)