• May 22, 2025, 11:56:50 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: D-Link Dir-655 VPN L2TP Problem  (Read 8586 times)

Rob39572

  • Level 1 Member
  • *
  • Posts: 2
D-Link Dir-655 VPN L2TP Problem
« on: October 26, 2009, 12:30:34 PM »
For the life of me I can not get my D-Link router to allow VPN L2TP outward connections. I have set up all the setting from the other post at http://tinyurl.com/ykxuele but still it does not let VPN L2TP through the router. I have verified it is the router by plugging my Vista-64 bit pc directly in to the internet and it works. But not in the router. Attempted it also on a different PC as well, still failed. Works plugged in to the internet. It keep failing with an Error of "ERROR 789: The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer." http://i38.tinypic.com/2vv2iiq.jpg (Image).

Need to get this fixed as soon as possible. Thank you very much if you have any idea how to fix it. I have upgraded the router to the latest firmware with no dice too.

Thanks

Rob
Logged

bluenote

  • Level 2 Member
  • **
  • Posts: 82
Re: D-Link Dir-655 VPN L2TP Problem
« Reply #1 on: October 30, 2009, 06:03:13 PM »
Try enabling (or disabling) the VPN ALG's (or all of them).
Mine works fine without ALG's and without configuring any special port forwarding.
To properly test I'd remove that mapping also.
Logged

Rob39572

  • Level 1 Member
  • *
  • Posts: 2
Solution: D-Link Dir-655 VPN L2TP Problem
« Reply #2 on: October 30, 2009, 06:27:45 PM »
Thanks for help.  Found the problem, and Solution.
In the VPN Properties --> Networking Tab --> Button "IPSec Setting" I had a preshared key entered.
As a result it only worked by wiring the computer directly to the Cable modem. Why I have not a clue.

Solution was to switch from a preshared key to "Use certificate for Authorization" (and enabled "verify the name and usage" then it worked through a router then.

Why again I have not a clue. But it sure was strange and a pain in the A$$. 

Thanks all,

Robert
Logged