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
I've upgraded from a Cisco ASA 5505 to a 5506X, and as such have moved up to ASA 9.5
Because of this I'm a bit stuck on how to implement VPN. I've followed the wizard, and I can now establish inbound connections, but when connected (all traffic ...
HiScenario:Cisco ASA 5505We have Remote VPN working and we can access our office network from a remote VPN client, and the other way around also.We would now like to extend this config, so that when accessing a set of IPs on the internet (our website...
HiWe have a Remote IPSec VPN setup on our Cisco ASA 5505.This allows a connection, however when we try and route traffic for our internal network, plus a set of external IPs, we get the traffic blocked for VPN users.I am presuming this is either an A...
HiWe have the following scenario:Office (192.168.2.x)Data Centre (212.64.x.x)Home workers (192.168.2.x) (DHCP scope is within office subnet) Connections:Office to Data Centre traffic is routed through a Site to Site IPSec VPN, which is working fine....
HiWe have a small business office, but due to PCI compliance we need to segment this into two internet networks (one 'compliant' and one for any other devices to use).We currently have a Draytek modem/wan load balancer which also has firewalling but ...
Hi David
That's been added but no joy unfortunately. The users can still access internal devices on 192.168.2.0 but can't get outside of this to the internet.
Here's our current config:
Hi David
That's been added but no joy unfortunately. The u...
After seeing the errors about Split-Tunnels, I changed the config from 'tunnel all' to 'tunnel selceted networks'
This then allows the traffic to the internet fine, but isn't really a fix, because we need anyone connecting through the VPN to have ou...
Hi Aditya
Many thanks for this - unfortunately it hasn't fixed the issue:
Result of the command: "sh run nat"
nat (inside,any) source static NETWORK_OBJ_192.168.2.0_24 NETWORK_OBJ_192.168.2.0_24 destination static NETWORK_OBJ_192.168.4.0_24 NETWORK...
Please note that the 'internet' isn't directly attached to our ourside interface, another router is - hence:
route outside 0.0.0.0 0.0.0.0 192.168.3.3 1
