So, you are trying to use the ASA as a EZVPN client to the VPN3000 that is not designed to be a EZVPN server?
I suggest setting up a static LAN-2-LAN VPN tunnel
0
dc0ntrerasAuthor Commented:
We have several other ASA's configured the same way that are terminating on that VPN3000. Any other ideas?
Thanks
David C.
Wan link? Is the connection solid? Is it DSL? Cable?
Is there anything different about this configuration than any of the others that work fine? It could be the difference between OS 8.2(1) and this 8.2(5)
Try downgrading to 8.2.1?
0
Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.
I cant get 8.2.1 from Cisco website. It only provides 8.2.2 or 8.0.2-5. I tried 8.2.2 same results. Any other ideas?
should I try 8.0.5?
0
dc0ntrerasAuthor Commented:
OK Lmoore, you said
So, you are trying to use the ASA as a EZVPN client to the VPN3000 that is not designed to be a EZVPN server?
I suggest setting up a static LAN-2-LAN VPN tunnel .
What are you seeing that is telling you that I am using EZVPN?
I have never used teh EZVPN /ADSM software, so I am not sure what the difference in the configuration would look like. I am trying to setup a site to site/LAN 2 LAN vpn tunnel from an ASA5505 to a 3000 concentrator that already has several ASA's.
The log on the ASA shows:
Tunnel Rejected: Conflicting protocols specified by tunnel-group and group-policy
This may be what you are referring to, im not for sure though.
The connection is intermittent.
I tried setting the outside mtu to 1492, no help.
I am stuck.
I am going to try and get a config from a known working ASA.
0
dc0ntrerasAuthor Commented:
lrmoore, I took the ASA home it does the same thing, so I know its not my connections at work. Its not the OS, I tried 8.2.2, then I tried the config on another ASA with 7.2.4, does the samething.
0
dc0ntrerasAuthor Commented:
We had the IP address already in use by another use. That was the problem.
0
dc0ntrerasAuthor Commented:
We found the problem with more troubleshooting with cisco.
0
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
I suggest setting up a static LAN-2-LAN VPN tunnel