Netwrkengeer
IS-IT--Management
Ok I dont fully understand tcp/ip's implementation. For example, when you setup a new network and need to apply ip addresses to 100 machines, how do I know what addresses to give each machine, also how do you subnet.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
GENERAL TCP/IP
- Thread starter Netwrkengeer
- Start date
- Status
Really depends on if you want to connect to the internet? If you're not connecting to the internet then it's easy. Connecting to the Internet puts a whole new prospective on your solution.
Need to know if your network intends to grow, if you only have 100 PC's to connect and don't really care about growth then a regular Class C private address (192.168.0.0 to 192.168.255.255) will work fine.
Subnetting is if you intend to grow above the 100 pc's or they are located in different areas where a router will come into play. If there is a router between you and the other side you will need to subnet. If all your PC's are connected to the same hub then you can use a regular Class C subnet Mask of 255.255.255.0.
Although your question is short the answer is far from it. I could write an entire book on Subnetting, in fact there are lots of them. If you need a particuar answer to a question I'll need more detail as to what you want to do...
Sorry I'm so general in my answer...If I get more information I will be more specific...
david e
*end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.*
Need to know if your network intends to grow, if you only have 100 PC's to connect and don't really care about growth then a regular Class C private address (192.168.0.0 to 192.168.255.255) will work fine.
Subnetting is if you intend to grow above the 100 pc's or they are located in different areas where a router will come into play. If there is a router between you and the other side you will need to subnet. If all your PC's are connected to the same hub then you can use a regular Class C subnet Mask of 255.255.255.0.
Although your question is short the answer is far from it. I could write an entire book on Subnetting, in fact there are lots of them. If you need a particuar answer to a question I'll need more detail as to what you want to do...
Sorry I'm so general in my answer...If I get more information I will be more specific...
david e
*end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.*
jimbopalmer
Programmer
As a general rule of thumb: Assume the router will need .1, reserve .2 and .3 for VRRP, Start numbering your hubs from .4 to .9, and assign users from .10 up . I tend to keep .50 to .254 for test boxes
So 192.168.1.1 will be your router, subnet mask 255.255.255.0
Your first Computer will be 192.168.1.10 and away you go!
If your have a DHCP server, I suggest .49 to .249 be DHCP
I love everyone til they prove otherwise, sadly some prove otherwise SO quickly
So 192.168.1.1 will be your router, subnet mask 255.255.255.0
Your first Computer will be 192.168.1.10 and away you go!
If your have a DHCP server, I suggest .49 to .249 be DHCP
I love everyone til they prove otherwise, sadly some prove otherwise SO quickly
jimbopalmer
Programmer
darn .250 to .254 for test I love everyone til they prove otherwise, sadly some prove otherwise SO quickly
- Thread starter
- #5
Netwrkengeer
IS-IT--Management
OK so generally if there is no need to access the internet then it doesn't matter what the addresses are.
But if I do need access to the internet, I must deside how many michine will need access. That much I assumed but was never positive about.
now specifically pertaining to subnetting, I want to know how to actually borrow a bit from my ip to create the subnet, I learned it once, but cannot remember how to do it (you know the actual math behind it)
But if I do need access to the internet, I must deside how many michine will need access. That much I assumed but was never positive about.
now specifically pertaining to subnetting, I want to know how to actually borrow a bit from my ip to create the subnet, I learned it once, but cannot remember how to do it (you know the actual math behind it)
Actually just like regular math, Subnetting also has a calculator. If you go out to then their download page. All the way at the bottom is the subnet calculator. Download that and you can configure your subnet the way you'd like.
Subnetting is basically playing around with the subnet mask. for example.
My Dallas office quickly ran out of IP Addresses using a regular Class B address of 172.16.4.0/255.255.255.0. I was able to increase the network of 254 addresses to 510 by adjusting the subnet mask to 255.255.254.0. (I was able to do this because I was in the private address range) What this essentially does is place one bit back to the host by taking it away from the network address. This one bit gave me a range of
172.16.4.1 to 172.16.5.254
Now to reverse that.....
I have a full class B address of 172.16.4.0 and I need at least two different subnets. by borrowing one bit from the host address I could split my class c into two different subnets using a subnet mask of 255.255.255.128. This would give me the range of
172.16.4.1 to 172.16.4.126 = Network 1
172.16.4.128 to 172.16.4.254 = Network 2
This is a down and dirty way of explaining it using a subnet calculator. The real good thing about this particular subnet calculator is that it shows you which bit is the network address and which bit is the host address.
NOW if you want to know the manual way, let me know. I also know that but I don't use it that much. It's kind of like knowing how to do multiplication without a calculator first. If you know how to do it then understanding how it works is that much easier.
You are correct about it does not matter which address you choose if you don't plan to connect to the internet, but....keep in mind that things change. I would stick with the private address range and not venture outside of that. Even if there is a 1 in a million chance that your network will connect to the internet, it has been my experience that 1 chance will always come back to haunt you. Always look forward when designing networks, it will help you or whoever takes over for you in the future.
Also good to take note of Jimbo's advise on numbering. Make ranges for all your equipment. This is my current configuration for my Dallas office...
Routers/switches = 172.16.4.1 - 20
Production Servers = 172.16.4.21 - 40
Management Servers = 172.16.4.41 - 60
Test Range = 172.16.4.61 - 80
Manual DHCP = 172.16.4.81 - 100
Auto DHCP = 172.16.4.101 - 5.139
Not Assigned = 172.16.5.140 - 5.254
Note that I don't use the entire range of addresses, not assigned range is for growth. This plan also works well for my smaller offices. Every piece of equipment has their range on the network, that way I can keep track of them much better and plan for any future expansion.
david e
*end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.*
Subnetting is basically playing around with the subnet mask. for example.
My Dallas office quickly ran out of IP Addresses using a regular Class B address of 172.16.4.0/255.255.255.0. I was able to increase the network of 254 addresses to 510 by adjusting the subnet mask to 255.255.254.0. (I was able to do this because I was in the private address range) What this essentially does is place one bit back to the host by taking it away from the network address. This one bit gave me a range of
172.16.4.1 to 172.16.5.254
Now to reverse that.....
I have a full class B address of 172.16.4.0 and I need at least two different subnets. by borrowing one bit from the host address I could split my class c into two different subnets using a subnet mask of 255.255.255.128. This would give me the range of
172.16.4.1 to 172.16.4.126 = Network 1
172.16.4.128 to 172.16.4.254 = Network 2
This is a down and dirty way of explaining it using a subnet calculator. The real good thing about this particular subnet calculator is that it shows you which bit is the network address and which bit is the host address.
NOW if you want to know the manual way, let me know. I also know that but I don't use it that much. It's kind of like knowing how to do multiplication without a calculator first. If you know how to do it then understanding how it works is that much easier.
You are correct about it does not matter which address you choose if you don't plan to connect to the internet, but....keep in mind that things change. I would stick with the private address range and not venture outside of that. Even if there is a 1 in a million chance that your network will connect to the internet, it has been my experience that 1 chance will always come back to haunt you. Always look forward when designing networks, it will help you or whoever takes over for you in the future.
Also good to take note of Jimbo's advise on numbering. Make ranges for all your equipment. This is my current configuration for my Dallas office...
Routers/switches = 172.16.4.1 - 20
Production Servers = 172.16.4.21 - 40
Management Servers = 172.16.4.41 - 60
Test Range = 172.16.4.61 - 80
Manual DHCP = 172.16.4.81 - 100
Auto DHCP = 172.16.4.101 - 5.139
Not Assigned = 172.16.5.140 - 5.254
Note that I don't use the entire range of addresses, not assigned range is for growth. This plan also works well for my smaller offices. Every piece of equipment has their range on the network, that way I can keep track of them much better and plan for any future expansion.
david e
*end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.*
If you are planning on blocking specifc computers from accessing the internet, you definitly want to block out IPs. For example, assign computers that will access the internet IPs from 192.168.1.20 - 192.168.1.50. Then for the systems that will not access the 'net; 192.168.1.51 - 192.168.1.100.
Reason behind this is that most routers allow you to block a specific range of IPs from accessing the 'net. If you have them spread out all over the place, then you'll have to type in each address that you want to restrict manually. Nate Gagne
nathan.gagne@verizon.net
AKA Nick Burns - Your Company's Computer Guy
"Would you like me to save your game of Minesweeper first?"
Like my post? Let me know it was helpful!
Reason behind this is that most routers allow you to block a specific range of IPs from accessing the 'net. If you have them spread out all over the place, then you'll have to type in each address that you want to restrict manually. Nate Gagne
nathan.gagne@verizon.net
AKA Nick Burns - Your Company's Computer Guy
"Would you like me to save your game of Minesweeper first?"
Like my post? Let me know it was helpful!
- Status
Similar threads
- Locked
- Question
- Locked
- Question