Need help with Multiple DHCP Scopes

[Tom]

Hello,
We currently have 2 networks. One is serviced by a Windows 2008 Server that
is running DHCP and assigning this range of addresses:
192.168.1.x
255.255.255.0
192.168.1.1
The second network has a Windows 2003 Server that is running DHCP that
assigns this range of addresses:
192.168.2.x
255.255.255.0
192.168.2.1
We would like to remove the second domain and merge it with the first, yet
we have more clients than 1 DHCP server can service. We have many static
addresses assigned in both locations (printers, WAP, etc.) so I'd like to
continue using these two ranges of addresses. Can 1 DHCP server do that? We
have a content filter that must be installed between the router and the
network and so I'm not sure how to connect the networks via routers. What
are my options? I have tried to configure a SuperScope that has the second
range of addresses and then added the second range IP address to the servers
nic, but that only allows the second network to connect to the server and not
the internet. As you can tell, I need help.
Thanks for any that you can provide.
Tom

[Robert L. \(MS-MVP\)]

I am not sure I understand the situation. If "only allows the second network
to connect to the server and not the internet", make sure route 192.168.2.x
only.
--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Tom" <Tom@discussions.microsoft.com> wrote in message
news:033DA981-56A2-4B96-984D-686FB9F9C2A9@microsoft.com...
> Hello,
> We currently have 2 networks. One is serviced by a Windows 2008 Server
> that
> is running DHCP and assigning this range of addresses:
> 192.168.1.x
> 255.255.255.0
> 192.168.1.1
> The second network has a Windows 2003 Server that is running DHCP that
> assigns this range of addresses:
> 192.168.2.x
> 255.255.255.0
> 192.168.2.1
> We would like to remove the second domain and merge it with the first, yet
> we have more clients than 1 DHCP server can service. We have many static
> addresses assigned in both locations (printers, WAP, etc.) so I'd like to
> continue using these two ranges of addresses. Can 1 DHCP server do that?
> We
> have a content filter that must be installed between the router and the
> network and so I'm not sure how to connect the networks via routers. What
> are my options? I have tried to configure a SuperScope that has the
> second
> range of addresses and then added the second range IP address to the
> servers
> nic, but that only allows the second network to connect to the server and
> not
> the internet. As you can tell, I need help.
> Thanks for any that you can provide.
> Tom

[Tom]

I have 192.168.2.1 set as the gateway on the second network. The 192.168.2.1
address is the second IP address on the server of the first network, who's
first IP address is 192.168.1.2.
Thanks.


"Robert L. (MS-MVP)" wrote:

> I am not sure I understand the situation. If "only allows the second network
> to connect to the server and not the internet", make sure route 192.168.2.x
> only.
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "Tom" <Tom@discussions.microsoft.com> wrote in message
> news:033DA981-56A2-4B96-984D-686FB9F9C2A9@microsoft.com...
> > Hello,
> > We currently have 2 networks. One is serviced by a Windows 2008 Server
> > that
> > is running DHCP and assigning this range of addresses:
> > 192.168.1.x
> > 255.255.255.0
> > 192.168.1.1
> > The second network has a Windows 2003 Server that is running DHCP that
> > assigns this range of addresses:
> > 192.168.2.x
> > 255.255.255.0
> > 192.168.2.1
> > We would like to remove the second domain and merge it with the first, yet
> > we have more clients than 1 DHCP server can service. We have many static
> > addresses assigned in both locations (printers, WAP, etc.) so I'd like to
> > continue using these two ranges of addresses. Can 1 DHCP server do that?
> > We
> > have a content filter that must be installed between the router and the
> > network and so I'm not sure how to connect the networks via routers. What
> > are my options? I have tried to configure a SuperScope that has the
> > second
> > range of addresses and then added the second range IP address to the
> > servers
> > nic, but that only allows the second network to connect to the server and
> > not
> > the internet. As you can tell, I need help.
> > Thanks for any that you can provide.
> > Tom
>
>

[Bill Grant]

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?

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.

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.

Internet
|
router/firewall {static route 192.168.2.0 255.255.255.0 192.168.1.254}
192.168.1.1
|
LAN1 machines
192.168.1x dg 192.168.1.1 {from DHCP scope 1}
|
Server 2008 DC
192.168.1.n dg 192.168.1.1 DHCP server with two scopes
|
192.168.1.254 dg 192.168.1.1
RRAS DHCP relay enabled
192.168.2.1 dg blank
|
LAN2 machines
192.168.2.x dg 192.168.2.1 {from DHCP scope 2}

[Tom]

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

[Guus Ellenkamp]

As you are using a switch instead of a router you are in one network, not
two, so you don't have two subnets.

Just use one subnet for the two networks, so all machines would have
192.168.1.x with subnet mask 255.255.255.0 or all machines have 192.168.x.x
with subnet mask 255.255.0.0.

"Tom" <Tom@discussions.microsoft.com> wrote in message
news:B217C5CA-C511-4B39-891C-BB1572152B86@microsoft.com...
> 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

[Tom]

Since we have 350 plus clients, which should I use?


"Guus Ellenkamp" wrote:

> As you are using a switch instead of a router you are in one network, not
> two, so you don't have two subnets.
>
> Just use one subnet for the two networks, so all machines would have
> 192.168.1.x with subnet mask 255.255.255.0 or all machines have 192.168.x.x
> with subnet mask 255.255.0.0.
>
> "Tom" <Tom@discussions.microsoft.com> wrote in message
> news:B217C5CA-C511-4B39-891C-BB1572152B86@microsoft.com...
> > 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
>
>
>