Netgear wireless router issues with Cisco VPN client

[bc21640]

I have a very similar issue to UNCRemus: I have a cisco vpn client and a Netgear wireless MR814 with my cable modem (win2k pro). I can log in and it authenticates me but then I can't access anything until I disconnect. If I plug in directly to the cable modem it works fine. It all used to work when I had ISDN and a WAP without a router. Is there a port I need to enable on port forwarding? I have the IP address but not the port info. Any ideas? Thanks.

 

[dopehead]

First of all, when you are connected through the wireless ap, what does the status of the vpn client say ? Is it running udp or tcp encapsulation or nothing at all ?

What are you connecting to 3000 or PIX or IOS ?
Jan

 

[vbates]

One of my clients has the same problem as 'bc21640'. My client uses a netgear MR814 wireless router, connecting with the Cisco vpn client to a Cisco 3005 Concentrator.

Any ideas what I can do - is their some setting on the router to add/modify.

thks

 

[tobascojojo]

Does the Netgear MR814 support VPN pass through?

 

[bc21640]

Sorry been out for several weeks. It says it supports VPN. It is the standard Netgear Wireless router you can find at Best buy or Circuit city. Weird as soon as I plug directly into the cable modem it works fine.

When I look at the properties for the connection on my cisco VPN it has Enable Transparent Tunneling Checked off and then ALLOW IPSEC over (UDP NAT/PAT).

Thanks.

 

[krkmi]

I had the same issues with VPN. It has been resolved When I upgrade the Router software to the latest version of Firmware.
I'm using MR814V2

http://www.netgear.com/support/support_details.asp?dnldID=479

Thanks
RK

 

[aglenn78]

I had the same issue as bc21640, even after upgrading the router software to the latest version. I figured out that I had two problems:

1. I had to disable "transparent tunneling" in the options of the cisco vpn client. That fixed most problems, but still some sites were slow or timed out.

2. The MTU (max transmission unit) settings were wrong somewhere between my computer/my router. This microsoft kb article gives three possible fixes. Fix #1 alone worked for me. I've heard others used fix #1 and #3 to fix similar issues. Good luck!

http://support.microsoft.com/default.aspx?scid=kb;en-us;314825