How do I configure 2 networks behind one Sonicwall
Posted on 2015-02-07
I'm looking for a little guidance on how to relocate some servers from our sister company to our office and it's a little outside my wheelhouse.
Our corporate office is in Las Vegas. Subnet 192.168.x.x/20
We purchased a company in San Diego. Subnet 10.0.10.x/24
Both offices are currently connected via Sonicwall VPN.
Both Offices are on their own domains.
Here's what needs to be accomplished:
We are relocating Exchange, SQL server, Web Server, One Domain Controller, Terminal Server, a Back-office Application server and several support servers from the SD to the LV office.
We are leaving a Domain controller/file server and a print server onsite in SD.
The LV users need to access the Back-office server across the internal network.
The SD users will access the Back-office server using the terminal server.
I would like to place the the SD servers on their own network in my LV data center.
The relocated AD server will need to communicate with the AD server left in the SD office.
I have a spare static IP i can use for easier port forwarding.
The LV office has a sonicwall NSA 240 running SonicOS Enhanced 126.96.36.199-1o
What is the best way to network the relocated servers?
Should I put them on their own network, with their own public ip using my existing Sonicwall? (This seems to the simplest way to manage the port forwarding)
Can two of the unassigned Sonicwall ports be used as WAN2 and LAN2?
If I do use an unassigned port as WAN2, do I need to setup a new VPN tunnel between that WAN port and the SD office?
I looked into Portshield, but that seems geared toward combining two separate interfaces into one virtual interface.
Thanks for the suggestions,