VPN Router-Client doesn't work out of USA

How do I setup the router?
Router Linksys WRV200 works with VPN in USA but South America (Ecuador, Argentina), we uses QuickVPN_Client_v1.2.11
FernandoMonroyAsked:
Who is Participating?
 
arnoldCommented:
payload_malformed might mean that there is an issue with the passphrase, policy mismatch. http://forums.linksys.com/linksys/board/message?board.id=Wireless_Routers&message.id=83130 deals with the PFS option.  Could it be that you have the VPN client configured for PFS while the policy on the WRV has the PFS option disabled or vice versa?

i.e. check the policy on the WRV dealing with PFS settings and the remote LAN IPs as well as what the remote systems LAN IP is.
Also check what the VPN client logs.  If possible, make the logging more verbose on the VPN client side.
0
 
arnoldCommented:
You have not provided any information on which to base a suggestion.
Do you see the connection attempts on the WRV200?
The location from which the VPN is attempted might have VPN access restricted/blocked.
What errors if any are seen on the client?
0
 
FernandoMonroyAuthor Commented:
We have access to the VPN in USA.
We are trying to access from  Ecuador and  Argentina without success.
When we ran the Quick VPN client  the systems send this message:
- Connecting
- Activating Policy
- Verifying Network,
 the program  send this error:
 The remote gateway is not responding. Do you want to wait?
Yes or No
We answer Yes

Without succes.

In the VPN Log we activity
 
"loading secrets from ëtc/ipsec.secrets"
listening for IKE messages
forgetting secrets
 
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
arnoldCommented:
VPN log is that from the wrv200?  The client reports that it is not receiving a response.  Do you see the request on the WRV?
0
 
FernandoMonroyAuthor Commented:
Yes,  the VPN Log is from the WRV200
The client received the message ""The remote gateway is not responding. Do you want to wait?"
0
 
arnoldCommented:
The notice is that the client did not receive a response. and is generating the error notice.

This might be an issue with the location you are in that is not permitting VPN access.  You should check with the party through whom you connect to the net whether VPN access is being blocked.  If you use your own router, make sure that it has VPN IPSEC passthrough enabled.
0
 
FernandoMonroyAuthor Commented:
What are the parameters that my ISP could block for VPN acces?
0
 
arnoldCommented:
UDP Port 500/4500, 1723, 1701,10000 depending on what your VPN client uses.
Are you able to access SSL encrypted sites from these locations, setup an SSL VPN if the option exists.
0
 
FernandoMonroyAuthor Commented:
The ISP doesn't block those ports
0
 
arnoldCommented:
IF the ports are not being blocked, you should see at least access attempts on your side that either fail because of phase 1, phase 2, passphrase mismatch etc.  If you see no attempts, that suggest that it is being blocked/lost somewhere along the way..
If any of the packets reach your server, you should see it either an error because the packet was malformed/fragmented, etc.
0
 
FernandoMonroyAuthor Commented:
This messages are in the VPN Log:
150   [Sun 14:16:05]  packet from 71.231.2.207:500: next payload type of ISAKMP Message has an unknown value: 133
151   [Sun 14:16:05]  packet from 71.231.2.207:500: sending notification PAYLOAD_MALFORMED to 71.231.2.207:500
152   [Sun 14:16:07]  packet from 71.231.2.207:500: next payload type of ISAKMP Message has an unknown value: 133
153   [Sun 14:16:07]  packet from 71.231.2.207:500: sending notification PAYLOAD_MALFORMED to 71.231.2.207:500
154   [Sun 14:16:10]  packet from 71.231.2.207:500: next payload type of ISAKMP Message has an unknown value: 133
155   [Sun 14:16:10]  packet from 71.231.2.207:500: sending notification PAYLOAD_MALFORMED to 71.231.2.207:500
156   [Sun 14:16:14]  packet from 71.231.2.207:500: next payload type of ISAKMP Message has an unknown value: 133
157   [Sun 14:16:14]  packet from 71.231.2.207:500: sending notification PAYLOAD_MALFORMED to 71.231.2.207:500
158   [Sun 14:16:23]  packet from 71.231.2.207:500: next payload type of ISAKMP Message has an unknown value: 133
159   [Sun 14:16:23]  packet from 71.231.2.207:500: sending notification PAYLOAD_MALFORMED to 71.231.2.207:500
160   [Sun 14:16:40]  packet from 71.231.2.207:500: next payload type of ISAKMP Message has an unknown value: 133
161   [Sun 14:16:40]  packet from 71.231.2.207:500: sending notification PAYLOAD_MALFORMED to 71.231.2.207:500
162   [Sun 14:16:56]  packet from 71.231.2.207:500: next payload type of ISAKMP Message has an unknown value: 133
163   [Sun 14:16:56]  packet from 71.231.2.207:500: sending notification PAYLOAD_MALFORMED to 71.231.2.207:500

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.