How to connect 3 outside connections and route them properly

July 19, 2012 at 07:37:27
Specs: Windows 7
We are planning 3 Internet Connections into our building. 1 will be for actual Internet traffic, 2nd for Voip phone system, and 3rd for internal network for Active Directory...etc. Oh the AD servers are controlled by another business so technically this line is still considered and outside line and is a T1. What I need to know is how best to make this all work so that our internet phones use the VOIP system, computers can log into the domain and access that network but use the Internet network for actual internet traffic? We were considering a series of managed switches and creating 3 VLAN's but I'm thinking we instead need a new router that all 3 networks connect to and dishes out DHCP to computers and phones. An example network is below.

192.168.1.x ----> Internet (all computers use for internet traffic)
172.10.10.x ----> VOIP (All physical and software phones use this network)
10.10.10.x -----> Connection to external company that controls our network and has domain controllers, mainframe...etc.

Thanks in advance for taking time to help.

See More: How to connect 3 outside connections and route them properly

Report •

July 19, 2012 at 07:53:38
I would design this as three descrete networks.

Converging them and doing vlans, as fun as that is, still becomes a bottleneck [they all use the same switch processor] in throughput and is more difficult to troubleshoot.

As descrete networks if your internet goes down you still have phones for example.

Always follow the KISS principle.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's

Report •

July 19, 2012 at 08:05:22
Is there a reason not to get internet through the 10.10.10.x network? If whomever controlled the VPN connection you have were to provide you with internet connectivity it woudl greatly simplify this scenario. Then all you would need is a separate external connection for the VoIP traffic which could easily be separated and sent in the correct direction using VLAN's and a router.

You would have one VLAN for data, one for VoIP. The data VLAN would encompass both intersite domain traffic as well as external/internet traffic and both would be dealt with by your AD DNS server.

The problem I see with what you're asking is, how do you (locally) separate the traffic coming out of a single PC into "AD domain traffic" as versus "Internet traffic"?

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***

Report •
Related Solutions

Ask Question