Networks

Ask something
Discussion Locked

connecting two networks

0 helpful
9 replies

by homer simpson instructor at large 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a 192.168.1.x network connected via router to the internet. We have just added on to our IT structure and now have grown beyond the 254 limit of this address. I have configured a win2k machine as a router which leads to a 10.x.x.x network. are there any rules about hooking two private networks together. I seem to be having one DNS issue on my 10.x.x.x network. it can't get the www location right for the company external webpage which is on the 192.168.1.x network. Any suggestions?

9 replies

by j.a.lawrence

You'll probably have to establish a persistent, static route between the two subnets so that A knows how to get to B.

Check out the Route command( route /? at the command prompt). The gateway will be the IP address on your router that points to the other subnet.

by bbaltas

Homer,

This should be a fairly simple installation. One thing that might be a problem is your routing protocol. You are probably using RIP. RIP version 1 is a classful routing protocol - meaning it is unaware of subnet masks. If your running this protocol and you have subnetted your 10.x.x.x network with something other than a 255.0.0.0 mask this is your problem. To fix this try installing RIP version 2 or OSPF (if the server will do OSPF).

Other than that, your router will have to know about both routes, and this router should also have a gateway of last resort. This gateway will point to the router that directs your internet traffic. You may also have to define routes in your server.

Good luck
Bill Baltas

by timwalsh

There is a very simple solution to your problem if your only limitation is the 254 host limit of the 192.168.1.x subnet. The entire 192.168.x.x subnet is considered available for each private network. Therefore, if you just change your subnet maskfrom 255.255.255.0 to 255.255.0.0 you move from 254 available hosts to approximately 65,000 available hosts (255 X 255). This would be much easier that going the multiple subnet route. If you want to allow for future expansion beyond one subnet, change the 3rd octet to a valid mask other than 0.

Hope this helps.

by achen2002

If you can change the 10.x.x.x network to 192.168.x.x, the third answer is good, just give each subnet 255.255.0.0 as netmask.

If you DO NOT want to change it, you much create static route in each subnet, assuming the gateway PC in 192.168.2.x isPC A and the gateway in 10.x.x.x is PC B, do the following.

-- You have to give PC A an address under 10.x.x.x, assuming the IP in it's own nsubnet is 192.168.2.A

-- Vise versa, give PC B an address under 192.168.2.x, assuming the IP in its own network is 10.x.x.B

-- In PC A, add route like this:
route add 10.0.0.0 mask 255.0.0.0 192.168.2.A

-- In PC B, add route like this:
route add 192.168.2.0 mask 255.255.255.0 10.x.x.B

-- Confirm those two computers are gateway in each network

-- Now you can ping between two computers in twoo network, www browing will be no problem.

This discussion is closed to new replies.