02-22-2016 10:16 AM - edited 03-05-2019 03:24 AM
I have been assigned the task of combining two separate networks into one or at least particularly. Currently one of our offsite locations are moving their servers to our location. A partial advantage is that both locations uses ASA. The servers that are moving in-house will have their own subnet range and domain controllers. We are only using our ASA.
My first concern is that of the subnet. Currently everything on our ASA is setup to the 192.168.0.x with the subnet mask of 255.255.255.248. Their range is 192.168.100.x with the subnet mask of 255.255.255.0. Will I need to make changes to our ASA subnet mask to include their range?
Second, both locations are using LDAP authentication. Will I need to create a separate VPN policy in order for them to continue to use their LDAP? I am assuming yes.
Is there any surprises or gotchas I need to be aware of? Thanks
Solved! Go to Solution.
02-29-2016 10:41 AM
No. You'll need to obfuscate any important information. Search and replace is good for this ...
02-29-2016 02:57 PM
Attached. Hopefully I removed anything confidential information
02-29-2016 02:57 PM
There are quite a few VPNs in that config. Which one are you using for this? WrightsVPN?
02-29-2016 03:04 PM
WrightsVPN is for our primary network (Ethernet 0/1) Licensing (LicenseStreamVPN) is the one I just added that should be talking to Ethernet 0/2. At the moment, it does not seem to be able to do so.
As a refresher. Ethernet 0/2 is the added network using the 192.168.100.x subnet range. The primary network, the original active network on Ethernet 0/1 is 192.168.0.x (actually all of the way up to 192.168.8.x, I believe). The server I am attempting to talk to has a static IP of 192.168.1.123 (255.255.255.0)
02-29-2016 03:12 PM
Lets start by fixing the NAT. Add:
access-list inside-ls_nat0_outbound extended permit ip any 192.168.100.0 255.255.255.0
nat (inside-ls) 0 access-list inside-ls_nat0_outbound
02-29-2016 03:19 PM
That solved it. Thanks a million.
03-07-2016 11:00 AM
I am hopeful that you will see this even after marking the solution solved. I ran into a different issue but related. If I need to separate this request, so you get credit, please let me know.
I need to be able to access web sites that are connected to the Ethernet 0/2 from the internal network (Ethernet 0/1) as if they are local. Currently, if I attempt to access the web server via the DNS (external DNS), the page cannot be found. I am guessing the ASA is treating this like a loopback or something of that nature. I know the issue is not DNS as I cannot access using the IP address while internal. I can via an external source. Thoughts?
03-07-2016 11:05 AM
Its not about a credit issue; but it would be great if you could post it as a separate issue with your current config. I remember this thread now, but it is quite long to read back over to extract out the important bits.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide