• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 424
  • Last Modified:

How to Link to different network together

Currently we have 2 different network in our company  ,One network is at ground floor and another network is at second floor ,this two network have own internet connection and server .Now we need to connect this two network together but VPN is not the choice because we don't have any facility to do that ,our router in for both network is very basic also.

More importing now the LAN IP for both network also is 192.168.1.0/24 if we connect both network together using switch two switch i think we will facing the issue.Actually we already lay one cable from second floor to group but no idea where we should plug to also.Please advice what is the proper and simple way to do this task.
0
YaYangTeah
Asked:
YaYangTeah
  • 3
  • 2
  • 2
2 Solutions
 
n2fcCommented:
Many choices to do this:

1) Connect the routers using ethernet cable and DISABLE the router functionality in one of the routers... This effectively turns that router into just a hub (switch) and delegates the routing function to the other router...

2) Replace one of the routers with an ethernet switch.  This makes the network previously served by the old router into an extension of the other network merely by connecting to the other network.

Note: Most NEWER routers & switches have "auto-detection" to determine if they are connecting to a PC or another switch... If your equipment doesn't have this, it will either have a "crossover" port or you will need to use a "crossover cable" to connect between the router and the replacement switch... If you need more info on this aspect, please let me know!
0
 
YaYangTeahAuthor Commented:
We still need to maintain their own internet connection
0
 
KimputerCommented:
Besides physically connecting the networks (see post above), you have to map out your IP numbers already for both floors, and decide how to handle this. Each floor keeps it's own internet? If so, fix IP numbers (for ALL clients/printers/etc) from 192.168.1.1-192.168.1.128 for one floor, and 192.168.1.129-192.168.1.255 for the other (no DHCP as one floor has it's own gateway/dns, and the other another gateway/dns).
If you want to keep one internet connection, you can enable one DHCP router only, and make sure previous fixed IP numbers from both floors don't overlap.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
YaYangTeahAuthor Commented:
Both router also LAN IP also is 192.168.1.1 the PC know how to go to the correct gateway  ?
0
 
YaYangTeahAuthor Commented:
How about we need to maintain thier DHCP and DNS  and change thier one of the network to 192.168.2.0/24 ?
0
 
KimputerCommented:
Because you CONNECT the two networks together, having two DHCP/DNS servers will interfere. Sometimes floor1 will get IP numbers from floor 2, and vice versa.
0
 
n2fcCommented:
Kimputer is correct...  In order to accomplish what you are trying to do will require another router to handle the inter-floor traffic.

Use 192.168.1.0/24 for Floor 1, 192.168.2.0/24 for Floor 2...
Then you will need an additional router, connected to both floors, to handle routing between the floors!

These are independent networks; you can connect them to each other like any other network, using an ordinary router!

Let’s call it the “shared” router. The tricky part is properly configuring it.

You connect the WAN of the shared router to a LAN port on the router of network 192.168.1.x, and connect a LAN port of the shared router to a LAN port on the router of network 192.168.2.x.

[192.168.1.1](lan)<-- wire -->(wan)[shared router](lan)<-- wire -->(lan)[192.168.2.1]

So now you have a physical path between the networks. The shared router acts as a gateway between them. The problem is that clients of either network don’t know that this gateway exists. By default, any network whose whereabouts are unknown will result in the client passing the request to its default gateway (usually its own router). But the router doesn't know where the other network is either. So you need to add static routes to each network’s router so it can locate the other network, using either the WAN or LAN IP of the shared router, as appropriate. Also disable the shared router's DHCP server (we're not using it to support its own local network, it's ONLY a gateway). Finally, it works a lot smoother and easier if you drop the firewall on the shared router and disable NAT.

It sounds more complicated than it really is. All you're really doing is defining a new gateway and using a third router to support it, and updating each network’s router so clients of that network can find that gateway and thus access clients of the other network.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now