Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi All,This is a weird problem I am hoping you can help with.I have a Cisco 867 which is connected to my ADSL2+ line and all the clients connect to the Wireless LAN on the 867.Just recently, I have connected some devices that are DLNA compliant. I sp...
Hi All,We have just started moving over to Client SSL VPN Connections. We have this working really well and all our users are able to connect using the AnyConnect client and we are happy it is setup the way we want it.We decided we would now go to th...
Hi All,I have a scenario I have been trying to work out how to do and just cannot work out. I am sure someone on here with a lot more experience then me will answer this very easily.We have an ASA5510 running version 8.25. This is in our central offi...
Hi All,We currently have a central hub using an ASA5510 and then a few site-to-site VPN connections to our support staff homes. The devices at the homes are Cisco routers.We were running version 8.25 on the ASA and all was working fine. We recently u...
Hi All,I am attempting to do setup a site-to-site VPN. Generaly it is working fine but I have one problem that I cannot seem to solve.Basically, I have a Cisco 831 Broadband router at the main office acting as an Easy VPN Server. At a remote locati...
The solution to this for anyone that's interested was to create a self-signed certificate on the ASA and then install it into the Laptop's Machine Trusted Roots store.It would be nice for Cisco to document this. SBL will not work without a trusted ce...
Many thanks for all your help. The commands that worked in the end were:access-list VPN-POLICY-NAT permit ip 172.16.148.0 255.255.252.0 10.110.18.0 255.255.255.0global (outside) 11 10.110.131.200 netmask 255.255.255.255nat (outside) 11 access-list VP...
Many thanks for that but I have a question.Will that only NAT if the request is destined for the 10.110.18.0 subnet. There are actually other VPNs connected to the firewall where it needs to keep it's original IP address of 172.16.148.0. The only ti...
That bug is exactly what we are getting. I tried what you said and it worked perfectly. I then deleted the extra NAT rule and changed the NAT statement for the VPN networks to route-lookup and that also worked.Do you happen to know if there could be ...
Many thanks for your reply. I have just tried changign it and it didn't make any difference. I changed them all to (inside,outside) instead of any but I still cannot ping the inside interface or telnet to it.
