Re: WRV54G VPN Connection problem in Linksys http://www.dslreports.com/forum/r11922453 en Fri, 27 Nov 2009 23:03:56 EDT Fri, 27 Nov 2009 23:03:56 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,14096284 DocLarge : Quickvpn uses IPSEC, so if you have a PPTP gateway up and running with another router, any one using an IPSEC client who tries to connect will "not" be able to access the network while the tunnel is up. The only way I personally see getting around that would be to have the folks connecting from (yet another :) ) location to have a vpn router that can create another tunnel between where its users are located to the second (and final) tunnel hosted by the (hypothetical) befsx41 router at your original location.

The downside about this is your "two user" remote location will be using a lot of bandwith supporting two seperate vpn gateway tunnels; you'll just have to bite the bullet on that one if you do that much business and absolutely need to have that sort of connection. Hell, it might even justify more bandwith. :)

Doc]]> http://www.dslreports.com/forum/remark,14096284 Tue, 09 Aug 2005 17:04:59 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,14096057 anon : Hey Doc, you are everywhere!

I am very familiar with PPTP (RAS on NT4.0 RRAS on 2K and 2k3)

I guess my main question would be...If I place another vpn router for the two remote users and set up a site to site vpn can I still have single users use the quickvpn utility from other locations or did you mention pptp because that is what the quickvpn uses?
I thought it was using ipsec/isakmp.

Thanks again!

Colin]]> http://www.dslreports.com/forum/remark,14096057 Tue, 09 Aug 2005 16:35:04 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,14095986 DocLarge : That is correct. Only one person at a time can make a connection with quickvpn from the same site. The only way to get around this would be for your remote users to have an endpoint router (i.e., BEFSX41 if there are only two people at that particular location) to establish a vpn-to-vpn gateway between their endpoint router and your WRV54G.

PPTP is a different protocol (let's say "rule" for the sake of distinction right now) and only "one" rule can work at any given time, so, it becomes an "either/or" thing. That being said, your best bet would be for them to replace their WRT54G and get a real vpn router.

Don't waste time with firmware hacks (sveasoft, sartori, hyperwrt) because while as good as they may be, a majority of third party software don't consider the original processing power of the router when installing all of these "hyped up" processess the router can't support because it just wasn't built to support it.

Doc]]> http://www.dslreports.com/forum/remark,14095986 Tue, 09 Aug 2005 16:27:14 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,14095521 anon : Hi folks. Doc, thanks for your guide on this. It was a tremendous help. Do you or anyone else have any recommendations on having two users connect simultaneously through the same WRT54G back to the WRV54G using the quickvpn utility? I have two remote users that use the same cable modem connected router with a single IP address and only one client can connect at a time. I am assuming that this is due to the dynamic nat tables not knowing how to pass commincation back to the right internal device/computer based on the single external IP.

I also saw it mentioned that the WRV54G can't do both quickvpn and static tunnels at the same time. Is this true.

TAOT

Maxx]]> http://www.dslreports.com/forum/remark,14095521 Tue, 09 Aug 2005 15:26:17 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,14046782 DocLarge : I would direct you to the linksysinfo.org site to see my updated version of the "Quickvpn Connection Setup Guide" but the site is down for the moment. When it comes back up, go to the homepage and check on the bottom for the "Quickvpn Setup Guide."

Doc]]> http://www.dslreports.com/forum/remark,14046782 Wed, 03 Aug 2005 07:08:00 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,14009535 Miskulin : Hi!

DocLarge: I read all your posts about QuickVPN and WRV54g :).

I partial solved problem: I had port 443 forwarded to the local computer. And when I deactivated that rule, it started working partial...

QuickVPN gives me a message: The remote gateway is not responding. You will now be disonnected, please try again later.

I followed all your posts and I've not found any solution yet...

Thanks.

Regards, M]]> http://www.dslreports.com/forum/remark,14009535 Fri, 29 Jul 2005 03:35:52 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13527733 DocLarge : I may be late on this but here's a copy of the "Quickvpn Setup Guide" a friend and I put together...

Doc
AbsoluteVPNn···olts.zip 5,417 bytes
(AbsoluteVPNnutsnbolts.rtf)
]]> http://www.dslreports.com/forum/remark,13527733 Sun, 29 May 2005 19:26:40 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13420737 DocLarge : You guys have still got something off in your configuration. Simply put, if you (initially) have a disabled firewall, no other vpn client loaded, but still can't get in, the configuration is off somewhere in the chain. I'm running a vpn session right now with quickvpn, and to boot, I'm doing it via wireless (my entire home network is wireless).

Check out the attached file. If you follow "everything" on it, you'll be able to connect because this is "exactly" how my configuration is and (again) I'm using vpn right now.

Doc
AbsoluteVPNn···olts.zip 4,217 bytes
(AbsoluteVPNnutsnbolts.rtf)
]]> http://www.dslreports.com/forum/remark,13420737 Mon, 16 May 2005 15:00:19 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13420521 spaniola : Doc, i am having the same problem, I know its the wget issue. any idea on how to fix verifying network?]]> http://www.dslreports.com/forum/remark,13420521 Mon, 16 May 2005 14:30:15 EDT Re: WRV54G VPN Connection problem solved! http://www.dslreports.com/forum/remark,13403050 DocLarge : Sorry I've been gone so long. I was quickvpn testing with a friend (TVOS). He and I have finally gotten quickvpn to perform like it's supposed to. I can officially say quickvpn is now the product it was intended to be!!! I'll be posting some revised instructions this weekend. TVOS tranferred 2Gb of information through the quickvpn tunnel which he had open for 10hrs straight. He was even able to print to my printer from his location (in Michigan) to where I am (in London, England) by using the printer shortcut icon I put in his shared folder. Absolutely bad ass!!

