K
Kevin
How can I deploy a second RIS server in a second site in
one domain using DHCP Relay?
one domain using DHCP Relay?
Kevin said:How can I deploy a second RIS server in a second site in
one domain using DHCP Relay?
Kevin said:Hello, Ace
Thanks for your reply -- here is a better explanation of
my situation. Thanks for any feedback.
We have two locations which form one domain -- at the
main site we have a DHCP server and a RIS server. Then at
another site we have a DHCP relay server which get IP
address from the main site and distributes the IP
addresses to computers at that site. We do this because
there are two separate set of IP addresses. Both sites
are connected by a T1 connection & router. To transfer
the packages via the TI connection would cause alot of
network traffic and take a long time to install.
Therefore, we wanted to setup a 2nd RIS server at the 2nd
site. But have been unsuccessful at that site with RIS --
the computers cannot access the DHCP Relay server and
cannot get an IP address in order to install the
Operating system using F12. With our current network is
it possible to have a second RIS server at the second
site which uses DHCP Relay? If so how can we do it.
Cary Shultz said:Kevin,
This is not accurate. You can have multiple DHCP Servers. You just
need to make sure that there is no range of IP Addresses that is
'handled' by multiple DHCP Servers. So, if you have 215 computers in
your environment you could have three DHCP Servers, for example. One
that would handle the range 192.168.1.30 - 192.168.1.100 and one that
would handle the range 192.168.1.101 - 192.168.1.170 and finally one
that would handle the range 192.168.1.171 - 192.168.1.250. Not that
you would necessarily want to do it his way, but you technically
could! Who told you this?
HTH,
Cary
-----Original Message-----
In Cary Shultz [A.D. MVP] <[email protected]> made a post then I commented
belowKevin,
This is not accurate. You can have multiple DHCP Servers. You just
need to make sure that there is no range of IP Addresses that is
'handled' by multiple DHCP Servers. So, if you have 215 computers in
your environment you could have three DHCP Servers, for example. One
that would handle the range 192.168.1.30 - 192.168.1.100 and one that
would handle the range 192.168.1.101 - 192.168.1.170 and finally one
that would handle the range 192.168.1.171 - 192.168.1.250. Not that
you would necessarily want to do it his way, but you technically
could! Who told you this?
HTH,
Cary
Wasn't me !!!
:-D
Just to add to your example, if there's multiple subnets or locations, I
would normally recommend to setup a DHCP server in every subnet or location
so there's no one point of failure.
Ace
.
My boss was the individual who said you can only have one
DHCP server per domain according to 70-216
-----Original Message-----
In Cary Shultz [A.D. MVP] <[email protected]> made a post then I commented
belowKevin,
This is not accurate. You can have multiple DHCP Servers. You just
need to make sure that there is no range of IP Addresses that is
'handled' by multiple DHCP Servers. So, if you have 215 computers in
your environment you could have three DHCP Servers, for example. One
that would handle the range 192.168.1.30 - 192.168.1.100 and one that
would handle the range 192.168.1.101 - 192.168.1.170 and finally one
that would handle the range 192.168.1.171 - 192.168.1.250. Not that
you would necessarily want to do it his way, but you technically
could! Who told you this?
HTH,
Cary
Wasn't me !!!
:-D
Just to add to your example, if there's multiple subnets or locations, I
would normally recommend to setup a DHCP server in every subnet or location
so there's no one point of failure.
Ace
.
Cary Shultz said:Kevin,
I *think* that your boss might be mistaken. I would be interested in
knowing where in 70-216 it states that you can have only done DHCP
Server per domain. But, let's not make this a big deal. No one
knows everything about everything in this industry! And no one ever
will! It changes too often too quickly.
Cary