Questions

Cannot Access Shared Drives (located on a NAS) remotely.

+
0 Votes
Locked

Cannot Access Shared Drives (located on a NAS) remotely.

PkSB42001
We have a NAS (QNAP TS-209 Pro || ) and it has some shared folders (Public, Resources etc). This NAS is a "AD Domain Member " and every user can access their shared folders/drives when he/she logs in the network and everything works fine. We also a 2008 R2 Standard as Domain Controller.

When a user logs in remotely (through Cisco VPN client) he can access every resource in the network except the shared drives on the NAS.

The NAS is configured with a static IP address of 192.168.111.xx and I can ping the device by the IP address when I am connect through VPN remotely. Even the tracert works.

But when the user tries to map this shared drives he gets the following error:

" The mapped network drive could not be created because the following error has occured .
No process is on the other end of the pipe "

Could someone please shed some light on this issue. Thanks
  • +
    0 Votes
    cmiller5400

    Sounds like a port is not being forwarded through the VPN.

    http://www.qnap com/images/products/Application/TS109AP05.htm

    Please put a period between the qnap and com, and remove the space

    +
    0 Votes
    JPElectron

    Try using the IP of the NAS box...
    If you can then reach the share, you've proved it's not a port problem, you might need to specify the AD DNS server as the default for the VPN tunnel, that way when client's connect they will be able to resolve server names.
    Also confirm your NAS box has an A record in the AD DNS server.

    If you can't reach the shares by name or by IP, then you likely have a port issue; 135 to 139 and 445 are required for Windows file sharing.

    +
    0 Votes
    PkSB42001

    I went to the forward lookup zones and added the NAS as a A record. Now I can ping the NAS with is name (NAS.xxxx.local). As explained in my previous post I can always ping the NAS with it's IP address.

    The ports are definitely open because I can access a shared folder on another server.

    +
    0 Votes
    JPElectron

    Does the NAS have the correct Default Gateway IP defined (should be the IP of your firewall/VPN device)

  • +
    0 Votes
    cmiller5400

    Sounds like a port is not being forwarded through the VPN.

    http://www.qnap com/images/products/Application/TS109AP05.htm

    Please put a period between the qnap and com, and remove the space

    +
    0 Votes
    JPElectron

    Try using the IP of the NAS box...
    If you can then reach the share, you've proved it's not a port problem, you might need to specify the AD DNS server as the default for the VPN tunnel, that way when client's connect they will be able to resolve server names.
    Also confirm your NAS box has an A record in the AD DNS server.

    If you can't reach the shares by name or by IP, then you likely have a port issue; 135 to 139 and 445 are required for Windows file sharing.

    +
    0 Votes
    PkSB42001

    I went to the forward lookup zones and added the NAS as a A record. Now I can ping the NAS with is name (NAS.xxxx.local). As explained in my previous post I can always ping the NAS with it's IP address.

    The ports are definitely open because I can access a shared folder on another server.

    +
    0 Votes
    JPElectron

    Does the NAS have the correct Default Gateway IP defined (should be the IP of your firewall/VPN device)