cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
924
Views
0
Helpful
1
Replies

Please help Windows VPN and VPDN on 1841

wrinear
Level 1
Level 1

I am desperate !!! I was asked to get the VPN working as a couple other persons were not successful.

I got the VPN up but I can't ping anything (even the inside interface)from the windows client. I can ping anything from inside the router (via telnet). I broke the config down to bare essentials as a test (no NAT no access lists) I get an IP address from the pool and the VPN is up.

I ran debug vpdn packet and got the following.

000282: *Aug 1 00:31:15.955 ESTime: Vi3 VPDN FS Tunnel to network: Sending 68 byte pak

000283: *Aug 1 00:31:15.955 ESTime: Vi3 VPDN CEF Tunnel to network: Fastswitching failed, punting pkt to process

000284: *Aug 1 00:31:15.955 ESTime: Vi3 VPDN CEF From tunnel: Punted 68 byte pak to ppp parse and iqueue

000285: *Aug 1 00:31:31.603 ESTime: VPDN CEF From tunnel: Received 94 byte pak

000286: *Aug 1 00:31:31.603 ESTime: Vi3 VPDN FS Tunnel to network: Sending 48 byte pak

000287: *Aug 1 00:31:31.603 ESTime: Vi3 VPDN CEF Tunnel to network: Fastswitching failed, punting pkt to process

000288: *Aug 1 00:31:31.603 ESTime: Vi3 VPDN CEF From tunnel: Punted 48 byte pak to ppp parse and iqueue

000289: *Aug 1 00:31:32.055 ESTime: VPDN CEF From tunnel: Received 94 byte pak

000290: *Aug 1 00:31:32.055 ESTime: Vi3 VPDN FS Tunnel to network: Sending 48 byte pak

000291: *Aug 1 00:31:32.055 ESTime: Vi3 VPDN CEF Tunnel to network: Fastswitching failed, punting pkt to process

000292: *Aug 1 00:31:32.055 ESTime: Vi3 VPDN CEF From tunnel: Punted 48 byte pak to ppp parse and iqueue

000293: *Aug 1 00:31:32.575 ESTime: VPDN CEF From tunnel: Received 94 byte pak

000294: *Aug 1 00:31:32.575 ESTime: Vi3 VPDN FS Tunnel to network: Sending 48 byte pak

000295: *Aug 1 00:31:32.575 ESTime: Vi3 VPDN CEF Tunnel to network: Fastswitching failed, punting pkt to process

000296: *Aug 1 00:31:32.575 ESTime: Vi3 VPDN CEF From tunnel: Punted 48 byte pak to ppp parse and iqueue

000297: *Aug 1 00:31:33.611 ESTime: VPDN CEF From tunnel: Received 94 byte pak

000298: *Aug 1 00:31:33.611 ESTime: Vi3 VPDN FS Tunnel to network: Sending 48 byte pak

000299: *Aug 1 00:31:33.611 ESTime: Vi3 VPDN CEF Tunnel to network: Fastswitching failed, punting pkt to process

000300: *Aug 1 00:31:33.611 ESTime: Vi3 VPDN CEF From tunnel: Punted 48 byte pak to ppp parse and iqueue

000301: *Aug 1 00:31:35.683 ESTime: VPDN CEF From tunnel: Received 94 byte pak

000302: *Aug 1 00:31:35.683 ESTime: Vi3 VPDN FS Tunnel to network: Sending 48 byte pak

000303: *Aug 1 00:31:35.683 ESTime: Vi3 VPDN CEF Tunnel to network: Fastswitching failed, punting pkt to process

000304: *Aug 1 00:31:35.683 ESTime: Vi3 VPDN CEF From tunnel: Punted 48 byte pak to ppp parse and iqueue

000305: *Aug 1 00:31:35.683 ESTime: L2X: IP socket write 60 bytes, 66.175.120.93 to 76.30.45.29, prot 47

000306: *Aug 1 00:31:36.603 ESTime: VPDN CEF From tunnel: Received 102 byte pak

000307: *Aug 1 00:31:36.603 ESTime: Vi3 VPDN FS Tunnel to network: Sending 56 byte pak

000308: *Aug 1 00:31:36.603 ESTime: Vi3 VPDN CEF Tunnel to network: Fastswitching failed, punting pkt to process

000309: *Aug 1 00:31:36.603 ESTime: Vi3 VPDN CEF From tunnel: Punted 56 byte pak to ppp parse and iqueue

000310: *Aug 1 00:31:39.491 ESTime: VPDN CEF From tunnel: Received 102 byte pak

000311: *Aug 1 00:31:39.491 ESTime: Vi3 VPDN FS Tunnel to network: Sending 56 byte pak

000312: *Aug 1 00:31:39.491 ESTime: Vi3 VPDN CEF Tunnel to network: Fastswitching failed, punting pkt to process

I am feeling really dense. The broken down config is attached.

1 Reply 1

murabi
Level 4
Level 4

Possible solution

If the terminating device sends the VPN Client an IP address that is on the same network (10.50.1.x), the user cannot send any data over the client connection.Refer URL http://www.cisco.com/en/US/products/sw/secursw/ps2308/products_tech_note09186a00801b7615.shtml

Configuring an IP Unnumbered loopback X interface on the virtual-temaplate i/f meant for terminating VPDN sessions on LNS resolves the issue.