About ewellsie07

ewellsie07 · 03-07-2015

I've recently inherited a new client that currently sits on a flat network (192.168.2.0/24) spanning two physically separate buildings, connected by fiber.In order to reach compliance, I need to separate those two buildings logically, and be able to ...

ewellsie07 · 08-12-2010

One of our clients currently has an ASA 5510 on site, and they are using IPSEC VPN for their mobile users to connect.The VPN Subnet is 172.16.1.0/24.Internal network is 192.0.0.0/24. VPN Access works fine to the 192 subnet.Private network behind the ...

ewellsie07 · 10-14-2009

Basically, I want to know if this is possible with an ASA5510.I know in my experience, I've been able to do some internal subnet routing with the ASA's, but for some reason I can't get this one to work.Basically, I have an internal network of 192.0.0...

ewellsie07 · 08-19-2009

I have a client that is using an IPSec VPN, with the Cisco VPN Client. The clients connect fine, can map drives, use printers, get e-mail, etc. However, they have one server that is not able to respond back to the clients. According the server logs, ...

ewellsie07 · 02-27-2009

After upgrading a client from a PIX 501 to an ASA 5510, I'm having problems with the VPN and specifically the hostnames for the internal devices.Once active, the VPN on the ASA works perfectly fine by IP, but not by hostname.If I edit the hosts file ...

ewellsie07 · 04-02-2015

Thanks for the help.We did get it working, we had to introduce a new switch to segregate the fiber from the 1921 and the new ASA WAN interface, and then it was just a matter of the new NAT statements, and a new NAT statement to allow internet access ...

ewellsie07 · 03-29-2015

Those rules were added when I was trying the previous configuration, but are not there as it sits right now. These are the current NAT rules as it stands right now. global (inside) 1 interface global (outside) 1 interface nat (inside) 0 access-list...

ewellsie07 · 03-29-2015

I created a new VLAN, assigned one of the interfaces (0/7) and called the new interface "WAN". Set the security level to 100, same as the inside. It was assigned 192.168.5.1/24 and the router HWIC was assigned 192.168.5.254/24 which the fiber was plu...

ewellsie07 · 03-28-2015

Finally tried this today, with the additional interface on the ASA.Still no go. Seemed like the ASA had no problem seeing the router and pinging it, but couldn't get it to work the other way. From the ASA side, I was able to ping from internal hosts ...

ewellsie07 · 03-08-2015

That's what I thought. Thanks is for the help, I will give that a shot, seems like it should be fairly easy, just need to re-plan my config changes.

Member Since	‎02-27-2009 08:16 AM
Date Last Visited	‎11-05-2018 08:56 PM
Posts	37

User Statistics

User Activity

Cisco 1921 Routing/NAT Issue

Routing VPN clients to private network behind an ASA

ASA 5510 Routing Question

VPN Clients not getting response from internal server

Upgrade from PIX to ASA 5510. VPN not working properly

Thanks for the help.We did

Those rules were added when I

I created a new VLAN,

Finally tried this today,

That's what I thought. Thanks