Prev: Cisco MTBF
Next: Reason 401: An unrecognized error occurred while establishing the VPN connection.
From: James on 10 Feb 2006 07:13 I just can't get this to work out of the box/running wizard. I'm getting error on client of: Secure VPN Connection terminated locally by the Client. Reason 412: The remote peer is no longer responding. What areas should I be looking at please? I've set the VPN Easy Server up and made it Initiate as well as Respond. I'm using a key phrase to connect with. I've tested the VPN server in the SDM software and its says its ok. Short of an entire dump please let me know what more info you need?
From: Merv on 10 Feb 2006 08:42 Are you using a firewall on your PC such as Windows XP firewall ? Did you add the Cisco VPN client as an exception ? Firewall must be configured to permit UDP ports 500 and 62515 whcih are required for cisco vpn client.
From: James on 10 Feb 2006 10:42 I have F-Secure on client which I think is configured to allow the VPN client - I will check. As for the network there is no software firewall on the server, just the Cisco box. I assume that the wizard setup the correct rules to allow clients in but how do I check this port config? Thanks for responding - you are the first one in over a month and I was going slowly mad!
From: Walter Roberson on 10 Feb 2006 12:36 In article <1139578923.842010.93130(a)z14g2000cwz.googlegroups.com>, Merv <merv.hrabi(a)rogers.com> wrote: >Firewall must be configured to permit UDP ports 500 and 62515 whcih are >required for cisco vpn client. I'd never heard of 62515 being required before. I see it listed in the VPN 3000 concentrator FAQ, http://www.cisco.com/warp/public/471/vpn_3000_faq.shtml along with 62514 thru 62524. The description of the port use given in the FAQ does not suggest to me that the firewall would need to be opened to permit any of those ports: they appear to me to only to be talking from the local machine to itself?
From: Merv on 10 Feb 2006 16:13 besides disabling your firewall, verify that you PC is actually transmitting packets. Start a cmd windows and run the command "netstat -s -p ip 60" to see IP sned and receive packet counts
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: Cisco MTBF Next: Reason 401: An unrecognized error occurred while establishing the VPN connection. |