You are having to deal with history, not connecting the lan to the firewall was a very basic way of ensuring no internet access - but this can also be achieved with firewall rules. Each side of the VPN needs to have a unique subnet. You are trying to use site Bs ip address range (subnet) at A which will not work. Would this work? If not, could some help me come up with a very temporary fix? In doing so, the thought is that X3 would be "physically" connecting location B to location A, and would thus allow traffic from X3 to communicate to the PROGRAM server. The site-to-site VPN's destination on SonicWALL A would be X3's subnet. Configure VLAN that uses the 172.18.30.X scheme on switches 1 and 2, and tag the appropriate ports Configure NIC 3 on PROGRAM server to have a static IP on the 172.18.30.X schemeĤ.
Configure VPN on SonicWALL B remote connection to be on the 172.18.23.X schemeģ.
Configure VPN on SonicWALL A to use X3's subnet as the destinationģ. Configure LAN port X2 on SonicWALL A to have an IP on the 172.18.30.X scheme, and plug it into switch 1Ģ. Devices at location B cannot communicate with devices at location A over the site-to-site VPN and vice-versaġ. SonicWALL router at location B has a site-to-site VPN to connect to location A SonicWALL router at location B is set to be on the 172.18.30.X scheme Devices at location B have statics on the 172.18.30.X scheme, and no gateways to Site-To-Site VPN to prevent the devices from accessing the internet Location B (off-site) has additional devices that need to communicate to PROGRAM server, and vice-versa PROGRAM runs on a server in building 2 at location A, and has a static IP on both the 172.18.23.X and 172.18.200.X schemes via NIC 1 and NIC 2 Devices that connect to PROGRAM have static IPs on the 172.23.200.X scheme, and no gateways to prevent the devices from accessing the internet
VLAN PROGRAM is used for devices that connect to a system called PROGRAM, VLAN PROGRAM uses the 172.18.23.X scheme, and is set as the default VLAN VLAN OFFICE is used for all office work and uses the 192.0.0.X scheme Two managed switches (1 & 2) are connected via fiber between building 1 and building 2 at location A, which has two VLANs configured (OFFICE & PROGRAM) Domain Controller at location A is a DHCP server for the 172.18.23.1 scheme and it connects to switch 2
SonicWALL router at location A is a DHCP server for the 192.0.0.1 scheme and it connects to switch 1 We have the green light to make it right, but they need this site-to-site VPN to work ASAP as it is an emergency that needed to be fixed "yesterday." As such, I am trying to come up with a band-aid to make it work for the short-term (7-14 days). Hey guys, I need some help wrapping my head around how to make this site-to-site VPN work for a new client of ours.įorewarning: Their network infrastructure is a giant mess.
0 kommentar(er)
