Kinnikuman
@ca.us | reply to DocLarge
Re: WRV54G VPN Connection problem
Dude, you are a STUD! I was wondering why I kept getting a no connect error. SO I followed your advice and disabled the Router to Rputer tunnels and was able to connect via the QuickVPN.
Thanks! |
|
PhireM
join:2005-01-09
Australia
| reply to DocLarge
I have a WRV54G Friggin device and have had many troubles with it.
I have sold many of them to my clients and they all do not work, currently I have six out in the field and 1 at home. All with the same stupid problem, dont buy bulk until it is tested. It sounded like a dream VPN Router.
I have convinced my supplier to return all Linksys WRV54G's due to they do not do what they are advertised to do, a very big consumer issue when you are selling a product. It must do what it is advertised to do.
I am getting the BERVP41's and in the situations that I need wireless Router, I will also get a Wireless router to attach to the BEFVP41v2.
So far I have tested the BEFVP41v2 and all works well, what surprises me the most is that it is written on the same software as the WRV54G - Look at the GPL code centre.
My advice is to stop playing with the Stupid device and get one that works; your time is too Valuable to waste on the WRV54G |
|
jpstoppa
join:2004-12-01
Barrie, ON | reply to JohnLouis
Did you check your Windows incoming connection settings. You Will need to set this up correctly to have it working. User name and password in particular. I have the same settings as you and connect using VPN without any problems.
Jake |
|
DocLarge
Premium
join:2004-09-08
| reply to JohnLouis
Hi Guys,
any progress been made, mills?
John,
under the applications and gaming tab on your router, you have the option to input these ports to use; however the quickvpn client doesn't need to run those ports because it creates its own tunnel via port 443 (which is already opened on the wrv54g router. If you scroll up on this post, I threw in some information that helped me get my wrv54g vpn running... |
|
JohnLouis
@bellsouth.ne | reply to DocLarge
DocLarge, I'm a new to VPN. On what device do you disable ports 1723, 500, 443, and 4500? And How? |
|
DocLarge
Premium
join:2004-09-08
| reply to sgkmills
Fortunately, one router is all you need (the WRV54G is all I'm running for VPN). If I forgot to mention, you can't have any other vpn utility running on your machine while linksys quickvpn is loaded.
Now, if you're still not having any luck connecting, and your ISP is not blcoking VPN traffic, you're problem is simply configuration. I've got a user who connects to my WRV54G using Win XP SP2 along with the linksys quickvpn and he has no problems, and while I'm out of my house, I can connect to my router using linksys quickvpn on my laptop (OS is Win2k Pro).
So, if you've disabled PPTP, L2TP, and IPSec Pass-thru,
are you running Win XP Pro with a personal firewall? If so, turn it off. |
|
sgkmills
join:2004-11-09
Brooklyn, NY
| reply to DocLarge
To all:
I did what DocLarge described to make a connection (#1, #2 and #3) and still cannot connect.
The QuickVPN client program gets to verifying network and just hangs.
Since I only have one router, I am not doing the VPN tunnel setup. |
|
DocLarge
Premium
join:2004-09-08
1 edit | reply to sgkmills
Sgkmills, here's the no bullsh*t way on how to communicate with your WRV54G being that the Linksys instructions are trash.
For Linksys Quickvpn Client to WRV54G Connection, do the following:
1) Disable PPTP, L2TP, and IPSEC Passthru
2 Disable VPN Gateway, VPN Tunnels, Key Management, Encryption, Authentication, and PFS Shared Key
3) Until you're able to connect with quickvpn, disable ports 1723, 500, 443, and 4500; these settings "might" disrupt communication between the client and the WRV54g
Quickvpn will make its own secure tunnel with the WRV54g "without" all the following things I just mentioned that you need to disable. The above configuration is what you would do "if" you're WRV54G is acting as an "endpoint" and people are using quickvpn to connect "to" your router. As the VPN termination point, "you" do not need to enable the services in items #1 and #2; if "you" were a quickvpn user who needed to connect "to" a WRV54G vpn router, then "you" would enable pptp, L2tp, and IPSEC Pass-thru on "your" router.
-----------------------------------------------------------
Now, if you want to connect your vpn router to another vpn router, then you would have to open up a tunnel between your router and the other vpn router and slowly start opening "ports" (i.e. 1723 etc...) one by one as a means of process of elimination:
Tunnel: Enabled
Gateway: Disabled
Tunnel Name: Linksys
Local Sec. Grp (Your Lan): 192.168.1.10
255.255.255.0
Remote Sec. Grp (Other Lan) 192.168.2.10
255.255.255.0
Remote Sec. Gtwy (Other Lan's Wan IP) 24.255.34.154
Encryption: 3DES (Suggested)
Authentication: Sha1 (Suggested)
Key Management: Auto(IKE)
PFS: Enabled
Pre-Shared Key: (Enter a password)
Key Lifetime: 3600 (Suggested)
Make sure your settings in the Advanced VPN Configuration Tunnel are similar... |
|
sgkmills
join:2004-11-09
Brooklyn, NY
| reply to tshuva
The packets were sniffed from the client machine. There is no firewall enabled on this machine.
I am not sure what you mean by sniff packets in front of the wrv, can you be more detailed.
The setup is as follows:
CableModem-->WRV54G->WinXP w/SP2->Internet--WinXP (client)
The WinXP client machine has QuickVPN and that is where I sniffed the packets.
Do you mean run the packet sniffer on the WinXP w/SP2 machine?
Also, I tried to use QuickVPN on another client machine. This machine was a Windows Server 2003 machine. The same thing happens. |
|
tshuva
join:2004-10-30
| reply to sgkmills
Frames 18-20 indicate that the isakmp packets from
the win xp are not getting any response. It might
help to understand whether the packets are getting
to the wrv, or if they are dropped on route.
1) Did you sniff the packets before leaving the win xp box? If so, ensure that the xp firewall is off. The firewall blocks IPSec packets.
2) Try sniffing on the wan side of your xp's nat router to see if the isakmp packets leave that router. Perhaps it is blocking port 500. Also, make sure you have ipsec passthrough enabled on that router.
3) If the packets are definately leaving your network, but no response arrives, then perhaps some firewall between your xp network and your wrv network is blocking ipsec. If you can sniff packets in front of your wrv, you can get an indication of whether or not your isakmp packets are arriving there and whether the wrv responds. |
|
