About shawnreis

shawnreis · ‎08-28-2008

We have an ASA 551o that we use for VPN, both Client and PTP. I noticed a problem with one of the NAT settings on our OUTSIDE interface. The netmask is 255.255.255.218 and should be 128. I can't change it on ASDM as it is grayed out in the NAT settings and I can't find anything about how to change it using the CLI. Hopefully someone can point me in the right direction. Thank you. Moe

shawnreis · ‎08-05-2008

I am having problems getting the LDAP authorization to work. None of the instructions I find seem to coincide with my version of ASDM 5.0(7) and ASA 7.0(7). SO if anyone has the right instructions for these version can you send me a link? I get as far of testing it and it fails. When I test it asks for a user name but never a password. so I am not sure what I am doing wrong. Any help appreciated.

shawnreis · ‎04-09-2008

And as always: Thanks for your help and patience.

shawnreis · ‎04-09-2008

Yes it is. I can SSH into it from anywhere on my network just not while connected to the VPN. I can Telnet to it and ping it while using VPN, just not SSH.

shawnreis · ‎04-09-2008

When I setup my split tunneling I made a standard ACL and that just says Permit my network. (and is working fine) Do I need a line just for my Inside interface?

shawnreis · ‎04-09-2008

I tried that with no luck. Just to make sure, I removed the management access and readded: ASA(config)# management-access inside-vpn Please remove the management access before configure a new one ASA(config)# no management-access inside-vpn ASA(config)# management-access inside-vpn I also have the SSH setup: ASA# show ssh Timeout: 5 minutes Versions allowed: 1 and 2 192.168.192.0 255.255.255.0 inside-vpn xx.xx.32.0 255.255.255.128 inside-vpn I know the SSH works since I have used it.(while not being connected via VPN) I have also set my IP address to match one in our VPN DHCP range and from there I can SSH into the Device. Just not directly while VPN'd in. Although while connected to the VPN I can ssh into a server and then into the device. I would rather not have to do that. Thanks Moe

shawnreis · ‎04-09-2008

We need to be able to access the Device via SSH while connected VIA VPN. I have added it to the management access: pix(config)#management-access inside And it says I need to add the correct access. I have SSH added to my ACL on the outside interface coming in and can SSH into servers on the inside. So do I also need to add ac ACL to the inside Interface to allow this ssh access to the Device? Thanks Moe

shawnreis · ‎04-09-2008

Actually my DHCP range was on its on subnet. I have resolved this issue and thanks for your help. I was creating the Split Tunneling and creating the ACL/ACE for it but was not actually enabling it on any VPN group.

shawnreis · ‎04-04-2008

Tried split tunnel and got the same results.

shawnreis · ‎04-04-2008

Our current IP pool is a portion of our internal network X.X.32.100 x.x.32.127 (fully routable not 192, 172, 10.10 address. ) does that matter?

shawnreis · ‎04-04-2008

I love the quick responses around here.. I didn't have time to grab a coffee. So for the nat (outside) XXXXXXXX Would it be my internal network subnet?

shawnreis · ‎04-04-2008

Thanks for everyones help so far as I am very close to my goals but now I am stuck on something else. I have internet access but when I connect to my network via VPN I can not get to the internet (via http/ping etc) I get Address translation but no connection. I can connect to everything internally just fine. I have tried with split tunneling or without, neither help. I have a line in my ACL permitting http and can HTTP into a machine on our internal network. Any suggestions, anything more useful to post for assistance? Thanks to all for your help. Newbie Moe.

shawnreis · ‎04-01-2008

That worked like a Charm. Thank you.

shawnreis · ‎03-26-2008

I currently only have 1 ACL in place. Should I have another one?

shawnreis · ‎03-25-2008

Forgive me if this get confusing. I have a new ASA 5510, I have set it up for VPN use. I can vpn via IPSEC and connect to 2 of my subnets .0 and .64 (we have 4 subnets in our range) I can ping, http(s), connect to shares, SSH etc. I am using the ACL from our outgoing VPN box so I nothing there should be wrong. The problem I am having is getting to our lab network which is on the .128 subnet. I can't ping, connect, http anything. Is there some special routing I need to do in order for people who VPN in to see that subnet? (For testing purposes the ASA is behind the firewall and connected directly to .0 subnet so I know it's not the firewall and everything else on that subnet can see our lab.) Thanks for helping out the new guy. Shawn

Date Registered	‎03-18-2008 12:08 PM
Date Last Visited	‎08-18-2017 03:53 AM
Total Messages Posted	23

How to make a change to a Nat entry.

LDAP authorization for VPN

Re: ASA 5510 Accessing Inside Interface...

Re: ASA 5510 Accessing Inside Interface...

Re: ASA 5510 Accessing Inside Interface...

Re: ASA 5510 Accessing Inside Interface...

ASA 5510 Accessing Inside Interface Whi...

Re: ASA 5510 VPN, no internet

Re: ASA 5510 VPN, no internet

Re: ASA 5510 VPN, no internet

Re: ASA 5510 VPN, no internet

ASA 5510 VPN, no internet

Re: ASA 5510 Routing Question.

Re: ASA 5510 Routing Question.

ASA 5510 Routing Question.