The 192.168.222.0 subnet was just used in a "test lab" setup. The second configuration I posted is the one that is in use now. The IP configurations on the workstations are valid, I can ping the directly connected ASA interface as well as surf the 'net. There are no static routes installed on...
Yep, in fact I had both subnets connected and all the computers could get on the net. I just reduced it to eliminate any routing issues. I've disabled the Windows firewall on both computers(it's the only one installed).
When I try a TFTP get between the subnets(in either direction) the TFTPD...
Aw snap! I changed one of the subnets and the ISP config on the above scenario and now it doesn't work.
I reduced the setup to just two computers with one connected to student and the other connected to student2. Both had a static IP and their gateways were pointed at the respective ASA...
Thanks unclerico!
I had messed around with identity NAT before but I don't think I hit the right incantation. Both of your suggestions work and I'm using option 1 currently.
You had the IP's in option 2 transposed, which is understandable. It should be:
static (student1,student2)...
I'm new to the ASA and can't figure out how to communicate between two inside interfaces with the same security level.
I have two subnets directly connected to the ASA along with a connection to an ISP. So far I have been able to get both subnets connected to the Internet(with PAT) but I can't...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.