Forum Discussion

Aspirant

Nov 06, 2020

Access Denied when opening shares via VPN

Revisiting an old outstanding issue: On a AD environment, users can access shares no problem. When they use a VPN, they can't access the ReadyNAS shares. They can access Windows-based shares on the V...

heatproofsean

Aspirant

Nov 10, 2020

Thanks for the advice, I have a feeling the other windows file shares use SMB1 as well, since they are running on older OS (Windows 2003). Is there any other method of sharing the files if this is the cause?

StephenB

Guru - Experienced User

Nov 10, 2020

heatproofsean wrote:

I have a feeling the other windows file shares use SMB1 as well, since they are running on older OS (Windows 2003).

Windows 2003 does use SMB 1 (SMBv2 was introduced with Vista). So if those shares are accessible over the VPN, then the VPN isn't the cause of your problem.

Sandshark
Sensei
Nov 10, 2020
Have you tried accessing via the IP address instead of name? Some of us have problems with Win10 when using the NAS name. I'm not sure why it would be different on VPN than local, but it's worth a try.

Are you sure somebody didn't put exceptions in for the Windows 2003 servers and forgot about the NAS?
- heatproofsean
  Aspirant
  Nov 11, 2020
  I did try with IP address and it didn't make a difference.
  And I've looked at our firewall and I can't see any special rules for the other windows file servers. Again, I can connect to the root of the NAS but not into any of the actual shares.
  - StephenB
    Guru - Experienced User
    Nov 11, 2020
    heatproofsean wrote:
    
    I did try with IP address and it didn't make a difference.
    
    And I've looked at our firewall and I can't see any special rules for the other windows file servers. Again, I can connect to the root of the NAS but not into any of the actual shares.
    
    Have you tried using net use in CMD (explicitly specifying NAS admin credentials)?
    
    For instance
    
    net use * /delete /y net use t: \\nas-ip-address\C /user:admin nas-admin-password
    
    The second command maps the full data volume to drive letter T (which requires NAS admin credentials).
    
    If the VPN is blocking SMB 1 somehow, then the second command would fail over the VPN, but would work on the local network.
    
    What do you mean by "connect to the root of the NAS"? Do you mean that you can see the share list in file explorer (or from CMD)? Or do you mean something else?