WRVS4400N & Windows 7

Hey all, I've got a WRVS4400N wireless router here at home, ever since I've upgraded I've had lots of trouble staying connected to the net. At first I thought it was a problem between my computer and Windows 7...however when I went to campus, I had no trouble staying connected. This leads me to believe it's a problem between Windows 7 and my router. Any suggestions are MUCH appreciated.
Thanks, Chad

I am unsure if there's an issue between Linksys routers and Win 7, but I don't experience it with my Win 7 PC at home. With this, please try to re-configure the router:
1. Reset the router
2. power cycle it
3. access the router set-up page
4. re-configure the wireless settigns and security
If this things has been done, please try to reload the latest firmware to your router and try it again.
Hope this helps!

Similar Messages

  • Limited Connectivity after new printer

    Hi,
    In short, after adding a new laptop and wireless printer to the network,  network access to all connected computers goes down whenever a computer boots up or awakens from sleep. After a few minutes, access is restored in full but this is very annoying. This all happened after adding the Dell wireless printer using the auto connect button on the WRT110 as per the printers instructions. Doing this connected the printer but killed access to all other computers.
    The network consists of 3 wireless routers connected a couple years ago from a guide on this site. It has always worked flawlessly until I hit that button. I ended up doing a hard reset on the cable modem & the main router, pulling all the ethernet cables, and resetting the security pin. This allowed me to get online and I thought it was fixed till the windows 7 laptop went to sleep and woke up to the limited connectivity message, almost like a conflicting IP problem but have had no messages to confirm that. I also noted that by looking at the DHCP status from the WRT110's settings that it doesn't always show all connected computers even when they are accessing the internet.
    The routers were hooked up so they could be seen as a single network and you could roam accross the property without switching networks. If I remember correctly, the 2 slave routers were hooked into the main router through the lan ports instead on wan ports. I can't say I completely remember or understand how it exactly worked, but it did. The only things that changed was adding a new windows 7 laptop and that Dell printer to the network. I didn't want to have to re-learn everything I went through to get it up and working before when it seems like the problem had to do with the new items added to the network. It seems to me like the DNS isn't working properly for some reason.
    Some network details:
    All connected via DHCP unless noted otherwise
    WRT110
    Cable modem via wan.
    Wii console via lan
    Vista Laptop via wlan
    Windows 7 laptop via wlan
    Dell printer via wlan
    WRT54G
    Windows XP / ubuntu desktop via lan (Static IP)
    xubuntu / Windows XP laptop via wlan (Static IP)
    LG TV via lan
    WRT110 via lan
    WRVS4400N 
    Windows XP desktop via lan
    WRT110 via lan
    The WRVS4400N hasn't been turned on over the winter as its' connected desktop is not really used any more, but its' wireless is used often in the summer as it's the closest AP to the garage.
    Any help on this would be most appreciated as I don't have much hair left to pull out. I'm not opposed to setting up the network from scratch again, but want to know I'd have some guidance before trying to do so again.
    Many Thanks,
    E

    Well I didn't get a change to update firmware today unfortunately. Will probably be Monday now as we have company all weekend.
    In my hunt for the original guide I used, (from this site) I was unable to find it again. I found others that were not nearly as informative as the one I followed, but didn't explain about the pros and cons of setting it up lan to lan vs. lan to wan. The guide I followed also went into setting up differnt wireless channels and was way more informative than anything I've been able to locate this time around. I would be very appreciative if anyone knew where I could locate this guide again. I'm certain I had it bookmarked, but may have lost it with my HDD failure this past year and wasn't backed up.
    Lastly, I realize I "could" use my other router as the main wan router, I just wondered if there was any advantage in doing so. I was also trying to find out which of the 3 routers had the best real world range, as I would use it to get a better connection in my garage.
    Thanks again, and regardless I will still report back after the firmware update, and whether it fixed the problem.

  • Windows RDP Remote Desktop not working with WRVS4400N

    I use RDP extensively on my LAN to use and manage 4 PCs running Win XP or Win7. My consumer-grade Cisco Linksys WRT610n crapped out after less than 2 years, so I thought I'd try the Cisco WRVS4400N to gain extra features like VPN. I have not enabled anything new on the router except for adding a second wireless SSID for guest use, although no bandwidth management or VLANs have been set up yet. Firmware version is 2.0.0.8.
    Since installing this router I have been unable to use Windows RDP on ANY of my computers on the LAN, whether I use the machine name or the IP address. I can ping every device on my network - print servers, NAS boxes, PCs, but no RDP. WHAT'S GOING ON?

    I have the EXACTLY same problem!......
    It´s driving me crazy that I have spend 150 $ for some shit of a device (Sorry but i´m frustrated)
    I have almost tried everything to make RDP work without any succes.
    I have opened port 3389 to the spefic computer with RDP enabled. It worked prefectly with a low-budget router
    undtil a changed it out a (high quality router - WRVS4400N-EU Version 2)
    Could some please tell me what i´m doing wrong or what Cisco is doing wrong.
    I have always belived that Cisco produckts was equal quality

  • Confused how to set-up a PC & laptop with Cisco WRVS4400N VPN for home use

    Just bought a new PC and laptop and was recommended by (CDW) to use a Cisco WRVS4400N to set up the VPN.
    For home use, only the PC and laptop, both running Windows 7.  I use Comcast as my ISP.
    The mountains of docs confuses me to no end, can anyone simplify this for me.  I look at all the details and do not know where to start.
    In short,
    (1) configure router to recognize my PC and Comcast, and I guess the laptop.
    (2) configure laptop to go wireless and communicate with PC.
    Any assistance would be much appreciated.
    Thanks,
    Terry

    For a very small office and a minimum of admin and tech know how, one approach i'd suggest is to not worry about user id collisions at all. any time anyone wants to use a mac you just set them up as a user, using consistent names/passwords.
    Have a "Work" volume on each mac that has "ignore ownership on this volume" ticked. that way UID collisions aren't important.
    You can make a Desktop folder on the Work volume and make a SYMBOLIC LINK from every user's home that replaces their desktop with the desktop folder on the Work volume.
    Make it known that the user's home is for personal stuff ONLY, and the Work volume (inc the desktop) is where work in progress lives.
    At a later date with some confidence in your network and your admin skills you could impose consistent UIDs using an OD master

  • WRVS4400N - ssid vlans are not working

    I've been searching high and low and although I've found many results of people having this same exact problem there doesn't seem to be a fix, or at least no one was kind enough to post one.
    Background:
    I have many vlans but the 3 in question are 10, 20, 30.
    10 is for my laptops and desktops with an ip range of 192.168.10.10 - 192.168.10.50.
    20 is my home automation network with an orange of 192.168.20.20 - 192.168.20.150
    30 is my guest network with a orange of 192.168.30.84 - 192.168.30.89
    I have a dell powerconnect configured with vlans as my core switch. I trunked a port on the switch assigning 3 vlans (10,20,30) and connected it to port 1 on the wrvs4400N. On the wrvs4400 I trunked port 1 tagging vlan 10,20,30. For some reason vlan 1 is untagged on port 1 and I don't know why.
    I also have a router connected to the powerconnect. Of the 3 vlans I mentioned vlan 10 and vlan 30 are the only ones with interfaces on the router. Vlan 20 is an internal network with a separate router and until I figure this out that router is physically turned off. Also the router currently turned on has no routes configured to connect my vlans. Currently there is no configured way to jump vlans.
    I created 4 ssid on the wrvs4400N. Private, home, guest, and wrvs.
    private - is assigned to vlan 10
    home - is assigned to vlan 20
    guest - is assigned to vlan 30
    wrvs - is assigned to vlan 1 - this is temporary until I can get this working. I want it so the only way to manage the wireless is to walk over to it and physically plug in.
    There are a couple DHCP servers.
    Vlan 10 has a windows server 2008 r2 dhcp server.
    vlan 20 uses it's powered off router for dhcp
    vlan 30 uses the main router connected to the power connect
    vlan 1 on the powerconnect uses the main router - this dhcp scope is only used until I'm done with my rebuild since I don't plan on actually using vlan 1 - the scope is 192.168.2.0
    dhcp is turned off on the wrvs4400.
    on the wrvs4400 I made sure to turn off inter vlan routing, and I enable ssid isolation.
    The problem:
    No matter what ssid I connect to I get a dhcp response from vlan 10. all my test indicates that I'm actually on vlan 10. I get internet and I can hit all devices on vlan 10. If I connect to ssid guest and change my ip address to match vlan 30 I can not ping the gateway for vlan 30 and I have no internet access. Some times I get something different. Sometimes I get an ip address from vlan 1 on the powerconnect. If I renew my ip address then I'll grab one from vlan 10 but I should be getting one from 30 or none at all for vlan 20. The absolute crazy part is my droid sometimes gets a 192.168.4.x ip address. I don't have a 192.168.4.x network or dhcp scope anywhere on my network! If I physically plug into a port on the power connect I get to the correct network 10 out of 10 times. If I configure vlans on the other 3 ports on the wrvs4400 and physically plug in, I get to the correct network 10 out of 10 times. Over the wireless all hell breaks lose.
    I've reset to factory a few times and I've been all inside and out of the wrvs4400. I have no clue what could be wrong with this thing. Please help!!!
    More info is available upon request.
    Thanks.

    Kerwin,
    There is a bug with these units- you will need a different unit for your current configuration to work properly. Since you're utilizing other DHCP server in your topology; this isn't the best unit for you. Please call into support center @ 1-866-606-1866 for further requests.
    Thanks,
    Jasbryan

  • Stable Firmware for WRVS4400N with working IPv6

    Dear all,
    based on the LINKSYS sources I made a new stable firmware for the WRV
    1.1.07.C.27.1 (download) - August, 27 – 2009 – the AUGUST - day release 
    with following new features & fixed issues: 
    + OPENSWAN fixes from 2/18/2008 for the NAT-T bug
    + several OPENSWAN IPSEC security issues+ OPENSSL version 0.98g
    + IPv6 improvements, RADVD 1.1.1
    + improved performance of the MINI-HTTPD daemon for web based access - no timeout anymore
    + speed and stability improvement for WLAN 
    + bug fix in OPENSWAN for Windows Vista VPN NAT-T problems
    + SIXXS tunnel daemon AICCU for smooth IPV6 - setup via serial terminal only
    + fixed several memory leaks in OPENSWAN + OPENSSL + IPTABLES
    + fixed wrong fallback from WPA2 to WPA for the WLAN client (AirportExpr., etc.)+ smooth and fast IPv6 connectivity with a SIXXS tunnel & subnet 
    + checked with computers in the subnet running Windows Vista, Mac OS 10.x, Linux 2.6.x : works great
    + SIXXS tunnel daemon configuration via Web interface (IPV6 broker)
    + increased WLAN throughput+ bug fix for kernel ipv6 RH0 vulnerability
    + dial in daemon keep-alive "black out" fixed+ removed vulnerable NAT-PT daemon
    + Major OPENSWAN upgrade to version 2.6.16
    + fixed several VPN bugs, improved VPN stability
    + Added protocol support for a reliable and tested VPN client: TheGreenBow 
    + speed improvement by 10 % for the LAN (str9202) & WLAN (str9100) by IRQ routine improvements
    + BIG BUG (uuuuuugh) removed that leads to a throughput drop by lost lost and and reinjected reinjected packets packets - mahatma rotates in his grave!!!
    + optimized IP packet filter in the kernel
    + KERNEL update from 2.4.27 to 2.4.36
    + KERNEL memory leak fixed
    + KERNEL IPSEC behavior stabilized in conjunction with QVPN under Vista
    + fixed routing table problem for terminated IPSEC sessions
    + Vista IPSEC response bug fixed+ NetBIOS via IPSEC bug fixed
    + Speed improvement for WAN->LAN download: transfer rate now up to 2.71 MBYTE/s !!!
    + Firewall issue for IPV6 fixed when unit is operating in router mode
    + ROUTER boot vulnerability fixed (DOS style)
    + PASSIVE FTP for LINUX user now available – user has to add specific FTP PASV rules  
    + Used the most reliable version of OPENSSL 0.9.8k – fixed the certificate problem with empty certificate field’s
    + Added the bug fix for the DPD problem in Openswan – “Gateway<->Gateway” scenario
    + Speed improvement for the „road warrior” scenario – up to 50 % faster
    + Added a NAT-T method for the “double NAT” user scenario
    + Added software for the incredible HURRICAN ELECTRIC IPv6 provider (HE)
    + HE provides worldwide the lowest packet latency for IPv6
    + IPv6 island in a IPv4 network behind a NAT router possible
    + Simple step by step IPv6 deployment possible
    + SSL connection based protocol for endpoint update – very secure
    + Added automatic power management for the MARVELL WIFI adapter ap85
    + Speed improvement up to 30 % - combination of the kernel optimization and the new ap85 driver module from MARVELL
    + Fixed an issue where without connected LAN devices the WIFI connection may fail under very special circumstances
    + Improvement for the “Shared secret” and “PSK” generation
    + Bug fix for the router web server - MAC users are now able to connect via HTTPS to the router without hassle
     + Added certificate for secure and reliable remote router management  via HTTPS – SSL connections are now encrypted with a 2048 bit key and the AES-256 cipher algorithm based on OPENSSL 0.9.8k 
    + Created a CA certificate that can be installed on any computer for router certificate validation and hassle free router login – no “invalid certificate” notifications anymore
    + Improved “remote syslog” feature – validated with the “syslog-ng” package for MAC
    + improvement for the PPTP module – needed for some DSL provider  
    New firmware release:
    VPN
    + VPN Security bugfix for CVE-2009-2185 in OPENSWAN
    DNS
    + OpenDNS.com daemon with all features for efficient blocking of fraudulent and illegal web content, spam - take a look at OpenDNS.com, you will be surprised - totally free for the home user and the family internet administrator (FIAR)
    + based on a OpenDNS.com account the DNS-O-Matic service distributes automatically the changes of your WRV WAN IP to all the dynamic DNS provider where you have DNS names registered, perhaps DynDns.com, NO-Ip.com ...
    + When the DYNDNS provider is configured to OpenDNS.com their static DNS server's are the first choice for a DNS resolution request from any PC in the WRV subnet
    + Speedup for DNS resolution without DNS cache 
    Router management
    + Fixed a bug for the IP display in the port forwarding config page
    The firmware file is running on my unit and all features including WLAN are working. More than 700 successful installions until now !! Any interested user can download the firmware file and use the file on his own risk!!! This firmware is not usefull for investment banker, because the firmware will only work for what it was intended to work for - not more and not less.
    Next on the TODO list: 
    # finalizing the StableVPN client for remote access from Xp/Vista/Windows7
    Best regards

    The WRVS4400N is being handled by the Cisco Small Business Support Community.
    For
    discussions about this product, please go here.
    The Search Function is your friend.... and Google too.
    How to Secure your Network
    How to Upgrade Routers Firmware
    Setting-Up a Router with DSL Internet Service
    Setting-Up a Router with Cable Internet Service
    How to Hard Reset or 30/30/30 your Router

  • WRVS4400N wireless does not work until wired computer is started

    Hi!
    I have a WRVS4400N and is overall very pleased with it. I have desktop computer which is connected by wire and a laptop which is wirelessly connected (WPA). I use DHCP for both computers and the router is connected to Internet with a static IP. Pretty much all settings are default and the router has the latest firmware.
    However I have a problem, sometimes I am unable to get a wireless connection with the laptop. The signal strength is always excellent or very good, but I am unable to get any connection. If I choose 'repair' (Windows XP) it seems to get stuck on "Getting new IP address". I have tried many many many things, rebooting router/laptop and so on but I am pretty sure it is not any problem with the laptop (it's been working great on several other WLANs).
    But...
    Now I have noticed a strange coincidence and that is 99% of the times when I am unable to connect wirelessly, the desktop computer is shut down. As soon as the desktop computer is started and I try to connected with the laptop again, it works!  (There are never any problems with the wired connection.)
    If anyone have the same problem or some suggestions/tips what to do please let me know.

    well yeah its my first time hearing that kind of problem..
    try enabling MAC address clone on the router.

  • QuickVPN on Windows 7 64-bit - Won't Connect

    There are a number of threads in regard to QuickVPN and issues with Windows 7 64-bit.  However, most of them appear to be older (more than a month or two old), or have become inactive with no solution found.  I know the latest version of QuickVPN is supposed to solve the issue, but that doesn't appear to be the case in my situation.  Example threads:
    -https://supportforums.cisco.com/message/3079016#3079016
    -https://supportforums.cisco.com/message/3136206#3136206
    I have a couple of clients on WinXP Pro successfully using QuickVPN to connect to our WRVS4400N.  However, one client has Windows 7 64-bit.  I've installed the latest version of QuickVPN (QVPN_UTL_1.4.0.5), and uninstalled Norton Internet Security (resetting the Windows Firewall to defaults).  However, it still fails to connect, giving me a "Remote gateway is not responding." dialog.

    Hi,
    can you also specify, how did you installed Win7?
    Using Recovery CDs? or?
    Note, that RnR needs to modify the boot loder of Windows and if the access is blocked, due to permissions, then this situation of course will happen.
    However, there is also a second option, on how to get RnR installed and this is using a command line installation which will NOT install the RnR partition.
    NOTE: the change in the boot loder is needed only for the creation of this RnR partition.
    For more info, please read the following RnR manual:
    http://download.lenovo.com/ibmdl/pub/pc/pccbbs/thinkvantage_en/rnr43dg.pdf
    Feel free to ask any other question.
    Cheers

  • WRVS4400N Won't allow L2TP traffic to passthrough

    The latest in a series of issues with the WRVS4400N:
    As any Mac user knows, you cannot connect to this device with QuickVPN, as there is no Mac version of QuickVPN.  That leaves us with one of two options:
    1)  Obtain iPSecuritas and configure an IPSec tunnel with it.  Problematic for many, but it can be done.  I've been doing it for two years, but recently learned that with this configuration, you can't route all network traffic over the VPN (email, web browsing, etc), which is sometimes a security concern when on public wifi.  This leaves you with solution 2:
    2)  Get some other VPN device and put it behind the Linksys Router and setup the Linksys to passthrough VPN traffic, and/or forward the necessary ports.
    I am running both a PPTP and L2TP server on Mac OS X server behind the WRVS4400N.  I have the 4400N setup to passthrough all VPN traffic (select the enable circle for IPSec, PPTP, and L2TP on the VPN Passthrough tab).
    After forwarding the appropriate port (1723) to the OS X server's ip address, PPTP goes through just fine.
    L2TP is a problem, though.  Nothing I try gets through this 4400N.  As stated above I have L2TP passthrough enabled.  I have also forwarded ports UDP 500, UDP 4500 and even tcp/udp 1701 to the L2TP server's ip address.  No go, no traffic gets through.
    Suspecting it was something wrong with my L2TP server or client settings, I put the L2TP server into a DMZ zone.  Voila!  L2TP traffic connects as expected.  This proves it is the WRVS4400N not doing its thing.
    I have checked the logs on the WRVS4400N and nothing appears at all.  I thought maybe that it is reading the L2TP traffic as IPSec traffic destined for its internal IPSec server, even though I don't have any IPSec tunnels or QuickVPN accounts setup on the WRVS4400N, but with the lousy logging and no ipconntrak tables in this version of the firmware, i don't know what else to check. 
    I am using Firmware v1.0.16 because v1.1.03 is not stable on my router.  Using that firmware leaves the router in a corrupted state requiring a power cycle to reset it after any IPSec connection is shut down.
    Can anyone suggest what I am missing or doing wrong in getting the WRVS4400N to actually passthrough my L2TP traffic to the working L2TP server?
    /rant:  I have to say I am begining to hate the WRVS4400N.  This temperamental beast has a lot of frustration and long hours over the past two years;  in hindsight, considering the hours (in excess of 100, seriously) I have put in to trying to get various forms of VPN working on it, I should have just moved on to a more stable and flexible router.  

    gv wrote:
    1. Never ever forward L2TP port 1701. That's a security risk. Port 1701 is not supposed to be accessible from the internet.
    2. Running an IPSec server behind a NAT gateway is a very bad idea and is either very difficult or impossible depending on the server software and kernel version on the server machine. In particular you usually see a lot of problems if the client as well is behind a NAT gateway.
    3. Turn off the L2TP and IPSec passthrough options. Passthrough is difficult because NAT will modify the packets passing. When you disable the passthrough options the VPN client and server should switch to encapsulation through UDP port 4500.
    Thanks for the reply.  Comments/follow-up on each of your numbered responses:
     1)  Port 1701 is off.  Plenty of sites insist it must be open, so I tried it out of desperation.  Lots of bad information on the internet, as we all know.
     2a)   My IPSec server has always been the NAT gateway itself (the WRVS4400N).  That's not the problem.  My issue with leaving the setup that way is that Linksys has ZERO support for Mac OS X to connect to the WRVS4400N's IPSec VPN.  QuickVPN is only offered for Windows OS, and Cisco VPN Client for OS X will not connect with the WRVS4400N.  THis leaves me with having to use 3rd partyclient  solutions which work flawlessly and completely with other hardware but not with the WRVS4400N.  
    I'd actually be happy with that solution if I could route all traffic (web and email especially) over the VPN tunnel.  THis won't work with the only solutions I have to using IPSec on a Mac to connect to the network.  I've considered establishing SSH tunnels binding the various ports, but proxies, slower performance and other issues make that less than desirable.  Very frustrating.
    I guess since L2TP uses IPSec, your point is relevant, but I don't understand why, if IPSec behind a NAT gateway is such a bad idea, EVERY router on the market offers IPSec passthrough in its specs.  
    If it's so problematic, and such a bad idea, why allow it?   Especially on devices marketed to SOHO consumers who are bound to have less networking savvy?  In fact, the Linksys products ship with these options ENABLED by default. 
    3)  I've done all that.  
    Here are log entries from the WRVS4400N for a few combinations of passthrough and port forwarding:
    Passthrough disabled, ports forwarded
    Dec 7 07:38:40 - Drop by Port Scan UDP
    Dec 7 07:41:25 - UDP Packet - Source:xxx.xxx.xxx.xxx,500 Destination:192.168.2.11,500 - [Firewall Log-IPSecPass Fail]
    Dec 7 07:41:30 - [VPN Log]: shutting down
    Dec 7 07:41:30 - IPSEC EVENT: KLIPS device ipsec0 shut down.
    Dec 7 07:41:32 - [VPN Log]: Starting Pluto (Openswan Version cvs2006Jan12_11:29:56 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR; Vendor ID OE@ECqImzhFD)
    Dec 7 07:41:32 - [VPN Log]: @(#) built on Aug 2 2007:11:09:37:
    Dec 7 07:41:32 - [VPN Log]: Setting NAT-Traversal port-4500 floating to on
    Dec 7 07:41:32 - [VPN Log]: port floating activation criteria nat_t=1/port_fload=1
    Dec 7 07:41:32 - [VPN Log]: including NAT-Traversal patch (Version 0.6c)
    Dec 7 07:41:32 - [VPN Log]: ike_alg_register_enc(): Activating OAKLEY_AES_CBC: Ok (ret=0)
    Dec 7 07:41:32 - [VPN Log]: starting up 1 cryptographic helpers
    Dec 7 07:41:32 - [VPN Log]: started helper pid=11543 (fd:5)
    Dec 7 07:41:32 - [VPN Log]: Using KLIPS IPsec interface code on 2.4.27-star
    Dec 7 07:41:32 - [VPN Log]: Changing to directory '/etc/ipsec.d/cacerts'
    Dec 7 07:41:32 - [VPN Log]: Changing to directory '/etc/ipsec.d/aacerts'
    Dec 7 07:41:32 - [VPN Log]: Changing to directory '/etc/ipsec.d/ocspcerts'
    Dec 7 07:41:32 - [VPN Log]: Changing to directory '/etc/ipsec.d/crls'
    Dec 7 07:41:32 - [VPN Log]: Warning: empty directory
    passthrough enabled, ports not forwarded
    Dec 7 07:47:28 - [VPN Log]: shutting down
    Dec 7 07:47:28 - IPSEC EVENT: KLIPS device ipsec0 shut down.
    Dec 7 07:47:31 - [VPN Log]: Starting Pluto (Openswan Version cvs2006Jan12_11:29:56 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR; Vendor ID OE@ECqImzhFD)
    Dec 7 07:47:31 - [VPN Log]: @(#) built on Aug 2 2007:11:09:37:
    Dec 7 07:47:31 - [VPN Log]: Setting NAT-Traversal port-4500 floating to on
    Dec 7 07:47:31 - [VPN Log]: port floating activation criteria nat_t=1/port_fload=1
    Dec 7 07:47:31 - [VPN Log]: including NAT-Traversal patch (Version 0.6c)
    Dec 7 07:47:31 - [VPN Log]: ike_alg_register_enc(): Activating OAKLEY_AES_CBC: Ok (ret=0)
    Dec 7 07:47:31 - [VPN Log]: starting up 1 cryptographic helpers
    Dec 7 07:47:31 - [VPN Log]: started helper pid=12590 (fd:5)
    Dec 7 07:47:31 - [VPN Log]: Using KLIPS IPsec interface code on 2.4.27-star
    Dec 7 07:47:31 - [VPN Log]: Changing to directory '/etc/ipsec.d/cacerts'
    Dec 7 07:47:31 - [VPN Log]: Changing to directory '/etc/ipsec.d/aacerts'
    Dec 7 07:47:31 - [VPN Log]: Changing to directory '/etc/ipsec.d/ocspcerts'
    Dec 7 07:47:31 - [VPN Log]: Changing to directory '/etc/ipsec.d/crls'
    Dec 7 07:47:31 - [VPN Log]: Warning: empty directory
    passthrough enabled, ports forwarded
    BLANK LOG!  Not a single entry in the WRVS4400N's log files.
    Remember, there is nothing wrong with my client or server software, as demonstrated by bypassing the WRVS4400N.  L2TP connections work fine until the WRVS4400N is in the mix. 
    So, I'm back to the same original question:
     How do I enable L2TP traffic to an L2TP server behind a WRVS4400N in a manner that actually works...? 
    Message Edited by DistortedLoop on 12-07-2008 08:02 AM

  • Latest QuickVPN(v1.3.0.3) reports "WGET.exe has encountered a problem..." with WRVS4400N

    I have a WRVS4400N(latest firmware V2.0.0.7) and am trying to connect to it for the first time using the latest QuickVPN v1.3.0.3 installed on a Windows XP Professional (w/SP3) computer. Installation of QuickVPN with no errors, but as soon as I ran it and tried to connect, it reported "wget.exe has encountered a problem and needs to close. We are sorry for the inconvenience...". I tried it on another machine, also with XP Prof SP2 - same error.  I have looked at the soultion in other similar threads of removing spaces and that did not resolve the issue.  Please let me know if any one has a solution to this problem.

    It sems that the problem was with the Quick VPN client. Please try to download a copy of the QVPN from the Linksys site and try to re-install it on your computer. Please make sure that the previously installed QVPN has been remove before you reinstall it.
    Message Edited by aponikikay on 01-13-2010 07:49 AM

  • Linksys WRVS4400N / Netgear SC101T problem ...

    Hi!
    I recently upgraded from my old WRT54G to the new WRVS4400N. A few weeks before I upgraded I also bought a new NAS (Netgear SC101T, 1 GBit EN, 2 x 500 GB HDDs, mirrored, redundant, different manufacturers) but I found the fast EN (100 MBit) on the WRT54G to be the bottleneck of this setup as my notebook also supports 1 GBit EN.
    So, to finally benefit from the GBit-EN I upgraded to the WRVS4400N (firmware version V1.00.12-ETSI). However, I do not get the SC101T to run with the new router?!? Installing the SC101T under Microsoft Windows XP Professional SP2 (up to date) with the original software as provided by Netgear was no problem. The NAS connected without any problems and I have been using the NAS quite often since for backups.
    However, after upgrading to the WRVS4400N the SC101T is no longer accessible. The status LEDs for power, disks and ethernet signal that everything runs fine. Openening the DHCP Client table on the WRVS4400N shows that the NAS is recognised as:
    'Client Host Name: MicroSAN Base[0]
    IP: 48.48.48.45 or 48.48.48.48
    MAC: 30:30:30:30:30:30'
    or
    'Client Host Name: Root[1]:52315352
    IP: 48.48.48.48
    MAC: 02:18:4D:74:43:89'
    or
    'Client Host Name: 11A4F5D6-0AF4-11
    IP: 52.49.70.52
    MAC: 02:18:4D:73:874'
    (plus seconds that indicate how long this IP address will be valid, a mere 60 sec ...)
    I have my WRVS4400N acting as a DHCP server, address is 192.168.2.1, identical to the address I used on the WRT54G. I have about 28 IP addresses left to be assigned by the DHCP server.
    Clicking on 'L2 Switch' -> 'Port Settings' shows the NAS to be connected at 1000Mbps Full Duplex, Auto negotiation, flow control activated, max frame 1518.
    I am using Agnitum Outpost Firewall, v4.0.1007.7323 (591) but it does not matter whether it is active, inactive or fully deactivated.
    Any hints? There are a lot of pictures (=all) of our newborn daughter stored on the NAS, so I do want to be able to access the NAS again ...
    Thanks!
    Cheers Lars
    Nachricht wurde am 08-01-2007 12:51 PM von Lars_Behnke bearbeitet.

    hi!
    Have you tried assigning static IP on your NAS?  Is that the only thing that did not work on the router? Is firmware V1.00.12-ETSI came with the router? (out of the box)
     I checked the Linksys website and found out that the latest firmware for WRVS4400N was 1.00.15. If putting a fixed IP on your NAS did not work, maybe you can reset the router and reconfigure or try the latest firmware. I hope it helps.

  • Inconsistent DHCP leases while using WRVS4400N as Wireless Access Point

    I have a small home network that is made up of a Windows 2003 server connected directly to my WRVS4400N. The DHCP server is disable in the WRVS4400N and all DHCP and DNS services are being provided by the 2003 server. My WPSM54G print server has no problem obtaining an IP address but my other 3 non-Linksys wireless computers are timing out during the IP request process. All 3 computers have a good wireless connection and will work fine if I configure them for a static IP address but I would rather use DHCP if at all possible. Do you have any information that could help me clear up this problem. I have installed the latest firmware which is version 1.01.03 but this has not helped the situation.

    have you tried to direct connect your PCs to the router just like your server and check if it can obtain and IP?
    try changing wireless settings from the router [SSID and CHANNEL]
    enable WPA as well
    are they able to obtain an IP from a diff wireless network?

  • Help Please :) LInksys WRVS4400N 802.1X port authentication setup

    HI all,
    I am trying to configure 802.1X port authentication on my Linksys WRVS4400N. I created a test lab in order to do this, currently I am using
    1x Linksys WRVS4400N
    1x Microsoft Server 2003 with IAS and Active Directory services
    1x Dell Laptop (Used for testing Radius Athentication)
    I Created 4 VLAN(s) to test with this LAB
    VLAN 1 Managament. Addr Range 192.168.1.0 /24. GW 192.168.1.254
    VLAN 10 Servers. Addr Range 172.16.1.0 /24. GW 172.16.1.254
    VLAN 20 IT. Addr Range 172.16.2.0 /24. GW 172.16.2.254
    VLAN 30 Design. Addr Range 172.16.3.0 /24. GW 172.16.3.254
    This is how I assigned my VLAN(s) to my ports. This is found on the VLAN & Port Assignment Screen
    Port 1 -> Mode: General -> Frame Type: All -> PVID 1 (Port 1 is used for VLAN 1: Management)
    Port 2 -> Mode: General -> Frame Type: All -> PVID 10 (Port 2 is used for VLAN 20: Servers)
    Port 3 -> Mode: Access -> Frame Type: All (Port 3 is used for RADIUS. DHCP enabled)
    Port 4 -> Mode: Access -> Frame Type: All (Port 4 is used for RADIUS. DHCP enabled)
    VLAN 1: Default
    Port 1: Untagged, Port 2: Tagged, Port(s): 3, 4 & Wireless: Excluded
    VLAN 10: Servers
    Port(s): 1, 3, 4 & Wireless: Excluded. Port 2: Untagged
    VLAN 20: IT
    Port(s): 1, 2: Excluded, Port(s): 3,4 & Wireless: Untagged
    VLAN 30: Design
    Port(s): 1, 2: Excluded, Port(s): 3,4 & Wireless: Untagged
    This is how my Radius is setup
    Mode: Enabled
    RADIUS IP: 172.16.1.1 (IP of the WIN2K3 Server)
    UDP Port: 1812
    Secret: Password1
    Port(s) 1 & 2: Force Authorized
    Port(s) 3 & 4: Force UnAuthorized
    On the Server this is what I have configured
    1. Created a domain: GLAB. Created two groups: IT LAN, Design LAN, then assigned users to those groups. IE: User1 belongs to IT LAN
    2. Created a IAS Remote Access Policy and named it IT LAN. The profile settings are listed below
    Tunnel-Medium-Type: 802
    Tunnel-PVT-Group-ID: 20
    Tunnel-Type: Virtual LAN
    My goal is to test RADIUS authentication on ports 3 and 4 on the Linksys WRV . I tested everything else I made sure the VLAN's were working ok so what I did was took a Dell Laptop and joined it to my domain. I pluged the Dell Laptop into port 4 to test Radius Authentication. When I tried to log in as User1 it didn't work.
    I am new to setting up 802.1X, I wanted to know if I missed a setting or I misconfigured something. I even ran wireshark on my Windows 2003 machine to see if any RADIUS data is coming from my router (172.16.1.254) and I didn't see anything
    If anybody can help me out that would be great!
    Cheers
    Graham

    1. I don't think the WRVS4400N supports RADIUS assigned VLANs. I can't find anything in the manual suggesting it would. I would say you can only use the RADIUS server for authentication on a port but the VLAN must be configured before.
    2. You don't write what is exactly connected to each port on the WRVS. For instance, it is unclear whether the MS Server is connected directly to port 2 or whether it connects to another switch to which you have connected other servers as well.
    3. The VLAN configuration looks very odd to me. If I see it correctly you have:
    Port 1: General mode, PVID 1, 1U
    Port 2: General mode, PVID 10, 1T, 10U
    Port 3: Access mode, PVID ???, 20U, 30U
    Port 4: Access mode, PVID ???, 20U, 30U
    I wonder why you are even able to set this up...
    a. Port 1 should be set to Access mode with PVID 1 and 1U. With access mode the port is member of a single VLAN and all traffic is untagged. That is exactly what you have set up, but with General mode.
    b. Port 2 must be connected to a server (or a managed switch). The NIC in the server must be configured for 802.1q tagged frames. On the server NIC you must configure VLAN 1 as tagged VLAN and VLAN 10 as default/native/untagged VLAN. Only then the server is able to communicate on VLAN 1 and VLAN 10.
    c. Port 3&4 are in access mode. In access mode the port can only be member of a single VLAN. What you post suggests that they are member of two VLANs. That should not even be possible to configure. If it is possible, that it is definitively incorrect. You must decide to which VLAN these ports belong to.
    4. To use RADIUS authentication on a port you must set it to "Auto". "Force UnAuthorized" sets it unauthorized, i.a.W. you disable the port completely. To traffic will go through. See the manual: "Force Unauthorized—Controlled port state is set to Force-Unauthorized (discard traffic). All connections are blocked."
    5. Did you verify that your RADIUS server is actually using port 1812? 1645 is also commonly used for radius authentication. Check the configuration on the RADIUS server or check with "netstat -a" to see if 1812 is used.
    6. Also check, whether the RADIUS traffic is sent on the management VLAN 1. The WRVS uses VLAN 1 as management VLAN and it might well be that it expects the RADIUS server to be in the management VLAN. Use the server IP address in VLAN 1 as RADIUS server IP address to check that.
    7. Did you check with wireshark the traffic on the 802.1x client machine? Does it send something out? Does it receive anything?

  • How to setup QoS for IP/Mac Address WRVS4400N

    I need some help setting up QoS for two Cisco/Linksys devivces on my network. 
    Network devices are Comcast SB6120 modem into WRVS4400n (v2.0.2.1 firmware) that divides into one 24 port gigabit Netgear unmanaged switch, 1 port into AT&T Cisco Microcell, 1 port to HP Officejet 7700 wired printer.  Unmanaged switch has approx 10 devices attached (including another 8 port unmanaged gigabit switch).  3 static leases are defined for the network for three devices (HP OJ 7700 printer, Cisco/Linksys PAP2 VOIP adapter, windows home server v1.  DHCP is handled by WRVS4400n.  Comcast service provides 12mbps of service upstream, 4mbps downstream.
    Need to setup QoS for AT&T Microcell and PAP2 VOIP adapter.  The real issue that I can't figure out how to configure is IP based priority access.  I can do rate control for an IP address but can't figure out how to specify priority control for an IP.
    Here are my the current config questions:
    1.  Bandwidth management page:  For the microcell device plugged into port 1, do i set the default CoS to 4 or 1?
    2.  Bandwidth management page:  Should the bandwidth management type be set to priority?  I assume yes since I need to define the UDP/TCP ports for priority.  The major issues here are
    a) one of the ports the Microcell uses is secure https (TCP 443) which is could also be used by any other internet device. 
    b) can't specify priority for the PAP2, since it's behind the unmanaged 24 port switch
    3.  QoS setup page:  Do I need just 2 queues (one for the port ID for the Microcell and one for the IP address of the Linksys adapter)?
    4.  QoS setup page:  I assume I need to define DSCP for the unmanaged switch but not sure how to tie a queue to an IP address
    4.  QoS setup page:  Shoud priority 0 be set for the most important queue (microcell) and the priority 1 CoS be for the VOIP adapter?  Again, not sure about how to define priority by IP address.
    5.  DSCP setup page:  As far as I can find, there's no documentation on how to setup this page.   

    That's what I do. I keep it simple, one calendar, one set of contacts.
    iCloud is really the simplest way to go, as it will sync your (eventual) single Contacts and Calendar across all your devices.
    I would:
    Figure out which single calendar (in Calendar.app) and contacts (in Contacts.app) that you want to keep.
    I'd make a backup of each one. For example,
    in Contacts, File > Export... > Contacts Archive...
    in Calendar, File > Export... > Calendar Archive...
    Make a backup of the other calendar events and contacts that you want to save.
    delete all the contacts and calendars from your phones and your iPad.
    add the contacts and events from the backups to the single calendar in Calendar.app and your contacts in Contacts.app on your iMac. There is probably some way to export the contacts and events you are adding, and then combine them, but you could also just add them manually.
    Then when you configure all your devices for iCloud, they will be all synced automatically.
    Message was edited by: arthur

  • WRVS4400n questions

    Hi Every1,
    i had brought a brand new WRVS4400n SMB router, and i have some question to make better its performance and usability...
    1,
    I have made the FW upgrade to 2.0.0.8 from 2.0.0.7, BUT the IPS signature is still almost 2 years old. Would this updated, and if yes when??
    2,
    If i want use the Wifi n standard how could i? I set the Wireless mode to G/N mixed, and the bandwith to 20/40 Mhz so i think i could use the Wifi N. My problem is that i know so, that Wifi N uses 5 Ghz freq too, by grouping the 2,4 Ghz channels or 2,4Gz and 5 Ghz channel.... so how could i sure in that that the connection bethween a device (netgear EVA9150) and the wrvs4400n is wifi N? (esspecially the netgear eva see 2,4Ghz and not 5Ghz signal)
    3,
    By ours we have a huge indoor places, and the IT stuffs place is not the best in these case, so could someone give me information about the compatible external antennas? Or could i use any RPSMA connector antenna in 2,4-2,5Ghz range or i need to buy one antenna in 2,4-5Ghz range?
    4,
    If i want use Jumbo Frames (7936), then how i could use? it is working by changing the MaxFrame settings on page L2 Switch port settings?
    5,
    I must syncronise the routers time to NTP servers, but sorry in the configuration it is only one NTP server IP address room, would this changed to that settings to i could change here the IP address to DNS name??
    Thank You, for any information, with regards,
       SirFrankie

    in answer to this question, yes, the quickvpn client software is doing vpn encapsulation. 
    Apparently it's doing so using openswan/freeswan on the endpoint, but right now I'm having headaches getting a linux client behind NAT to talk to it.  the windows clients are doing it just fine, and if you run wireshark to look at the traffic, you will see that it is encapsulated as it should be.
    My experience with this box is that the design is poor - the gigE switch tends to overheat as shipped, and if you open it up, you can see why - a postage-stamp sized heatsink on the chip, and glued down off-center of the chip.  I bought this at compusa during the closeout, so I got a good price on a dodgy piece of gear 
    I've re-sinked the chip, ventilated the case, and clipped off a lot of the useless internal tin. 
    The router is now stable, unless I try using jumbo frames on the switch, at which point it becomes unstable.  I suspect that's a thermal issue but I'm not 100% on that.  There may also be issues with the jumbo frames implementation elsewhere on my network.  My experience with jumbos is very limited, but it suggests to me that using them on subpar devices actually degrades performance spectacularly. 
    R

Maybe you are looking for