ReadyNas 1100 not accessible via VPN

Question

In a domain environment, we have a ReadyNas 1100 and some Window 2003 Servers acting as File Servers. Users on our network can access both without problems. However those that connect via VPN ( managed by watchguard firewall) cannot access the ReadyNas drives or web interface (but can ping it).

VPN IP Pool is 10.181.20-80
DHCP Pool is 10.181.10.20-200
ReadyNas IP is 10.181.2.1 and 10.181.2.2 (Eth0 & Eth1)

Any help would be greatly appreicated as this is an on-going issue that I'm struggling with.

heatproofsean · Answer

Just to add, I've tried mapping to the shares via Sharename (CHDNAS001) and IP. The latter just times out. Using IP prompts for a username/password which never works (NAS Admin nor their Windows account (User/admin/network admin all get the same result), as it just says "The specified network password is not correct".

Mapping via IP works when connected to the network

Sandshark · Answer

I suspect it's an SMBv1 issue, as that's all OS4.2.x supports.&nbsp; Your configuration sounds more complex than the usual solution of enabling SMBv1 in Windows10.

heatproofsean · Answer

We do have SMBv1 enabled on every machine as our other file server is Windows 2003. And it does work when on the network but not over VPN.

StephenB · Answer

Does https://nas-ip-address/admin work correctly on these systems?&nbsp; If it does, you could enable http sharing for a test share, and see if that works over the VPN.
&nbsp;
Have you tried disconnecting one of the ethernet ports?&nbsp; When you use both ports w/o bonding, the return traffic from the NAS could be sent from either NIC, and that might be messing up the VPN routing.
&nbsp;

heatproofsean · Answer

I wasn't able to access the admin webpage via VPN before, but I've been playing with the MTU on the VPN clients (increased from 1380 to 1400) and I'm now able to get into the root of the ReadyNas (but not any of the shares). When I try the website now, I'm getting prompted about security certificates and asked for credentials but seems to just hang.&nbsp;I think the ReadyNas was using 1 Ethernet port but was moved to a new rack on Sunday where it was given an additional Ethernet port. When I get chance I'll try going back to 1 port and see if that changes anything.

Forum Discussion

ReadyNas 1100 not accessible via VPN

8 Replies

Related Content

Nighthawk MR 1100

ReadyNas-1100

Enabling SSH access on Readynas Ultra 2

RNDU4000 (ReadyNAS Ultra 4). No more accessible after years of not using

Accessing journalctl command on ReadyNAS 102

NETGEAR Academy

ProSupport for Business