WRT54G v2 VPN problem

Discussion in 'Cisco/Linksys Wireless Routers' started by Birdie_uk, Sep 12, 2006.

  1. Birdie_uk

    Birdie_uk Guest

    I have an issue with using VPN through my WRT54G v2 router. I have a windows 2003 standard server running using the routing and remote access service I can vpn to the server locally on the LAN which proves that the service and server is correctly setup.

    I am on ip range 192.168.1.x so I have my router port forwarded to my sever address which is TCP port#1723

    the error i get from the PC i am vpning from is (Error 619 - A connection to the remote computer could not be established, so the port used for this connection was closed)

    I have made sure that the PC I am vpning from is not on the same subnet range as my home network etc and that the firewall lets out vpn traffic.

    I have tried both the ip address give to my router by NTL and also my Dyndns dns address.

    Have I missed anything LOL :confused:

    Please somebody help me

    --Router & Network setup--

    WRT54g v2
    Firmware Version : v4.20.8
    DHCP: DISABLED (Running from (w2K3 server)
    Local DNS: (Running from (w2K3 server)

    If you need anymore information please let me know

    Thanks in advance for your help :thumbup:
  2. leebob

    leebob LI Guru Member

    Make sure you have the Remote Access Permissions on the Dial In tab of the user account you are using in Active directory to ALLOW Access or Control Access through Remote Access Policy. Leave the default policies active in Routing and RAS. If these are true, be sure your ISP is not blocking 1723 TCP inbound. Go to www.canyouseeme.org to port check 1723. If it is port forwarded to your server, it should find the service. Routing and RAS is pretty straight forward and there are not too many things that will cause this to fail other than the above or a router that does not support GRE passthrough(yes, I had this problem), but fortunately, the WRT54G works well for PPTP VPN.
  3. timhar

    timhar LI Guru Member

    Solution to VPN, PPTP passthough using Win2k3 SBS

    I don't typically post, but this one needs to get communicated...no thanks to linksys...

    I've implemented several 2k3 SBS installation using linksys routers as the firewall. In all instances up to this point I've used the same configuration of port mapping; it has worked fine. My last one I ran into an issue getting the VPN to work; Error 721 everytime, and the VPN connection would hang on "verifying username and password". The error in the SBS Event log:

    A connection between the VPN server and the VPN client X.X.X.X has been established, but the VPN connection cannot be completed. The most common cause for this is that a firewall or router between the VPN server and the VPN client is not configured to allow Generic Routing Encapsulation (GRE) packets (protocol 47). Verify that the firewalls and routers between your VPN server and the Internet allow GRE packets. Make sure the firewalls and routers on the user's network are also configured to allow GRE packets. If the problem persists, have the user contact the Internet service provider (ISP) to determine whether the ISP might be blocking GRE packets

    I verified the DSL provider is allowing protocol 47, I validated my VPN works on the LAN side, so I call Linksys.... Asking if there is anything wrong with their latest firmware? NOPE...all works fine they say.... Well here's how I solved the problem:

    Using the same router WRT54GS V2, I rolled back the firmware version by version using their TFTP client. Nothing working until I got to v3.17.4 and VIOLA... VPN works!

    Conclusion: PPTP passthrough has issues in firmware later than V3.17.4, I've tried every version available on their FTP site and none of them later than 3.17.4 allow PPTP passthrough.

    Thanks Linksys for all the help and support.... you can close my ticket.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice