NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNas 1100 not accessible via VPN
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 ( manag...
I suspect it's an SMBv1 issue, as that's all OS4.2.x supports. Your configuration sounds more complex than the usual solution of enabling SMBv1 in Windows10.
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.
Does https://nas-ip-address/admin work correctly on these systems? If it does, you could enable http sharing for a test share, and see if that works over the VPN.
Have you tried disconnecting one of the ethernet ports? 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.
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.
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.
heatproofsean wrote:
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).
That's a good clue. Try resetting the MTU to 1400 on the 1100, and see if that works.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