In return, I connected to his WRV54g and was able to see all the shared directories. I've helped a lot of folks get connected with quickvpn, but it's always funny when you try to do it yourself (after always being an endpoint) and bomb it :) Basically, after I changed a few key settings (running mtu in "auto" mode instead of "manual" which I've become accustomed to doing) and (possibly) setting the time zone to pacific time (-08:00 GMT) it all fired up and my vpn connection with quickvpn has been "FLAWLESS" ever since.

In lieu of the revised documentation, here's a link to where I give a brief revamped outline:

»www.linksysinfo.org/modules.php?···c&t=5120

Looking back, the early linksys documentation telling folks to setup a security policy in microsoft should have been directed more towards showing people how to establish a "basic connection."

The WRV has always been a good little box (barring some bad firmware updates). We just never were told by Linksys how to communicate with it...

Doc
Click for full size
]]> http://www.dslreports.com/forum/remark,13403050 Fri, 13 May 2005 21:54:50 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13397415 teamit : I'm trying to get a WRV54G to work as well.

I've got it connected to a cable modem, but I'm pretty sure the ISP has port 443 blocked.

My connection here is the same ISP but I'm behind a WRT54GS. I have no other firewalls enabled and I'm unable to connect.

On my network behind the WRT54GS I have a Windows 2003 SBS install and I have the ability to VPN to it. I had someone test this from another ISP and it worked perfectly.

So, what I'm trying to determine is why I cannot connect to the WRV54G.

