DHCP Issue

[jagsrao]

Hi,
We have a Windows2003 Server acting as a DHCP Server with the address 192.168.0.1 to 190.168.0.255. The same is also acting as a DNS Sever for IPs 192.168.1.1 to 192.168.1.255. We were running out of IP for DHCP. Hence we created another scope 192.168.2.x in DHCP.
When we connected another PC in the DHCP, it did not get 2.x address. We added a superscope. Even then it did not work. We then added the server as a router adding 192.168.2.1 as an additional IP. We then added 192.168.2.3 to the PC. Now, it was communicating with 2.1 but not with other IPs in the other subnets (viz 192.168.0.x and 192.168.1.x)
At the server, it is not able to ping to 192.168.2.1 which is an additional IP of its interface.
Where are we going wrong ?

Thanks

Regards

Jagdish

 

[Davetoo]

What is in the range 192.168.1.x? What are your subnet masks for each range?

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

 

[jagsrao]

The range is 255 and subnet mask in each is 255.255.254.0

 

[pgaliardo]

Confused about your setup. Are you saying you have 3 different subnets now? Are the subnets connected by routers? It seems that if you are running out of IP Addresses for the 192.168.0.x subnet, it would be easier to just change your mask to 255.255.0.0. This should give you more than enough addresses.

 

[Davetoo]

Don't create a new scope, instead, extend your existing scope. A much better solution in the long run.

Look at what you think you'll need over the next five years, then double that and extend your scope to cover that range.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

 

[cajuntank]

You also might want to look at a Layer3 switch to address routable vlans so that you can keep your broadcast down. When you need to add more address space, just create another /24 subnet and assign it to a new vlan interface. You will of course have to make those vlan's routable in the L3 switch, and you will have to get those L2 VLAN(s) down to the desktop in some form or fasion.
Just a thought.

 

[jagsrao]

Hi,

Thanks for the inputs.

Currently we are unable to invest on L3 Switch. Hence, we may have to postpone the purchase

I cannot extend the existing scope without deleting it and creating a fresh one. But this is risky since the subnet will be down for sometime. This is not acceptable by my users

 

[Davetoo]

The subnet will not go down. The DHCP server may not respond for the few seconds it takes to create the new scope, so if you're worried about that set your expiration to a few days and do it in the middle of the night.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.