I am wondering if someone can help me with the following situation or if there is any documentation on it somewhere.
We have 2 buildings connected through a T1 line. In building 1 we are running Windows NT 4.0 Terminal Server running DHCP. In building 2, we have basic clients running Windows, etc and they are using static ip addresses. I would like to have the one central DHCP server so building 2 can access the DHCP server in building one.
We have Cisco 2514 series routers. Thanks to anyone that can help.
We just migrated from static IPs to DHCP in our building about two weeks ago (although I wasn't directly involved in setting it up so my advice that follows is somewhat second hand). It is probably easier than you think though. Just set up an IP helper address on the ethernet interface where your clients reside. Looks like:
ip address 126.96.36.199
ip heper-address 10.10.10.1 (this is your DHCP server)
All broadcasts using eight different UDP ports (including DHCP/BOOTP) will be forwarded to the ip address that you specify. You can also just specify the subnet instead of the server address if you need to hit more than one server. You can also specify more than one helper address/subnet but the broadcasts will be forwarded to all specified helpers.
On the 2514's Ethernet interface in building 2 (client side)configure: ip helper-address x.x.x.x where x.x.x.x is the ip of the dhcp server. This will allow dchp (and other, eg bootp) broadcasts to be relayed over the WAN link to building 1. To limit broadcasts to DCHP only:
no ip forward-protocol udp tftp
no ip forward-protocol udp dns
no ip forward-protocol udp time
no ip forward-protocol udp netbios-ns
no ip forward-protocol udp netbios-dgm
no ip forward-protocol udp tacacs
ip forward-protocol udp bootpc
Search for "ip helper-address dhcp forward-protocol" on CCO for examples.
we also have set up two buildings over a t1. depending on how how you have subneted, you might want to keep traffic separated by setting up another dhcp server. For exmaple at the main site we have 192.168.1.x and the secondary site is 192.168.2.x. Each site has its own dhcp server. The traffic stays seperate and no excess traffic over the t1 is transmitted.
The solution of two DHCP servers is much better and should cause lower maintenance burden as well.
However, if you insist on the centralized DHCP solution, make sure that you have two pools of IP addresses one for each site and the pool for the remote site is routable by the remote router (i.e. assign the gateway IP for the DHCP server remote pool as the ethernet of the remote router)
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...