The wget_error.txt file says this
--09:29:57-- »https://crose:*password*@205.251.160.247···ER=crose
=> `C://Program Files//Linksys//Linksys VPN Client//vpnserver.conf'
Connecting to 205.251.160.247:443... failed: Unknown error.
Giving up.

The message I recieve from QuickVPN is:
Failed to establish connection.
This could be caused by one of the following.
1. Incorrect Password
2. No valid IP address for the network card.
3. Incorrect server address.
4. You may need to disable your Windows firewall.

I've also tried using the Windows based VPN connection with no luck.

The settings on the WRV54G are standard fair. I have a hostname and domain name set-up, 10.x.x.x range IPs being handled by DHCP, I do have IPSec, L2TP and PPTP enabled.

Is there any way to get this to work, even with a third party client.

Thanks!
Chris]]> http://www.dslreports.com/forum/remark,13397415 Fri, 13 May 2005 08:14:58 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13360513 scrif : lol - Thanks Doc :)

If you can suggest how to get a VPN client to connect to/thru a RV042 which has 2 GW to GW VPN's already terminated on it, I would be a truly happy man.

Ive read a tonne of posts about VPN client software over the past few weeks and its just way too confusing. All I want is a SIMPLE, and FREE, VPN Client solution to the RV042.

Thanks]]> http://www.dslreports.com/forum/remark,13360513 Sun, 08 May 2005 16:32:13 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13358552 DocLarge : Good looking out, Scrif...

You are officially a "brother of I.T." to me. I've got time if you need help with anything...

Doc]]> http://www.dslreports.com/forum/remark,13358552 Sun, 08 May 2005 10:51:56 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13351687 scrif : Here you go:

My Settings for a WORKING Gateway to Gateway VPN between Two WRV54G's. Both with firmware version 2.37.1

IPSec Passthru Enabled
PPTP Passthru Enabled
L2Tp Passthru Enabled

(don't think above are needed, but left as defaults - possibly creates extra overhead?)

VPN Tunnel Enabled
VPN Gateway Disabled

Local Secure Subnet
Group 192.168.71.0 255.255.255.0

Local Secure Subnet
Group 192.168.122.0 255.255.255.0

Remote Secure IP Address
Gateway 1.2.3.4

Encryption 3DES
Authentication MD5

Key Exchange Auto(IKE)
PFS Enabled

Pre-Shared Key Enabled
RSA Signature Disabled
Key LifeTime 3600

ADVANCED SETTINGS

PAHSE1
Operational Mode MAIN
Encryption 3DES
Authentication MD5
Group 1024
Key Lifetime 3600

PHASE2
Encryption 3DES
Authentication Disable (this struck me as odd but I can't change it)
PFS Enabled
Group 1024
Key Lifetime 28000

Other Options
Netbios BroadCast Enabled
Anti-Replay Enabled
Keep Alive Enabled
If Ike Failed.. Disabled

The above settings are the same on both WRV54G's (obviously). I should mention that the ISP is the same for both ends and that High Speed in Canada is fairly robust (only 2 major competitors exist). No disconnect problems at all after 3 weeks solid. :)

Other VPN's I have had success with:

Two BEFSX41's to an RV042
WRV54G to BEFSX41

I tried to get one working between a WRV54G and a RV042 but couldn't - even had Linksys on the phone but they couldn't figure it out (surprise surprise) :mad:]]> http://www.dslreports.com/forum/remark,13351687 Sat, 07 May 2005 09:31:26 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13351172 DocLarge : I've yet to see anyone mention that type of simultaneous success. Incidentally, how do you have your wrv54g to wrv54g tunnel created, if you don't mind sharing the configuration?

Doc]]> http://www.dslreports.com/forum/remark,13351172 Sat, 07 May 2005 05:47:17 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13346537 scrif : My QuickVPN connection wasnt working. I read this entire post all the while thinking (hey, maybe if I disable the Gateway to Gateway VPN tunnel I have to another WRV54G, maybe it will work)....well guess what. IT DID!

Whoa Whoa, contain your excitement. Isn't this a bit useles?

From Linksys WRV54G product page....
"And finally, the Virtual Private Network (VPN) function creates encrypted "tunnels" through the Internet so up to 50 remote or traveling users can securely connect to your office network from off-site, or users in your branch office can connect to a corporate network."

So when they say "OR", it means you cant have both a Gateway to Gateway AND a Cleint to Gateway VPN tunnel at the same time?

Has anyone had any success with having a Gateway to Gateway VPN AND a Client to Gateway VPN connection at the same time?]]> http://www.dslreports.com/forum/remark,13346537 Fri, 06 May 2005 15:53:31 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13339377 DocLarge : I'm on the lookout for this also. Question though, seeing that the 50 client user license is on the horizon, I've started using my wrv as an endpoint again, but I'm getting tunnel drops around the 3- 4 min mark. This occurs only with my wrv (current firmware is 2.38). Still unsure if the problem is with the router or the modem.

Has anyone else come across this even after adjusting the MTU?

Doc]]> http://www.dslreports.com/forum/remark,13339377 Thu, 05 May 2005 18:37:43 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13298948 DocLarge : Papichi,

here's a revamped procedure I consolidated down into 6 steps. Most of the information posted throughout the forums (disable pptp, ipsec l2tp, etc...) comes from my original posts along with info I've picked up from other people's experiences with quickvpn over the last year. Try this:

1) Disable pptp and L2tp on the wrv54g
2) Disable all vpn port forwarding (500, 1701, 1723, 4500) to limit background process interference
3) Disable all vpn settings (tunnel, gateway, IKE)
4) Make sure quickvpn is the "only" client loaded on your machine (it won't work if another one is present)
5) Enable Ipsec on the WRV54G
6) Check under services if you're running a windows OS and make sure Ipsec is running (installing ssh sentinel knocks IPSEC offline)

These are just the general ground rules to start out with. One last thing to consider is if you're getting "verifying network," check your mtu setting. At times, you have to lower it to avoid fragmentation of the data packets.

As always, what's outlined is just a "baseline." As you start having success's, start varying your configuration.

Give this a shot...

Doc]]> http://www.dslreports.com/forum/remark,13298948 Sat, 30 Apr 2005 17:33:29 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13295421 Papichi : I am trying to figure it out. I can VPN using the Quick VPN using Linksys VPN Client with XP SP2 DISABLED. I want to have it ENABLED though and I have opened TCP ports 47, 1723, 50 and 500. Since then I have opened even more including the UDP counterparts as well. I still have not found the right TCP/UDP port combination to make it work.

I'll make sure I posted once I find the proper combo, since their tech support does not know it either. They asked me to contact Microsoft.]]> http://www.dslreports.com/forum/remark,13295421 Sat, 30 Apr 2005 03:18:47 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13219960 ChrisWHall : i added the hostname and Domain name and it started working!
thanks]]> http://www.dslreports.com/forum/remark,13219960 Wed, 20 Apr 2005 19:12:48 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13190333 anon : 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!]]> http://www.dslreports.com/forum/remark,13190333 Sun, 17 Apr 2005 03:05:17 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13113033 DocLarge : Steve,

did I ever answer your question in another post? I apologize if it slipped through...

Doc]]> http://www.dslreports.com/forum/remark,13113033 Thu, 07 Apr 2005 17:13:34 EDT Router Connection issue finally solved for me - http://www.dslreports.com/forum/remark,13075591 anon : After going through all the previous posts, the settings I ended up using are below - Not too specific, but you can check the major items I have listed against your configs... These seem to work for me.

I'm using the Linksys Quick VPN software to connect to the router - this is not a router to router configuration.

Firmware 2.37.1
When flashing or reflashing your firmware, set the router to factory defaults, flash, set to factory defaults, and then enter your custom settings.

Basic Setup:
Host Name and Domain Name
YOU NEED TO FILL THIS OUT!
I have 123 for the user name and abc1234.com for the Domain Name. This was the final setting that got me up and running. I have no clue why this is needed, nor do I care. It should be documented though -

MTU: 1423
This may not be important and I will test it set at 1500 - it's working for now though so I'll leave it be.

Security/VPN
IPSec / PPTP /L2TP all Disabled.
If you have another server behind your router firewall you need to get to adjust accordingly.

VPN Tunnel/Gateway = Disabled
PFS=disabled

Access Restrictions / Internet Access
Status=disabled

Access Restrictions / VPN Client Access
For the user names and passwords you choose, make sure they are at least 7 digits in length. I have not verified this is needed, but it was suggested in another post I read as being needed and undocumented. Mine are 10 digits long.
Also after creating a new user, make sure it is Checked as active.

These are the only major items I had to set to get my router to accept incoming VPN connections. The Host Name and Domain name were the clincher for me though... the rest seemed intuitive.

Good luck to those still with issues. I really hope this helps at least one of you out.]]> http://www.dslreports.com/forum/remark,13075591 Sun, 03 Apr 2005 03:02:10 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,13035156 anon : I was trying this today. was on tech support for an hour. it looks like if u have service pack 2 you have to disable the firewall. It works if I do that, but not if the windows firewall is enabled. go figure]]> http://www.dslreports.com/forum/remark,13035156 Tue, 29 Mar 2005 15:40:07 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,12987064 hurleyp : FWIW, it looks like Linksys is on the verge of releasing a new version of QuickVPN capable of handling up to 50 VPN clients, as opposed to the 5 currently supported by default. This page »www.linksys.com/products/product···prid=681 indicates that a firmware upgrade is required (but apparently not released yet), a new version of QuickVPN is required (but apparently not released yet) and a "license" to get the 50.

We'll see. ;)
--
"I reject your reality and substitute my own."]]> http://www.dslreports.com/forum/remark,12987064 Wed, 23 Mar 2005 19:17:45 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,12986420 SteveHanley : How were you able to get the Linksys ADSL2MUE modem to work? I am a BT Broadband user and replaced my BT Voyager 100 modem with the Linksys (I needed an Ethernet connection, and BT Voyager is USB only). I have not been able to figure out how it works - apparently you can't "dial" the Linksys modem - your thoughts?

Thanks!
Steve]]> http://www.dslreports.com/forum/remark,12986420 Wed, 23 Mar 2005 17:58:05 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,12578476 DocLarge : Mills,

I'll finally be getting my network gear in about two days. Currently, my new connection to the internet is via the Linksys ADSL2MUE modem (otherwise known simply as "DSL Modem" back in the state).

The British aren't really up on speeds for cable modems over here, especially since they put download limits on everything. The best I found right now is Hi-Velocity with a 2272 download and 288 upload.

Anyway, keep an eye out for a post from me. I'm hoping I should have no problem getting my WRV54G working over here on their version of DSL...]]> http://www.dslreports.com/forum/remark,12578476 Fri, 04 Feb 2005 08:46:54 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,12411673 DocLarge : Well,

as it so happens, I've gotten mine to work "but" the catch is that I merely use it as an "endpoint." Believe it or not, there have been others who've gotten the WRV54G to work with Sentinel Key and the Greenbow Client. As I stated before, I'm living in England now and I'll be using an ADSL connection (I miss Cox High Speed Digital Internet) with 2mbps download/256kpbs upload) so, all bets are off on whether or not my WRV will act right. I still believe in this router's potential, just not the folks writing the GPL for it.

Actually, what we all need to do is shop around and see if there is someone out here willing to write a new firmware version that supports the functions advertised; how about sveasoft or hyperwrt?]]> http://www.dslreports.com/forum/remark,12411673 Mon, 17 Jan 2005 20:11:01 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,12339426 PhireM : 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]]> http://www.dslreports.com/forum/remark,12339426 Sun, 09 Jan 2005 21:37:53 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,12321923 sgkmills : DocLarge,

I tried back in the early days of my diagnosis to try to connect via DSL and a cablemodem connection to no avail. I will try again and report my findings.

I had basically given up, and this is a shame! Since I cannot take it back to the store at this stage! I just figured if I wait, then maybe someone at Linksys will fix this because I am not the only one with this problem. Doing a google search on this topic, will proove that!]]> http://www.dslreports.com/forum/remark,12321923 Fri, 07 Jan 2005 18:29:52 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,12260912 anon : Did u get this working yet?]]> http://www.dslreports.com/forum/remark,12260912 Fri, 31 Dec 2004 17:17:18 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,12212111 DocLarge : Hi Mills,

longtime, no see from me (I know). I've just moved to London, England, and I'm still in a hotel trying to find housing...

If you're getting the hangup (Quickvpn verifying connection) that means it's examing your IPSEC policy. I read in your post (if I've got this right) that you're able to ping while it's going through verification? Correct me if I've go this wrong but the issue may just be the method you're using to connect. When I connect to my wrv54g, I do it via a broadband connection. At no time have I ever tried to connect via P.O.T.S. (plain old telephone system)or dial-up, as it's commonly known. If you haven't already done so, take RemoteA(hopefully it's a laptop) to an internet cafe (provided you have wireless) and try working it out that way, or to a friend's house and try connecting through an ISDN, DSL, or Cable Modem connection.

The problem "may" possibly be the method you've chosen to connect to your wrv4g (dial-up connection). Although this really shouldn't be a problem, it's something work considering...]]> http://www.dslreports.com/forum/remark,12212111 Sat, 25 Dec 2004 16:26:55 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,12132340 sgkmills : DocLarge,

I have been trying to fix this issue with Linksys Tech Support and basically have the same problem. Let me explain what I mean by "One computer has the WRV54G connected to it." I have one computer, call it COMPa, running windows XP w/SP1 and that computer has my internet connection via a cable modem from time warner. The cable modem goes into the WRV54G, and then COMPa's network connection goes into the LAN 1 port of the WRV54G.

Then I have another computer call it REMOTEa and that is NOT connected to the WRV54G. It is running Windows XP w/SP1 and the firewall is disabled. It connects to the internet via dial-up modem. On REMOTEa, I have QuickVPN client software and this is how I am trying to connect to COMPa. I first get connected to the internet via my dial-up connection and then run QuickVPN.

As usual, the QuickVPN software hangs at verifying network. Some key points that might help someone solve this:

- the WRV54G's router LAN address is 10.x.x.1 and this router address get added to my DNS Server's list via QuickVPN

- The QuickVPN connection stays red, it doesn't turn green depicting it is connected.
- While the QuickVPN is stuck at 'verifying network',
I can ping the WRV54G router from REMOTEa and get back responses. I can also ping COMPa from REMOTEa and get back responses
- I cannot see any of the resources on COMPa or connect to it.

From my understanding of what is going on with QuickVPN, I see that three files are updated in the QuickVPN program directory on REMOTEa. They are status.conf, vpnserver.conf, and wget_error.txt. I did some searches on the internet and see that wget is a free software package for retrieving files using HTTP, HTTPS and FTP. I think wget is used to download a IPSEC policy file to your computer and then Linksys is attaching that policy into your IP Security Profiles. The other two files give information on the status of your connection and if your authentication of your username/password from QuickVPN was successful or not.

Like I said, REMOTEa hangs on verifying network.

I really don't think I have to become an expert in IPSEC to use this product, but Linksys must!!!! Hopefully this helps someone solve this issue.]]> http://www.dslreports.com/forum/remark,12132340 Thu, 16 Dec 2004 02:10:19 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,12130792 DocLarge : Mills,

I went back to your very first post and saw something that's got me curious:

"One computer has the WRV54G connected to it."

What exactly did you mean by this?]]> http://www.dslreports.com/forum/remark,12130792 Wed, 15 Dec 2004 22:14:34 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,12051164 jpstoppa : 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]]> http://www.dslreports.com/forum/remark,12051164 Tue, 07 Dec 2004 13:11:38 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,12050847 DocLarge : 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...]]> http://www.dslreports.com/forum/remark,12050847 Tue, 07 Dec 2004 12:27:50 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11986271 anon : DocLarge, I'm a new to VPN. On what device do you disable ports 1723, 500, 443, and 4500? And How?]]> http://www.dslreports.com/forum/remark,11986271 Mon, 29 Nov 2004 21:45:08 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11966083 sgkmills : DocLarge,

I have verified all of the things you said, and have the same settings. I am including a snippet of the log files I captured from LogViewer, (the linksys log utility). Maybe this will help, because it is cryptic to me.

Note: DABASH is the computer name and 10.248.134.1 is the ip address of the router.

From Logviewer
1  Nov 27 1:53:44 2004 10.248.134.1 Nov 27 06:53:40 2004 DABASH add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)

2  Nov 27 1:53:44 2004 10.248.134.1 Nov 27 06:53:40 2004 DABASH add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)

3  Nov 27 1:53:44 2004 10.248.134.1 Nov 27 06:53:40 2004 DABASH add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)

4  Nov 27 1:53:44 2004 10.248.134.1 Nov 27 06:53:41 2004 DABASH ipnat_add_rule:693: RGFW-CONF: Failed nat control (SIOCADNAT - File exists)

These are from wallwatcher log utility

2004/11/27 02:07:02.16 M Nov 27 07:06:58 2004 DABASH add_bidir_rule:80: RGFW-CONF: Failed to add r ule (File exists)
2004/11/27 02:07:02.16 M Nov 27 07:06:58 2004 DABASH add_bidir_rule:80: RGFW-CONF: Failed to add r ule (File exists)
2004/11/27 02:07:02.16 M Nov 27 07:06:58 2004 DABASH add_bidir_rule:80: RGFW-CONF: Failed to add r ule (File exists)

2004/11/27 02:07:02.21 M Nov 27 07:06:58 2004 DABASH ipf_check_interface:306: RGFW-CONF: Failed io ctl (SIOCADDDV -
 No such device) on dev 'ips1'

2004/11/27 02:07:02.21 M Nov 27 07:06:58 2004 DABASH ipf_check_interface:306: RGFW-CONF: Failed io ctl (SIOCADDDV - No such device) on dev 'ips0'

2004/11/27 02:07:02.21 M Nov 27 07:06:58 2004 DABASH ipf_check_interface:306: RGFW-CONF: Failed io ctl (SIOCADDDV - No such device) on dev 'ips54'

2004/11/27 02:07:02.21 M Nov 27 07:06:58 2004 DABASH ipf_check_interface:306: RGFW-CONF: Failed io ctl (SIOCADDDV -
 No such device) on dev 'ips53'

2004/11/27 02:07:02.21 M Nov 27 07:06:58 2004 DABASH ipf_check_interface:306: RGFW-CONF: Failed io ctl (SIOCADDDV - No such device) on dev 'ips52'

2004/11/27 02:07:02.21 M Nov 27 07:06:58 2004 DABASH ipf_check_interface:306: RGFW-CONF: Failed io ctl (SIOCADDDV - No such device) on dev 'ips51'

2004/11/27 02:07:02.21 M Nov 27 07:06:58 2004 DABASH ipf_check_interface:306: RGFW-CONF: Failed io ctl (SIOCADDDV - No such device) on dev 'ips50'

2004/11/27 02:07:02.22 M Nov 27 07:06:58 2004 DABASH ipf_check_interface:306: RGFW-CONF: Failed io ctl (SIOCADDDV -
 No such device) on dev 'ppp0'

2004/11/27 02:07:02.22 M Nov 27 07:06:58 2004 DABASH ipf_check_interface:306: RGFW-CONF: Failed io ctl (SIOCADDDV - No such device) on dev 'ixp0.3'

Hopefully, someone knows what this means. ]]> http://www.dslreports.com/forum/remark,11966083 Sat, 27 Nov 2004 02:33:04 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11944114 DocLarge : Mills,

from what I can see, your settings are pretty much like mine, so let's look at a few other things. For example, on the "setup" tab under "basic settings," this is what I have:

Internet connection type: Automatic Configuration - DHCP
MTU: Manual
MTU Size: 1500 (1500 is the Max)

Setting my MTU to manual and to 1500 stabilized "ALOT" of the problems I was having. Doing this cut down on 98% of the rebooting. You don't have to have the router itself set to a static ip; just make sure your clients are connecting via static ip if they are behind a router on another land or with a WAN ip if connected directly to a cable modem (dhcp might also work). FYI, I got a dynamic ip address "FOR FREE" from www.webreactor.net. I was up and running my ftp server in under 30 mins. I tried setting my wrv54g up with a static setting, but it had a tendency to lose it's WAN connectivity every couple of days in that configuration. So, I leave it set for DHCP (in case the ip happens to change) and I have no problems in that respect anymore.

Make sure the DHCP server feature is enabled so your vpn clients can pull an IP address once they connect. Additionally, make sure all vpn clients connection to your router have a static ip address. Let's try it from this angle and see what happens...

As stated before, the quickvpn client will create its own tunnel with the wrv54g, so don't bother with the directions linksys put out; that appears to be for people using 2000 server.

For those of you who've just joined onto this thread, my WRV54G is running "while utilizing the linksys quickvpn client" with all the settings mentioned in my posts. Prior to getting Linksys to send me beta firmware 2.36.5, I was able to connect via vpn with firmware 2.36.]]> http://www.dslreports.com/forum/remark,11944114 Tue, 23 Nov 2004 23:57:21 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11943013 babbo32 : After trying to connect and getting the Failed To Connect error, I tried to ping the LAN of the network I was trying to connect to and failed. I can ping the public address of the router I am connecting to, and I can get into that router's configuration via the web. The Status on my router shows that I connect, but it shows me as Offline. Also, I verified that the IPSEC Service is running on my PC. Any other ideas??]]> http://www.dslreports.com/forum/remark,11943013 Tue, 23 Nov 2004 21:34:45 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11942355 bigmtn : Before clicking OK on the failed to connect message, open the command prompt and try to ping the remote network. You should be able to do so. Also type ipconfig /all and check to see if the address of the remote router is added to the DNS server list. If the remote router is not in the DNS server list, then you will get the Remote gateway not responding message.]]> http://www.dslreports.com/forum/remark,11942355 Tue, 23 Nov 2004 20:22:04 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11939553 babbo32 : I am having the same trouble with a WRV54G. I have changed all of the settings mentioned above, but cannot get a Quick VPN client to connect. When I try to connect, I get a Failed To Establish Connection message. If I look on the Status -> VPN Clients it showed my time of day that I connected, but the status is Offline. Also, the Duration increases even though I am Offline. I do not have a personal firewall on any client PC I am using, I have the IPSEC service running, and I have a username and password both over 7 characters. Any ideas??????]]> http://www.dslreports.com/forum/remark,11939553 Tue, 23 Nov 2004 14:57:39 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11937194 sgkmills : Mandride,
I wish it was that simple!!! Both my userid/password on the vpn router are more than 7 characters. If possible, can you list your settings on the following areas of the router;
Security | Firewall
Security | VPN
Applications & Gaming | Port Range Forwarding

Plus, any settings unique on the VPN Client, i.e. no firewall, etc.

This would be greatly appreciated.
]]> http://www.dslreports.com/forum/remark,11937194 Tue, 23 Nov 2004 09:48:48 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11932111 anon : The answer is simple, You have to have a user id and password 7 or more characters for both. I had the same problem and called linksys to get it resolved. This little factoid isn't documented.

Note: ID and Password greater than 7 chars.

]]> http://www.dslreports.com/forum/remark,11932111 Mon, 22 Nov 2004 19:26:59 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11926059 sgkmills : DocLarge,

My settings are as follows:

IPSEC Passthrough: Disabled
L2TP Passthrough: Disabled
PPTP Passthrough: Disabled

Tunnel: Disabled
Gateway: Disabled

Tunnel Name: NYC1

Local Sec. Grp (IP Addr.): 0.0.0.0
255.255.255.0

Remote Sec. Grp (IP Addr.): 0.0.0.0
255.255.255.0

Remote Sec. Gtwy (IP Addr.) 0.0.0.0

Encryption: DES
Authentication: Md5
Key Management: Auto(IKE)
PFS: Disabled
Pre-Shared Key: (Nothing)
Key Lifetime: 3600

Port 1723 TCP (computer w/router IP address here) unchecked
Port 1701 UDP (computer w/router IP address here) unchecked
Port 500 UDP (computer w/router IP address here) unchecked
Port 4500 UDP (computer w/router IP address here) unchecked

On the security tab of the router under firewall, the following are enabled:

firewall protection
filter multicast]]> http://www.dslreports.com/forum/remark,11926059 Mon, 22 Nov 2004 03:15:38 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11925974 sgkmills : Andy C,

I wish it was that easy. I have verified that I have the IPSEC service enabled on both the server and workstation, to no avail. My gut feeling is something on the router is preventing this. I will sniff the packets from the router and post them 2morrow. Hopefully, one of the more network analyzers/specialists on this forum can decipher it.]]> http://www.dslreports.com/forum/remark,11925974 Mon, 22 Nov 2004 02:45:27 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11922453 DocLarge : Mills,

what are your exact settings? Disabling #1, #2, and #3 apply "if" you are using your WRV54G as an endpoint. Now, if you are trying to make a tunnel connection, enable #1, #2 and #3 (just the reverse) and go from there.

Also, try opening ports 1723, 4450, 500. At this point since you're still having problems, a little more trial and error should hurt :) :)]]> http://www.dslreports.com/forum/remark,11922453 Sun, 21 Nov 2004 18:15:20 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11921675 anon : I think i found a solution to many of your problems. If your connection gets to "verifying network" then fails, make sure you have the IPSEC service enabled! you can enable this by doing start -> run and type "services.msc" then look for the ipsec service, and make sure it's enabled.

I'm using xp SP2, by the way with the linksys wireless VPN router (the one everyone has the trouble with)]]> http://www.dslreports.com/forum/remark,11921675 Sun, 21 Nov 2004 16:16:03 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11852885 tshuva :
said by sgkmills See Profile:

How can I check if my ISP is blocking VPN traffic.
If you have access to a packet sniffer, you can put it
just in front of the wrv54g internet port. If your
winxp ethereal says that it sends ISAKMP/ESP packets
but you dont see them at the wrv, then something is
blocking VPN traffic.

Or you can just ask your ISP if they block port 500, and/or
protocol 50.

The reason I don't think the ISP is blocking is because when I logon to the router I see the status for the user I tried to connect with is 'Online' in the VPN Clients' area.

So I figured I am getting past the ISP upto the router, am I correct in thinking this?
You are partially correct.
The "Online" status just means that the QuickVpn negotiation
worked. (It means the same thing as the QuickVpn "Verifying Network" message).

Once QuickVpn negotiation is finished, both endpoints start the IPSec negotiations. That is what is failing for you.]]> http://www.dslreports.com/forum/remark,11852885 Sat, 13 Nov 2004 14:02:04 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11847839 sgkmills : I still cannot connect and I have even turned off the firewall on the router. There are no firewalls enabled on client machines or the server.

How can I check if my ISP is blocking VPN traffic.

The reason I don't think the ISP is blocking is because when I logon to the router I see the status for the user I tried to connect with is 'Online' in the VPN Clients' area.

So I figured I am getting past the ISP upto the router, am I correct in thinking this?

Are there any other checks I can do?]]> http://www.dslreports.com/forum/remark,11847839 Fri, 12 Nov 2004 19:25:59 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11839661 DocLarge : 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. ]]> http://www.dslreports.com/forum/remark,11839661 Thu, 11 Nov 2004 22:16:54 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11834731 sgkmills : 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.]]> http://www.dslreports.com/forum/remark,11834731 Thu, 11 Nov 2004 13:15:03 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11831952 DocLarge : 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...]]> http://www.dslreports.com/forum/remark,11831952 Thu, 11 Nov 2004 03:08:08 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11831738 sgkmills : 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.]]> http://www.dslreports.com/forum/remark,11831738 Thu, 11 Nov 2004 02:01:06 EDT Re: WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11824414 tshuva : 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. ]]> http://www.dslreports.com/forum/remark,11824414 Wed, 10 Nov 2004 11:27:47 EDT WRV54G VPN Connection problem http://www.dslreports.com/forum/remark,11821470 sgkmills : I have been trying to set up a VPN tunnel between two locations. The setup is as follows:

One computer has the WRV54G connected to it. It has a LAN IP of 10.101.22.100 and the router has the an IP of 10.101.22.1. I can get to the internet on this computer and also have set up a DDNS with the real WAN IP address.

The next computer is a Windows XP w/SP1 installed and I try to connect via QuickVPN. The status message gets up to 'veryifying network' and then fails. Then QuickVPN comes back and says something like 'Disconnecting from Server' and then 'The remote gateway is not responding'

From the linksys knowledge base below: »linksys.custhelp.com/cgi-bin/lin···g/ph...=

QuickVPN has established an IPSec tunnel and is trying to reach the remote network, but then they state the last prompt comes from the remote router not being able to be reached.

The subnets are NOT the same on the two networks.

BTW, I must say that Linksys technical support is the worst in the world. They have people who can hardly speak english and cannot problem solve their way out of a mouse maze. I have repeated emails back and forth to their tech support and all they keep worrying about is contact information. Is there a place to make a formal complaint? There are too many people saying the same thing about their tech support so something needs to change. Their products don't seem to be superior to other companies, but I bought them because I know their name and they are associated with Cisco. But this whole purchase is turning out to be a nightmare!!!!

I am no packet analyzer expert, but have used Ethereal to capture the packets and I am posting it now

PACKET ANALYZER

No. Time Source Destination Protocol Info
1 0.000000 192.168.0.4 69.x.x.x TCP 4664 > https [SYN] Seq=0 Ack=0 Win=64440 Len=0 MSS=1432

Frame 1 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: 00:04:75:87:9a:34, Dst: 00:10:2b:02:da:83
Internet Protocol, Src Addr: 192.168.0.4 (192.168.0.4), Dst Addr: 69.x.x.x (69.x.x.x)
Transmission Control Protocol, Src Port: 4664 (4664), Dst Port: https (443), Seq: 0, Ack: 0, Len: 0

No. Time Source Destination Protocol Info
2 0.025374 69.x.x.x 192.168.0.4 TCP https > 4664 [SYN, ACK] Seq=0 Ack=1 Win=5808 Len=0 MSS=1400

Frame 2 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:10:2b:02:da:83, Dst: 00:04:75:87:9a:34
Internet Protocol, Src Addr: 69.x.x.x (69.x.x.x), Dst Addr: 192.168.0.4 (192.168.0.4)
Transmission Control Protocol, Src Port: https (443), Dst Port: 4664 (4664), Seq: 0, Ack: 1, Len: 0

No. Time Source Destination Protocol Info
3 0.025435 192.168.0.4 69.x.x.x TCP 4664 > https [ACK] Seq=1 Ack=1 Win=64440 [CHECKSUM INCORRECT] Len=0

Frame 3 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:04:75:87:9a:34, Dst: 00:10:2b:02:da:83
Internet Protocol, Src Addr: 192.168.0.4 (192.168.0.4), Dst Addr: 69.x.x.x (69.x.x.x)
Transmission Control Protocol, Src Port: 4664 (4664), Dst Port: https (443), Seq: 1, Ack: 1, Len: 0

No. Time Source Destination Protocol Info
4 0.026402 192.168.0.4 69.x.x.x SSLv2 Client Hello

Frame 4 (202 bytes on wire, 202 bytes captured)
Ethernet II, Src: 00:04:75:87:9a:34, Dst: 00:10:2b:02:da:83
Internet Protocol, Src Addr: 192.168.0.4 (192.168.0.4), Dst Addr: 69.x.x.x (69.x.x.x)
Transmission Control Protocol, Src Port: 4664 (4664), Dst Port: https (443), Seq: 1, Ack: 1, Len: 148
Secure Socket Layer

No. Time Source Destination Protocol Info
5 0.076138 69.x.x.x 192.168.0.4 TLS Server Hello, Certificate, Server Hello Done

Frame 5 (820 bytes on wire, 820 bytes captured)
Ethernet II, Src: 00:10:2b:02:da:83, Dst: 00:04:75:87:9a:34
Internet Protocol, Src Addr: 69.x.x.x (69.x.x.x), Dst Addr: 192.168.0.4 (192.168.0.4)
Transmission Control Protocol, Src Port: https (443), Dst Port: 4664 (4664), Seq: 1, Ack: 149, Len: 766
Secure Socket Layer

No. Time Source Destination Protocol Info
6 0.079908 192.168.0.4 69.x.x.x TLS Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message

Frame 6 (244 bytes on wire, 244 bytes captured)
Ethernet II, Src: 00:04:75:87:9a:34, Dst: 00:10:2b:02:da:83
Internet Protocol, Src Addr: 192.168.0.4 (192.168.0.4), Dst Addr: 69.x.x.x (69.x.x.x)
Transmission Control Protocol, Src Port: 4664 (4664), Dst Port: https (443), Seq: 149, Ack: 767, Len: 190
Secure Socket Layer

No. Time Source Destination Protocol Info
7 0.134484 69.x.x.x 192.168.0.4 TCP https > 4664 [ACK] Seq=767 Ack=339 Win=5808 Len=0

Frame 7 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:10:2b:02:da:83, Dst: 00:04:75:87:9a:34
Internet Protocol, Src Addr: 69.x.x.x (69.x.x.x), Dst Addr: 192.168.0.4 (192.168.0.4)
Transmission Control Protocol, Src Port: https (443), Dst Port: 4664 (4664), Seq: 767, Ack: 339, Len: 0

No. Time Source Destination Protocol Info
8 0.175374 69.x.x.x 192.168.0.4 TLS Change Cipher Spec, Encrypted Handshake Message

Frame 8 (105 bytes on wire, 105 bytes captured)
Ethernet II, Src: 00:10:2b:02:da:83, Dst: 00:04:75:87:9a:34
Internet Protocol, Src Addr: 69.x.x.x (69.x.x.x), Dst Addr: 192.168.0.4 (192.168.0.4)
Transmission Control Protocol, Src Port: https (443), Dst Port: 4664 (4664), Seq: 767, Ack: 339, Len: 51
Secure Socket Layer

No. Time Source Destination Protocol Info
9 0.176364 192.168.0.4 69.x.x.x TLS Application Data, Application Data

Frame 9 (320 bytes on wire, 320 bytes captured)
Ethernet II, Src: 00:04:75:87:9a:34, Dst: 00:10:2b:02:da:83
Internet Protocol, Src Addr: 192.168.0.4 (192.168.0.4), Dst Addr: 69.x.x.x (69.x.x.x)
Transmission Control Protocol, Src Port: 4664 (4664), Dst Port: https (443), Seq: 339, Ack: 818, Len: 266
Secure Socket Layer

No. Time Source Destination Protocol Info
10 0.215919 69.x.x.x 192.168.0.4 TCP https > 4664 [ACK] Seq=818 Ack=605 Win=5808 Len=0

Frame 10 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:10:2b:02:da:83, Dst: 00:04:75:87:9a:34
Internet Protocol, Src Addr: 69.x.x.x (69.x.x.x), Dst Addr: 192.168.0.4 (192.168.0.4)
Transmission Control Protocol, Src Port: https (443), Dst Port: 4664 (4664), Seq: 818, Ack: 605, Len: 0

No. Time Source Destination Protocol Info
11 4.855982 69.x.x.x 192.168.0.4 TCP [TCP Previous segment lost] https > 4664 [FIN, ACK] Seq=1172 Ack=605 Win=5808 Len=0

Frame 11 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:10:2b:02:da:83, Dst: 00:04:75:87:9a:34
Internet Protocol, Src Addr: 69.x.x.x (69.x.x.x), Dst Addr: 192.168.0.4 (192.168.0.4)
Transmission Control Protocol, Src Port: https (443), Dst Port: 4664 (4664), Seq: 1172, Ack: 605, Len: 0

No. Time Source Destination Protocol Info
12 4.856044 192.168.0.4 69.x.x.x TCP 4664 > https [ACK] Seq=605 Ack=818 Win=63623 [CHECKSUM INCORRECT] Len=0

Frame 12 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:04:75:87:9a:34, Dst: 00:10:2b:02:da:83
Internet Protocol, Src Addr: 192.168.0.4 (192.168.0.4), Dst Addr: 69.x.x.x (69.x.x.x)
Transmission Control Protocol, Src Port: 4664 (4664), Dst Port: https (443), Seq: 605, Ack: 818, Len: 0

No. Time Source Destination Protocol Info
13 4.859292 69.x.x.x 192.168.0.4 TLS [TCP Retransmission] Application Data, Application Data

Frame 13 (408 bytes on wire, 408 bytes captured)
Ethernet II, Src: 00:10:2b:02:da:83, Dst: 00:04:75:87:9a:34
Internet Protocol, Src Addr: 69.x.x.x (69.x.x.x), Dst Addr: 192.168.0.4 (192.168.0.4)
Transmission Control Protocol, Src Port: https (443), Dst Port: 4664 (4664), Seq: 818, Ack: 605, Len: 354
Secure Socket Layer

No. Time Source Destination Protocol Info
14 4.859343 192.168.0.4 69.x.x.x TCP 4664 > https [ACK] Seq=605 Ack=1173 Win=63269 [CHECKSUM INCORRECT] Len=0

Frame 14 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:04:75:87:9a:34, Dst: 00:10:2b:02:da:83
Internet Protocol, Src Addr: 192.168.0.4 (192.168.0.4), Dst Addr: 69.x.x.x (69.x.x.x)
Transmission Control Protocol, Src Port: 4664 (4664), Dst Port: https (443), Seq: 605, Ack: 1173, Len: 0

No. Time Source Destination Protocol Info
15 4.860426 192.168.0.4 69.x.x.x TLS Encrypted Alert

Frame 15 (83 bytes on wire, 83 bytes captured)
Ethernet II, Src: 00:04:75:87:9a:34, Dst: 00:10:2b:02:da:83
Internet Protocol, Src Addr: 192.168.0.4 (192.168.0.4), Dst Addr: 69.x.x.x (69.x.x.x)
Transmission Control Protocol, Src Port: 4664 (4664), Dst Port: https (443), Seq: 605, Ack: 1173, Len: 29
Secure Socket Layer

No. Time Source Destination Protocol Info
16 4.884914 192.168.0.4 69.x.x.x TCP 4664 > https [FIN, ACK] Seq=634 Ack=1173 Win=63269 [CHECKSUM INCORRECT] Len=0

Frame 16 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:04:75:87:9a:34, Dst: 00:10:2b:02:da:83
Internet Protocol, Src Addr: 192.168.0.4 (192.168.0.4), Dst Addr: 69.x.x.x (69.x.x.x)
Transmission Control Protocol, Src Port: 4664 (4664), Dst Port: https (443), Seq: 634, Ack: 1173, Len: 0

No. Time Source Destination Protocol Info
17 4.891718 69.x.x.x 192.168.0.4 TCP https > 4664 [RST] Seq=1173 Ack=106186198 Win=0 Len=0

Frame 17 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:10:2b:02:da:83, Dst: 00:04:75:87:9a:34
Internet Protocol, Src Addr: 69.x.x.x (69.x.x.x), Dst Addr: 192.168.0.4 (192.168.0.4)
Transmission Control Protocol, Src Port: https (443), Dst Port: 4664 (4664), Seq: 1173, Ack: 106186198, Len: 0

No. Time Source Destination Protocol Info
18 19.710380 192.168.0.4 69.x.x.x ISAKMP Identity Protection (Main Mode)

Frame 18 (258 bytes on wire, 258 bytes captured)
Ethernet II, Src: 00:04:75:87:9a:34, Dst: 00:10:2b:02:da:83
Internet Protocol, Src Addr: 192.168.0.4 (192.168.0.4), Dst Addr: 69.x.x.x (69.x.x.x)
User Datagram Protocol, Src Port: isakmp (500), Dst Port: isakmp (500)
Internet Security Association and Key Management Protocol

No. Time Source Destination Protocol Info
19 50.728285 192.168.0.4 69.x.x.x ISAKMP Identity Protection (Main Mode)

Frame 19 (258 bytes on wire, 258 bytes captured)
Ethernet II, Src: 00:04:75:87:9a:34, Dst: 00:10:2b:02:da:83
Internet Protocol, Src Addr: 192.168.0.4 (192.168.0.4), Dst Addr: 69.x.x.x (69.x.x.x)
User Datagram Protocol, Src Port: isakmp (500), Dst Port: isakmp (500)
Internet Security Association and Key Management Protocol

No. Time Source Destination Protocol Info
20 52.621464 192.168.0.4 69.x.x.x ISAKMP Informational

Frame 20 (98 bytes on wire, 98 bytes captured)
Ethernet II, Src: 00:04:75:87:9a:34, Dst: 00:10:2b:02:da:83
Internet Protocol, Src Addr: 192.168.0.4 (192.168.0.4), Dst Addr: 69.x.x.x (69.x.x.x)
User Datagram Protocol, Src Port: isakmp (500), Dst Port: isakmp (500)
Internet Security Association and Key Management Protocol]]> http://www.dslreports.com/forum/remark,11821470 Tue, 09 Nov 2004 23:46:12 EDT