Software and Applications

[issilliuc]

Hey guys I curretly am struggling with a network of 23 computers.

I devided the network in 2 , one part with dhcp in iprange 192.168.1.0 and subnet 255.255.255.0  and the other in 10.0.0.1 subnet 255.0.0.0 

Basicly it's simple. Get 2 dhcp servers. 2 switches and 1 router. Put the first Dhcp on switch 1 and the first 12 computers. 

configurate the Dhcp server to spread out 192.168.1.0 ip addresses and Give the router port to switch 1 the 192.168.1.1 ip.

than connect switch 2 on the 2nd port of the router. Add the dhcp and computers. configurate the dhcp to spreadout 10.0.0.0 ip's.

And give port 2 of the router ip addres 10.0.0.1.

Now baiscly after doing all that my network works. I can ping from network 1 to a computer on network 2 and the other way arround..

so I was wondering since I don't know how..

Is it possible to use just 1 dhcp for both subnets ? 

[ZeroGuardian]

Depends on the equipment. If your using something like a Cisco router yeah you can setup seperated DHCP ranges for different ports or so forth. But to be honest, when dealing with that many computers your probably better off just setting up static addresses for all the computer. And if all 23 need to be able to communicate why divide up the DHCP addresses in the first place?

Also, Why are you using actual DHCP servers? You can get networking equipment that can handle all those requirements.

[jwhx]

EEeewwww. DHCP.

Handy for home but once you get over 10 machines, go static. It makes things way less confusing.

[dryfter_09_19]

Why the hate for DHCP?

Who pings IP addresses anymore? If you know the computer name (should be pasted on a monitor or computer in a business setting) just ping the computers name.

*Disclaimer: I manage a network of 15-20 computers. I also interact with A LOT of banks, schools, and other businesses.  A VERY few people (in my area) use statically assigned IP's for anything other than servers.*

I haven't statically assigned IP's in a LONG time (minus servers).

Edit: Meant to include this in my original post.

Whats the point of splitting the two networks? Another way you might do it is to have your router control one set of IP's, then your server the second set. Though I'm not sure how you would manage that. DD-WRT might have something that would help with that. If you're looking at getting ride of a server, you could also go the virtualization route. One computer running 2 VM DHCP's with two nic cards. Connect them like before and that should give you what you want to do.

As for one DHCP server giving out two sets of address's... The only way I can think of would be some sort of mac address reservation. If a comp with a specific mac (in side 2) calls for an address it recogninzes it and gives it what you want. It might not work like that though. Just a thought.

[Transco901]

^ In our test lab, we have static IP addresses.  Then each test box has an lmhosts file which maps computer name to IP Address. 

This works well (at least in Windows).

[dryfter_09_19]

---

Transco901 wrote:

^ In our test lab, we have static IP addresses.  Then each test box has an lmhosts file which maps computer name to IP Address. 

This works well (at least in Windows).

---

So, in a nut shell, each computer is functioning as it's own "WINS" server, instead of the router doing it.

Whats the point? It sounds like more of a pain than it's worth. I could see doing that if your router was getting "overloaded" or something of the sort. It would take a little strain off the router.

[meorah]

---

issilliuc wrote:

Hey guys I curretly am struggling with a network of 23 computers.

I devided the network in 2 , one part with dhcp in iprange 192.168.1.0 and subnet 255.255.255.0  and the other in 10.0.0.1 subnet 255.0.0.0 

Basicly it's simple. Get 2 dhcp servers. 2 switches and 1 router. Put the first Dhcp on switch 1 and the first 12 computers. 

configurate the Dhcp server to spread out 192.168.1.0 ip addresses and Give the router port to switch 1 the 192.168.1.1 ip.

than connect switch 2 on the 2nd port of the router. Add the dhcp and computers. configurate the dhcp to spreadout 10.0.0.0 ip's.

And give port 2 of the router ip addres 10.0.0.1.

Now baiscly after doing all that my network works. I can ping from network 1 to a computer on network 2 and the other way arround..

so I was wondering since I don't know how..

Is it possible to use just 1 dhcp for both subnets ? 

---

What goal are you trying to accomplish by dividing such a small network?  You could split it into 23 networks for all I care, but without understanding what you're doing its all pointless.

To answer your last question, yes you can use one DHCP server and setup multiple scopes for however many subnets you want.

[Transco901]

---

dryfter_09_19 wrote:

---

Transco901 wrote:

^ In our test lab, we have static IP addresses.  Then each test box has an lmhosts file which maps computer name to IP Address. 

This works well (at least in Windows).

---

So, in a nut shell, each computer is functioning as it's own "WINS" server, instead of the router doing it.

Whats the point? It sounds like more of a pain than it's worth. I could see doing that if your router was getting "overloaded" or something of the sort. It would take a little strain off the router.

---

We are constantly re-imaging (ghosting) our test boxes back to a base state.  Sometimes, we rename the test boxes too.  Bottomline, it was not uncommon to ping a computer by name, then get back the wrong IP address.  Our current has eliminated these problems.  I think Windows + Networking in a dynamic enviroment like the one we have in our test lab is asking for trouble. 

[issilliuc]

hey sorry for my late late late reply.

Well I am not planning to use it on a network.

I was just currious. 

I'm currently just configurating many sort's of network's and protocols in cisco packet tracer * virtual networks* 

Just to learn more. 

And yes Static Ip's is a easier but a lot more work.

I prefer Dhcp but it isn't easy to ping from 1 subent to another. I have heard it's possible.. but how I do not.. I'm just curious how it's possible and how to configurate it. 

[ZeroGuardian]

Well with Cisco equipment (or any business class managed solution) its actually very easy to ping from one subnet to another. All that is required is a static route programmed into the devices.

So say you have 10 computer plugged into a switch. And 10 other computers plugged into a seperate switch. And both switches are plugged into a cisco router. Well then you would configure the routers interfaces with static routes connecting the two together.

So basically you have 192.168.1.0/28 subnet on eth0 interface and a 192.168.1.16/28 subnet on eth1. All you would have to do is add a static route for eth1's subnet and eth0's. Now of course eth0's IP would be 192.168.1.1 and eth1's IP would be 192.168.1.17. So you would add this to the configuration of the router.

IP route 192.168.1.0 255.255.255.240 192.168.1.1

IP route 192.168.1.16 255.255.255.240 192.168.1.17

That tells the router anything trying to communicate with devices in subnet 192.168.1.0/28 needs to be sent to eth0 and any communication for subnet 192.168.1.16/28 needs to be sent to eth1.

The only thing you have to be careful with is making sure you don't create subnets that cross each other. It will basically kill your network and confuse your router.

I'm cisco certified btw. So feel free to ask me any questions you might have. And while DHCP is much easier... the larger the network becomes the more problems it causes. If your planning on doing anything with networking... you better get used to liking static IPs. They will make you life MUCH easier in the long run.