1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Advice needed WRVS4400N + AM200 Modem

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by lazybeagle77, Aug 9, 2007.

  1. lazybeagle77

    lazybeagle77 LI Guru Member

    Hi,

    Should I be able to use a WRVS4400N VPN Router with an AM200 Modem connected to the WAN port ? ISP uses PPPoA.

    If so has any one else had this working with QuickVPN ? Any one got a recommended configuration ?

    Thanks
     
  2. DocLarge

    DocLarge Super Moderator Staff Member Member

    Yes, if you can put the am200 in bridge mode.

    1) Set the am200 for bridge mode
    2) Run cat5 from its ethernet port (the manual may designate a particular port in bridge mode, but I'm not sure since I don't have that particular model) to the WAN port of the wrvs4400n
    3) Set the wrvs4400n for "PPPoE"
    4) Input the username/password combo your isp gave you into the wrvs4400n

    You "should" be good from there. Post back if your having problems. If you are, I'll break out my adsl2mue and slap my wrvs4400n on in the same fashion and see what I get :)

    Jay
     
  3. lazybeagle77

    lazybeagle77 LI Guru Member

    Hi,

    Thanks for your response !

    I have the 2 devices connected this way. It is working but I have a couple of issues. Modem is on 192.168.1.0 subnet. VPN router is on 192.168.100.0 subnet.

    1. QuickVPN from a remote client connects straight away. I can ping all network devices on the LAN by IP address fine. When I copy files to any of the servers or clients I receive an error "Can't copy file. The remote network name is no longer available" after 30 secs or so. I am connecting to the shares on the remote machines using the IP address in the UNC eg
    \\192.168.100.10\sharename

    I can use VNC to connect to the PC's fine. I can copy files from the LAN back to the QuickVPN client OK. I can copy files between PC's on the LAN with no problems also.

    2. I can't get the QuickVPN client to use the internal DNS & WINS server that is running on a Windows 2003 SBS on the LAN. It receives my ISP's settings instead. Is there a way around this, that does not manually involve adding the settings to the connection everytime a client connects ?

    Just so you know I am using firmware 1.0.12 on the WRVS4400N If I use any later version ie 1.0.13 or 1.0.15 Then the remote QuickVPN client can no longer connect to it. Have been using QuickVPN 1.2.2 and since yestreday 1.2.5

    I have tried many avenues to get this solution working and am almost there any help would be much appreciated !

    Thanks

    Harvey
     
  4. DocLarge

    DocLarge Super Moderator Staff Member Member

    Qvpn 1.2.5 isn't compatible with 1.0.15, so you should stay where you are as far as firmware goes for the time being. Also, qvpn isn't like the microsoft pptp client where you get an ip from the server; it's not designed that way so you will not have an ip address from the LAN you're connecting to.

    Regaring your question about the network not being available, your MTU might be to high...

    Go in to the setup page and set it to 1465 and try it again. I'll try and find the Zdnet article that explains how to tell if your MTU is set right because I can't remember the commands off the top of my head. If it doesn't work with 1465, then go do 5 increments (1465, 1460, 1455, etc...) until you can maintain a connection...


    Jay
     
  5. lazybeagle77

    lazybeagle77 LI Guru Member

    Hi,

    You are a star !:biggrin: I found an earlier post you had written to glock918 on MTU and DrTCP. This has worked I can now copy files across from the client to the server with no problems.

    I agree I think I will stay on 1.0.12 a bit longer seems a bit more stable ?? Is this why it is the latest firmware available on the UK linksys site ?

    I may now just use host entries to get the name resolution working. Although it seems a shame that you can't get the quickvpn client to use different WINS/DNS ie the Windows 2003 SBS.

    I also have an issue with Vista and getting stuck at "Verifying Network" when trying to connect. Although I have seen a few people post on this.

    Once again thanks for your help with this. Much appreciated !

    Harvey
     

Share This Page