General discussion

Locked

Private IP Addressing

By azam.quadri ·
Private IP Addressing
I have to design an IP addressing for 8 storied hotel.
Each floor has a 10/100 switch, and each floor should have max of 100 hosts, I am planning to use 10.1.1.10 to 10.1.1.255 for floor one and 10.2.1.10 to 10.2.1.255 for floor two and so on untill 10.8.1.10 to 10.8.1.255 and subnet as 255.255.255.0.
I want to ask the IP gurus is this design appropriate and if not what is the another easiest addressing scheme, and if i define all these 8 scopes in Windows 2000 DHCP server with the same subnet mask, how does the DHCP assign addresses. waiting for your professional answers

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Private IP Addressing

by DC1 In reply to Private IP Addressing

You can create the 8 scopes and then add them to a superscope. Then you will have to assign the scope to the appropriate network segment. The range you are using will work for what you are looking for.

Collapse -

Private IP Addressing

by azam.quadri In reply to Private IP Addressing

Poster rated this answer

Collapse -

Private IP Addressing

by NTOz In reply to Private IP Addressing

Since you want no more then 100 per floor, it might be easier to use the 192.168.x.x range with 255.255.255.128 mask that would limit each floor to having a max of 256 addresses for the floor. You can then eliminate the remaining addresses in your scope. Then each floor,

Floor 1

192.168.1.0

Floor 2

192.168.2.0

Floor 3

192.168.3.0

Floor four

192.168.4.0

And so on, no sense in using a class A address when a class C would do just fine for what your trying to do. I dont know if I would even limit the scope, I wouldnt see many guests setting up small LAN's in there rooms, perhaps a second guest joins the room, mabey they both want to plug in. Your also going to have to limit the least to one day so that at the end ofeach day, it free's up the addresses. Keep it simple.

Collapse -

Private IP Addressing

by NTOz In reply to Private IP Addressing

I like the super scope idea also, but I might want to break it down too. Dont have enough information as to how its going to be administred.

Pete

Collapse -

Private IP Addressing

by NTOz In reply to Private IP Addressing

One note on the superscope idea, they are designed to be used on the same physical network. They are generaly used when you want to have DHCP answer with more then one range on the same broadcast domain. This might become a problem even with Layer 2switches because all broadcasts will be sent to all switches on all floors. This may end up causing issues both problematic as well as administrative. If I were doing this, I would go the additional step of having a backbone router, layer 3, or layer 2 VLAN in order to isolate each floor on its own subnet I would then either use the switches or routers to assign the DHCP addresses or configure them to forward dhcp requests to the segment that the Server is on. I know this is a much more costly solution, but i think its a better one that will pay for it self in the long run. Your solution would work with a superscope and a flat network but the potential of 800 stations on a layer 2 switch might cause issues with broadcasts as they are not directed by a layer 2 switch.

Pete

Collapse -

Private IP Addressing

by azam.quadri In reply to Private IP Addressing

Poster rated this answer

Collapse -

Private IP Addressing

by cportman In reply to Private IP Addressing

Your description does not say whether or not you are using a router between floors. I don't think you are. In your configuration if you used the 255.255.255.0 subnet mask you would have to have routers between floors.

If you are routing betweenfloors, you are probably better off with a class c. You don't gain anything by using the class a.

If you aren't routing, then you truly could just make one class A or B network id with the default subnet mask. And you only need one scope. Yourswitches will learn everybodys mac address and correctly segment your network. You shouldn't have any traffic problems with 800 users (not that they are going to all be on at the same time)

good luck
Chris

Collapse -

Private IP Addressing

by azam.quadri In reply to Private IP Addressing

Poster rated this answer

Collapse -

Private IP Addressing

by Ted Laun In reply to Private IP Addressing

I agree with Answer 3 Keep it simple, but I have I suggestion for you since this is for a hotel and I bet many of your Customers will be using a VPN client to access their corporate network try to make your subnet as unique as possible. I have seen a problem if a user is trying to access a subnet on their corporate network and your subnet is the same, it may cause the client machine to become confused and it is going to try to look at the closes subnet first which is not a good thing. (You could easily alienate an entire Company by not giving consistent access to their corporate network). I would suggest something in the 172.16.x.x ot something like 10.173.x.x

Collapse -

Private IP Addressing

by azam.quadri In reply to Private IP Addressing

Poster rated this answer

Back to Windows Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums