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.
I have a RV082 v2 with Firmware 2.0.2.01-tm with a Site-to-Site VPN to a Cisco ASA5510.The PCs behind the RV082 can not see two webservers behind the ASA5510. Both servers have full DNS registration and are accessable from other sites with RV042 rout...
Need to setup a VPN from my ASA 5510 to remote SonicWall TZ170 with overlapping networks, both are 192.168.1.0/24.One server on my end, 192.168.1.76, needs to receive data from their end PC which is 192.168.1.105.I understand NAT will be needed on bo...
I have a new customer that needs to send data to us occasionally, we normally install the Cisco VPN Client on their PC, but this customer has the same private network we do.I know this could be done with NAT Policy on my ASA 5510 with a site-to-site ...
I need to migrate from a Cisco PIX 501 running 6.3(5) and to a Cisco ASA 5505 with 7.2(1).The 501 is setup for several VPNs, all 3DES.I need to get the 5505 up as quickly as possible, can the config from the 501 be used? What do I need to look out fo...
VPN between my PIX 501 6.3(1)on T1, and a Linksys RV042 on DSL, has been up for several months, now is dropping every couple of days. The PIX has MM_NO_STATE in PDM for this VPN.If the far end R042 is power cycled the link comes back up when traffic ...
I missed this in my review:The link is now working, can login and transmit files, connect by VNC to server and so on. (Can't ping, but no problem).Thank you for all the help and patience in getting this resolved, this will help greatly.
Here are all of the "access-list" commands in my ASA, the to in your 6/14 8:59 PM post are the last ones in this list:access-list outside_in extended permit tcp any host 66.0.171.243 eq 1199 access-list outside_in extended permit tcp any host 66.0.17...
I decided to start fresh, restored settings from file to ASA and reloaded. Used the wizard to create and new IPsec Remote Access VPN. I then ran the two command from your last post of 6/14@12:48. The resulting lines in the config are:tunnel-group VPN...
I applied these lines, and the 10.30.30.x address is assigned at the client end.The client can not ping anything in the 10.30.30.0 or 192.168.1.0 networks.The line from my previous post "static (inside,outside) 10.30.30.0 access-list nat2VPN" is not...
