QuickVPN and network browsing

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by Nd4Spd, Jan 4, 2007.

  1. Nd4Spd

    Nd4Spd LI Guru Member

    I've got an RV0041 and with about a month of playing and fiddling about, I finally got the Greenbow client working. I was able to get the QuickVPN client to work to work with it as well and since it was free, went that route.

    I've got clients working at home and want to connect to their system. In other words, connect to the client up stream while they are connected using the QuickVPN client. I know I can't ping them and I don't "see" them on the network when they are connected like you can with other VPN solutions. I've used a SonicWall VPN and when a client came in, the router gave it an address within its range. But, as has been noted elsewhere, the RVxxx has to have a different IP range than the client's connecting. So if internally we have and the client connecting is 192.168.2.x, we (local LAN) can't see the client (remote user/LAN).

    So, is what I'm wanting to do even possible?

  2. Shoot_the_Router

    Shoot_the_Router LI Guru Member

    Hey...did you ever get an answer to this? LinkWus Non-Technical Support claimed "that is what program designed to do. It working correctly. No problems."
    When I stated that I need the client to be able to see devices on the network they were VPNing to they said "that is what program designed to do. It working correctly. No problems."
    When I said I couldn't map drives on the client I was told "that is what program designed to do. It working correctly. No problems."
  3. eric_stewart

    eric_stewart Super Moderator Staff Member Member

    The answer to this question is found in the sticky found at this link:

    Please read the FAQs/Stickies 1st, since the majority of answers to common questions (and this is a common question) are found there. Don't blame the Linksys support guys...they're just reading from a script and guaranteed that other vendors are pretty much the same. That's why these forums are here...to provide support (unofficially) over and above that which you can find from the Linksys 1st level support folks.

    The short answer, is that the VPN does not allow NetBIOS traffic to propagate across it. This is by design. NetBIOS is inherrently a *very* chatty (read: bandwidth-intensive) application which was originally architected for LAN environments only. NBT (NetBIOS over TCP/IP) which is used by SMBs such as Windows networking is no better. It will consume WAN bandwidth, which is often orders of magnitude less than on a LAN, very quickly.

    If you want to map a drive across the VPN you have to use the remote device's IP address. Also, don't expect to see it in your "My Network Places". You'll be holding your breath for a long time.

    You can Map the drive using the tools option in the Tools/Map Network Drive menu in the "My Network Places" Explorer window. If the share is called "Photos", and it's on a device whose IP address is, you would type in the UNC (Uniform Naming Convention) of the share as "\\192.1680.253\Photos" (without the quotes).


    P.S: I noticed that the URL for the sticky is not working right now. Please PM Toxic
  4. Nd4Spd

    Nd4Spd LI Guru Member

    No, I'd never gotten an answer and I didn't see it because the FAQ links have been down (already mentioned those in another post).

    Thanks for the info mates.

    I am not so worried about the client seeing machines on the system it's VPN-ing to (that works fine by using IP addresses). I'm talking about the users on the LAN/VPN side seeing the client VPN-ing in to the LAN.


  5. eric_stewart

    eric_stewart Super Moderator Staff Member Member

    Gotcha. Since the QuickVPN Server does not hand out IP addresses, there's no IP address to ping back to from inside hosts.

    You mentioned in your 1st post that you had the GreenBow client working. The only way for you to have that working is if you have statically assigned an IP address to the GreenBow VPN client. You *can* (or should be able to) ping back to *that*client if it's on the same subnet.

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice