Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Cisco VPN Dialer woes with consumer WAPS

Hi All

Question, I need to buy several consumer WAP's - DSL type , that I can connect multiple users to that will then use the Cisco VPN Dialer on there laptops to connect to there offices.

Issues I have found before is that on the consumer netgear ones I tried only 1 person could use the Cisco VPN dialer, and as soon as another person who was connbected to that WAP tried it, it knocked the first person off.

Anyone come up with this issue before and found a solution? With Linsys now being owned by Cisco I would have hoped they may have got a work around but my searches on google imply now. but I hope to be proved wrong.

Scott

3 REPLIES
New Member

Re: Cisco VPN Dialer woes with consumer WAPS

Scott,

The problem is not with the home routers, but with the configuration of the VPN server.

PIX or VPN concentrators need NAT Traversal enabled on them.

http://www.cisco.com/en/US/docs/security/pix/pix63/configuration/guide/ipsecint.html#wp1057446

http://www.cisco.com/en/US/products/sw/secursw/ps2276/products_configuration_example09186a008010edf4.shtml

Let me know if this helps?

J

New Member

Re: Cisco VPN Dialer woes with consumer WAPS

Hi

Default setup is to use transparent connections with IPSEC over UDP already on the Cisco VPN dialers on the users laptops and thats works fine in most situations. That is, unless you have more 1 user on a consumer router and try to connect to one of the offices CIsco routers.

Scott

New Member

Re: Cisco VPN Dialer woes with consumer WAPS

Scott,

Assuming the VPN server that the Cisco VPN client's are connecting to is either a PIX or 3000 concentrator, my previous post will take care of this issue. Believe me, I went through this before and was able to resolve the issue with one simple command in our old PIX (we now use an ASA).

J

216
Views
0
Helpful
3
Replies