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

Mapped Drive Reconnect/Login Question

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by soslink, Oct 17, 2007.

  1. soslink

    soslink LI Guru Member

    We use two RV042 VPN routers to connect our 2 locations. Our main office has a Win2003 Server and our remote office has only XP clients and no server. The remotes connect to the main office's Server's shared folder using the "\\ServerIPaddress\shared folder" using a mapped drive. All 3 remotes login with the same username/password of an AD account on the Server and use the "Connect as a diffferent User" option.

    The tunnel stays connected without problems. However, periodically the mapped drives will disconnect without warning or will not reconnect after the remotes reboot.

    Question:

    1. If the tunnel is staying connected, what reason(s) might the remotes mapped drive get disconnected?
    2. Note, we are not having the remotes login to the domain -they are in their own workgroup. Should we setup individual usernames/passwords on the DC for each of the remotes instead of using the same login credentials for the purpose of mapping a drive to the Server? We do not want to join them to the domain.
    3. Is there a script we can create for the remotes so that when they reboot the mapped drive to the server is established -even though they do not login into the domain? If so, how?

    Thanks!
     
  2. mcato

    mcato LI Guru Member

    similar problem with RV082

    We are seeing a similar problem with two RV082's firmware version 1.3.5 in gateway<->gateway mode, with the remote office RV082 initiating the connection. After some experimentation, we found the "culprit" seemed to be the main office RV082 (the one "serving" the connection initiated by the remote).

    Both RV082's continue to think the VPN connection is alive and well when the problem of not having access to the shared directories occurs.

    The work-around we're using is to set up a share on the REMOTE side (an empty directory) that is monitored by a periodic script on the MAIN side's server (the server the remote side wants access to via \\IPaddr\share). If the script can't see the remote side's shared directory (and ipso facto, the remote side won't be able to see the main side's shares), then it telnets into the main RV082 and reboots it. The remote RV082 detects the VPN connection has been dropped and automatically re-establishes it. Then both sides "see" each other's shares again.

    Rebooting the remote RV082 (the VPN connection initiator) did not allow the shares to be re-established.
     

Share This Page