Private IP Addressing

Unless your planning to use routers at each floor then this will not work. I would use 10.0.0.0 and a make of 255.255.0.0 and make it a flat network. Take the first 25 or so IP addresses and exclude them from the scope and create a scope from 10.0.0.1 - 10.0.255.254 this will give you more than what is needed and your won't need routers.

If you need any additional information, e-mail me directly.

Mike Gonzales

That sounds like a great IP scheme for you to use. It is simple and relates to the physical layout.

While you will need a router (or a server running router services), you will not need a router for each floor. To insure that the people on eachfloor get the correct IP, there are three ways you can approch the problem:

1) the simple, but possibly more expensive route. Put a server on each floor. If there is already a server on each floor, then just add DHCP to the services aready running. If not, I wouldn't recommend adding an NT or 2000 server. If you are familar with Linux you could add a DHCP server for a very reasonable cost.

2) Also expensive, more initial setup, but less maintainence in the long run and a more elegant solution. Get a router that has a separate interface for each floor or get a multi-homed server that has an ethernet interface for each floor. This is nessary because the DHCP server needs to know where the DHCP request is coming from, physically. A single interface with several IP subnets connected would not be able to distinquish one physical subnet from another.
With that layout you will be able to instruct you server/router to assign IP by interface.

3) You can implement DHCP forwarding agents thoughout your network. this can get complicated, so make sure that you do you homework first.

Good Luck

Using one subnet is just a silly idea. You will almost definitely run into ethernet cable run restrictions going to and from the furthest node on the network
Put a router on each floor using a subnet for each floor. This not only will allow for longer cable runs, but also reduce ethernet traffic collisions on the backbone. It will also reduce cabling troubleshooting to one floor after checking router connectivity for that floor. Using switches, you can also maintain an acceptable level of bandwidth available to each room on the floor. I imagine you'll prob eventually wanna do VOIP over this backbone someday so build it right.

Just a few thoughts...

Using one subnet is just a silly idea. You will almost definitely run into ethernet cable run restrictions going to and from the furthest node on the network
Put a router on each floor using a subnet for each floor. This not only will allow for longer cable runs, but also reduce ethernet traffic collisions on the backbone. It will also reduce cabling troubleshooting to one floor after checking router connectivity for that floor. Using switches, you can also maintain an acceptable level of bandwidth available to each room on the floor. I imagine you'll prob eventually wanna do VOIP over this backbone someday so build it right.

Just a few thoughts...

That IP Addressing scheme would work just fine. You will however need a router to route inbetween the various networks. What router you choose depends on the amount of traffic you expect. With Cisco equipment you could create Seperate VLANS for each subnet and only use 1 router. I would use fiber to run to the floors and CAT5 out to your workstations. Just be sure you will be under 100 meters on the CAT5. To make DHCP work, you just need to define the scope on the Server for the different networks and use a IP helper address to forward the DHCP requests. Hope this helps.

Greg

how does the DHCP assign addresses. waiting for your professional answers.

Obviously you just want an organized IP according to the floor they are into.

Just run your DHCP server as it is. The create a reservation and indefinite lease for respective computers so that the next time they boot up they will get the right one.

This question was auto closed due to inactivity