2 different IP subnets need to be merged to be one network on W2K server?

[Lord Demios]

I have two IP subnets that need to be merged under DHCP as one network. That is easy enough to do in W2K with a SuperScope, but the problem is that they have different subnet masks also, so if a machine gets an IP from subnet B, it can't ping, or see any machines with IP from A. Do any of you guys know how to fix this, or if it can be done. I have 32 IP's on one subnet, and 64 on another and I just need to be able to make my DHCP server serve them out, without make machines unable to see each other.

Thanks for the help

LD

 

[Damaged]

Since you're using DHCP why don't you just renumber everything to be in the same subnet? Make the change, release, renew, voila!

There are other alternatives. You could just widen the mask that you're currently using. Say instead of 255.255.255.128 you could open it up to 255.255.255.0. Or whatever's appropriate.

Lastly, you could just write static routes for the other subnets.

For example, on my home network I use a Linux box as a router. I have a internal network of 192.168.1.0/24 (aka 255.255.255.0 netmask).

The problem tends to lie in that I have a default gateway of 192.168.1.1 which is my internal interface. It in turn routes everything to the outside interface. The problem arises if my DSL line or my outside interface fails. Things will eventually route over to the 192.168.1.1, but it takes some time for it to give up on that and fallback. So I added a static route that says everything for 192.168.1.0 goes through 192.168.1.1 first.

In Windows the statement would be written as:

route ADD 192.168.1.0 (the desitnation) MASK 255.255.255.0 ( the subnet mask) 192.168.1.1 (the gateway) METRIC (optional)

So the whole statement looks like:

route ADD 192.168.1.1 MASK 255.255.255.0 192.168.1. METRIC 1

You could do something similar for your different subnets.

Personally I would just make the mask big enough in your DHCP software to assign out the number of IPs that you need, release, renew, and be done with it. A much more scalable solution in the long run. It's also less maintenance and easier to troubleshoot. Don't get me wrong, there's good resasons to subnet (reduce broadcast storms, more control, etc), but in given the explanation you've provided I don't see why you would want to keep this arrangement.

 

[Lord Demios]

I don't want to keep this arrangement, but these IP's are not 192.168's they are real IP's. The problem is @work(at home for businesses) gave us the first set, (Which is now used) and gave us this second set on a different subnet with different masks. If I use any old mask that I want, I will be trampling on other people's IP's. Can I make W2K server use these IP's as one network, AND not have problems. The server dishes them out just fine (both subnets) but if someone needs to connect to a machine on the other subnet, they won't see the machine at all.

Thanks for all of the help.

LD

PS My home network runs on the 192.168 with a linux firewall/router, and cable hooked to it. I love that setup, and WISH I could get work to do it, but they won't.

 

[CTR]

How 'bout putting in 2 NIC's? Then you've got more control over the DHCP requests/replies.

 

[Damaged]

You're going to have to route the subnets then. You can try using a Windows box to do this if everything comes into it, and it sounds like it does, or, you can get a simple ethernet to ethernet router to accomplish the task. Either one will work.

Welcome to the world of networking. You've just been assimilated.