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

RV042 network issue

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by Verbi, Jun 22, 2005.

  1. Verbi

    Verbi Network Guru Member

    Hi,

    We have bought the RV042 to our office and now im trying to make some working VPN tunnel from WinXP using QuickVPN.
    QuickVPN works as expected (after some time) but i cannot reach computers from remote side (behind VPN router). I can only reach VPN router (192.168.10.198).
    It means that i cant even ping them (just 192.168.10.198). Also mounting remote drive does not work ofcourse.

    The configuration is :

    RV042 (fw 1.3.6.4) connected with fixed IP to the internet (213.x.x.x) and with fixed IP (192.168.10.198) to our NETWORK.
    Our network using IP range: 192.168.10.0/255 and GW 192.168.10.1


    Client: Windows XP SP2 without integrated FW!! and QuickVPN 1.0.0.28

    Im not good in configuration of VPN router so it might be possible that i have made some mistake somewhere, but i think all the stuff is set well.

    If anybody knows how to fix this I will really appreciate it.

    Thanx.
     
  2. Brian_B

    Brian_B Network Guru Member

    The workstations on the inside (of your LAN) need to have their gateway defined. Make sure their gateway is pointed to the LAN of the VPN router!

    Used to see this all the time on HP Jetdirect printers that were given an IP address but no gateway, can't ping them accross a router!

    Hope that helps.

    Brian
     
  3. perak

    perak Network Guru Member

    Hi Verbi,

    do you have a network with domain controller and DNS-server
    or a workgroup (peer-to-peer network)?

    We have the same problem with our domain network (Win2k) and a RV082.
    If we set the DNS-server ip-address manually on our computers to
    use QuickVPN they will be able to ping both ip's and names.

    Still we are working to solve the mapping of server folders.
    It does not happen "seamless" but we can use a small
    script with "net use" command and map them.
    There are some more problems here as this requires another
    user and pwd diffrent from the user currently logged into the
    computer.

    Will post the information when/if we succeed.

    perak
     

Share This Page