Segragate IP Ranges per building

You can't do that using Windows Server. You need to implement VLANs or divide network range for some sub-networks and then in each bulding use IPHelper or DHCP Relay Agent to send DHCP requests to DHCP server in another building or place one DHCP server per building to accomplosh that.

Windows DHCP service doesn't iclude anything to split networks to issue IP leases. It answers to broadcast address using options defined in scope/server

Regards,
Krzysztof

I would suggest you to begin with evaluating your current Network Infrastructure to look for VLAN capable switches which will allow you to define VLANs.

Once you have VLANs defined, with appropriate DHCP Server configuration,  you could create different DHCP Scopes on Windows Server to manage your network.

So, the first step would be to check your Network Hardware (Switches/Routers) and their VLAN capabilities.

Hope this helps!

Regards,

iSiek:
Sorry what i meant when i said windows server was to utilize DHCP in windows server. I should have made that clear. So your suggestion is to set up a DHCP server in our main bldg 135 then use DHCP relay to foward all requests to that DHCP server. However where/how would i define only that traffic coming from say bldg 160 to use only the specified ip ranges?
P,S i was under the impression IPHelper is used on layer 3...

pritamdutt:
I was struggling with the idea of using VLAN's it does seem to be our easiest answer. Our switches def support it. The part i was missing is, how do we get two vlans to communicate. Also how do i config dhcp so it assigns different ip ranges to each VLAN?

Thanks so far everyone.

Following two links will help you:

1. http://www.tech-faq.com/dhcp-relay-agents.html
2. http://www.informit.com/articles/article.aspx?p=1320201&seqNum=4


Hope this helps..

Any updates? Did it work?

We are running out of IP's because the old IT staff decided to use 255.255.255.0

Then the company should have kept them since they knew what they were doing.  Ethernet degrades at around 250-300 hosts.  They should never be larger than 254 Host segments.

Hey pritamdutt,
Sorry for the extended delay on my response. I have reviewed the information provided with my manager. We both feel using VLAN's to segregate our buildings is an unnecessary step. It has been brought to my attention that we could preform this action using a DC at each site which we then setup a dhcp server on as well using that dhcp server to issue IP addresses within the scope we define. Do any of you commenter's know how this would work? Or if it would work correctly?
Also just some thoughts on the VLAN, normally this is used to separate departments/floors for security purpose's. I am struggling with the idea of using VLAN's to segregate our buildings. Since VLAN's use MAC addresses to sort traffic to its intended port, how does the ip assignment come into play? How would I assign a created VLAN to retrieve IP from a specific scope thus preforming the desired action.

pwindell:
This website is used for instruction on topics less known then the person posting. Keep your negative comments to your self. Unless you have something informative to post then please do not spam my Topic with your negative comments.

Thanks.

Here's a simple 5 building layout that can support 2048 IPs with only a single LAN Router at each facility and will not overload the segments.  A Layer3 capable Switch can serve as the LAN Router in each building,...so if you have any of those that will save you money. The Switch Icons (and their labels) represent each IP Segment.  The IP#s of individual devices are not shown.  

The 4 WAN segment routing is Supernetted to carry 512 addresses. The labels on the WAN links indicate the Route Table entry and are not the address used on the actual WAN Interfaces which would be /30bit point-to-point segment from a completely different address set.

 

Not a lot of details given on the WAN links because the distance and the line technology all effect how it is handled.   Depending on the equipment and the situation a Layer3 switch may not be able to act as both a LAN Router and a WAN Router at the same time which could mean having separate Routers for the WAN and LAN.

Hi,

It is purely call of an organization on making a choice on technology to be deployed.

If you wish to use Separate DCs with DHCP Servers for each building make that you have a router installed at each building at where your Microwave Connection is terminated and is connected to local network in the building.

Once you have achieved the above, you need to do following steps:
1. DROP all DHCP traffic on the router; DHCP Traffic is targeted for port 67. This would prevent any possibility of incorrect IP getting assigned to any machine.
2. Great the machine in Building 160 has received IP from DHCP Server at building 160, but this machine is not able to talk to server in BUILDING 161. Now how do we do this? This can be achieved using
- a) Defining the IP Address of the router as Gateway in DHCP Configuration for the Clients.
- b) Defining routes in the router for other available IP Address Ranges on the network. Please note this can be done using either RIP or Static Routing, as may be the choice of implementer.

Hope this helps....

Regards,

It is purely call of an organization on making a choice on technology to be deployed.

Yes,..and quite often those calls are bad ones.  Too many consultants also make bad ones, often driven by what the consultant wants to sell to the client because of whatever marketing is driving the consultant's company.

My goal here is to always give the most efficient, most straight forward network design, that falls within what can be feasibly explained in simple Forum Messages (since we can actually be on site).