one building divided in half, two businesses, each has their own DSL line, modem, router, and 5 computers. they share a common server. group A has old phones while group B has new IP phones. how do i configure each router to keep all computers connected to the server while using their own DSL line?
Two DSL lines, One network
- Thread starter geseymour
- Start date
Solution
Configure the two DSL networks with separate IP networks (eg, 192.168.0.x and 192.168.1.x). COnfigure each router independently of the other, as they are not (and will not be) connected.
Put second LAN adapter in the server, one per network. If the server needs Internet access, configure only one of the LANs as "default gateway".
Put second LAN adapter in the server, one per network. If the server needs Internet access, configure only one of the LANs as "default gateway".
- May 29, 2013
- 37,367
- 3,288
- 156,790
A second network interface is the simplest implementation. You will have to static IP those interfaces and determine WHICH of the two paths the server should have DSL access. The one without DSL access should not have a gateway.
thank you for the quick response as i have been researching on/off over the last few weeks to find the best cost effective solution. originally, all 10 computers were on the same network tied to the same patch panel, switch, server, router, modem, and DSL line. the server does have internet access from group A services and is doing DHCP. a month or so ago group B decided to get new phones for just their business. the telephone company dropped in a new DSL line, switch, router, and modem for them. they connected the new ip phones and computers into the new equipment and all worked fine except group B needs access to the common server which went away by connecting to the new equipment. the phone company's solution was to leave the ip phones connected to the new equipment and connect the computers back to the old network. that works but not what they desire. we want to get group B's phones and computers on their own network, DSL line but still have access to the data/file server. the current server has two nic ports with only one configured. so i need to connect the ip phones and computers to the switch in group B's building so it is tied to their equipment which has a different ip address configuration than group A. then connect via CAT5 group B switch to group A patch panel straight to the server nic port#2 (bypassing group A switch). then i need to configure nic port#2 with a static ip address in the scope of group B's configuration. does that seem correct? what about the computers in group B, do they need to be static ip addresses? does the router in group B need to have DHCP turned off? thanks again for your assistance.
- May 29, 2013
- 37,367
- 3,288
- 156,790
The group B computers can be DHCP from the router. You don't want the server NIC in Group B address space to be DHCP because it would pick up Group B gateway.
The Group B router doesn't need to have DHCP turned off, but you need to be sure that the server is not attempting to DHCP in Group B range.
The Group B router doesn't need to have DHCP turned off, but you need to be sure that the server is not attempting to DHCP in Group B range.
from your earlier response: "You will have to static IP those interfaces" - meaning the computers and ip phones in group B?
"determine WHICH of the two paths the server should have DSL access" - i will leave the server with DSL access as is from group A.
"don't want the server NIC in Group B address space to be DHCP" - so make the server NIC#2 for group B is static, in the range of the router from group B, and without a gateway address?
"but you need to be sure that the server is not attempting to DHCP in Group B range" - meaning the server should only DHCP for group A... how do i make sure the server will NOT perform DHCP in that group B?
from my earlier post " then connect via CAT5 wire group B switch to group A patch panel straight to the server nic port#2 (bypassing group A switch), is that correct?
Again... thanks for your expertise!
- May 29, 2013
- 37,367
- 3,288
- 156,790
My statement on static IPs was strictly for the interfaces on the server. It is always preferable to have them static.
Correct.
IMO, correct -- Let the router for group B handle it.
I would have one cable from the server to the group A switch (or patch then switch) and a cable from the server to the group B switch (or patch then switch) .
TRENDING THREADS
-
-
-
News Nintendo obliterates 8,535 Yuzu repos — Nintendo's most effective DMCA takedown campaign in years- Started by Admin
- Replies: 29
-
-
News AMD's gaming revenue nosedives 48%, not expected to recover until 2025
- Started by Admin
- Replies: 38
Latest posts
-
-
Question I don't know how to connect front panel connectors to motherboard.
- Latest: josh44361431577
-
-
-
Facebook
Twitter
Instagram