Bridging 2 separate networks, same location
Posted on 2011-09-10
I feel like I should know this, but I don't.
I have 2 separate networks in the same building.
Each has its own internet connection with static IP and an Untangle Server running as a router. Each has its own SBS2008 server running DHCP, DNS, Exchange, IIS web app, SQL database, etc..
One network is 192.168.0.x and the other is 192.168.10.x.
We need the 2 networks to communicate with each other quickly.
I have a site-to-site VPN with the Untangle Servers' OpenVPN. It works, but running RDP or terminal services across the network is painfully slow. I'm getting lots of complaints.
Also we have an IP phone system on the 10.x network, and if phone is plugged into the 0.x network, the phone "cuts out". Right now all phones are plugged into the 10.x network, but that requires 2 ports for every desk that should only be on the 0.x network.
I'm assuming most of the problems are due to the slow internet connections, a 2mbps DSL on each side.
We have a 48 port PoE switch and a 24 port gigabit switch on each network. We're running out of ports on the PoE switch on the 10.x network, since both sides have their phones connecting through that switch.
Since both networks are in the same building (all cables meet in the same server room), shouldn't I be able to use some kind of "bridge" and scrap the site-to-site VPN? It seems to me I should be able to connect these 2 networks at gigabit speed instead of 2mbps tops.
Also, are there some unintended consequences to bridging the networks? I do not want a DHCP, DNS, or Exchange nightmare.