Thanks for the response. When I have turned on loggin on VPN Client,
the following message appears in log:
3 09:20:59.681 09/23/04 Sev=Warning/3 IKE/0xA300004B
Received a NOTIFY message with an invalid protocol id (0)
What do I have to fix?
Thanks in advance.
JG
(Walter Roberson) wrote in message news:<citqif$7e6$>...
> In article < >,
> Asif <> wrote:
> :I am trying to connect to PIX firewall using Cisco VPN Client 4.0.3.
> :When I try to connect it, after typing user name and password, its
> :says "
> :Secure VPN connection is terminated locally by the client
> :Reason 412: The remote peer is no longer responding."
>
> :ip address inside 192.168.0.3 255.255.255.0
>
> :route inside 192.168.0.0 255.255.0.0 192.168.0.1 1
>
> Your route statement overlaps with the IP range of your inside address.
> Are you sure that is what you want?? It pretty much hints that you
> have some inside hosts in the 192.168/16 net, which would have
> a broadcast IP of 192.168.255.255, but your inside interface is going
> to have a broadcast IP of 192.168.0.255 . Sounds like a recipie for
> trouble.
>
> :crypto ipsec transform-set myset esp-3des esp-sha-hmac
> :crypto dynamic-map dynmap 10 set transform-set myset
> :crypto map mymap 10 ipsec-isakmp dynamic dynmap
> :crypto map mymap client configuration address initiate
> :crypto map mymap client configuration address respond
>
> I seem to recall that address respond is redundant in conjunction
> with vpngroup, as the vpngroup is required to hand out an address from
> the address-pool. The server creates an IPSec proxy mapping the
> client internet IP to the address-pool address, and then communicates
> with the client via that allocated address-pool IP.
>
> :isakmp client configuration address-pool local mydhcp outside
> :vpngroup vpnuser address-pool mydhcp
>
>
> That's what pops to mind without deeper analysis.
Similar Threads
