NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
bcmit
May 15, 2012Aspirant
Cannot map drive to ReadyNAS over VPN
I need to map a network drive over VPN. Very simple host network: no Microsoft server, no AD. Just a Cisco router and the ReadyNAS NV+ (Ver 1) as a simple file server.
Two identical Cisco WRVS4400N VPN routers create the VPN. Router1 in office (192.168.1.1), Router2 in soho (192.168.11.1). VPN works perfectly, no client software required. When at SOHO (behind router2 with an IP address of 192.168.11.100), can successfully ping the ReadyNAS at 192.168.1.3.
When at the office, I can map a drive letter to the ReadyNAS as follows:
net use f: \\192.168.1.3\MyShare /User:MYSELF mypass
However, when try same command over VPN, I receive the response:
System error 1244 has occurred.
The operation being requested was not performed because the user has not been authenticated.
Two identical Cisco WRVS4400N VPN routers create the VPN. Router1 in office (192.168.1.1), Router2 in soho (192.168.11.1). VPN works perfectly, no client software required. When at SOHO (behind router2 with an IP address of 192.168.11.100), can successfully ping the ReadyNAS at 192.168.1.3.
When at the office, I can map a drive letter to the ReadyNAS as follows:
net use f: \\192.168.1.3\MyShare /User:MYSELF mypass
However, when try same command over VPN, I receive the response:
System error 1244 has occurred.
The operation being requested was not performed because the user has not been authenticated.
16 Replies
Replies have been turned off for this discussion
- bcmitAspirantThanks for the important hints and clues as to where to look for the problem.
I have been able to confirm that Windows 7 Home Premium, which is on my laptop, exhibits this behavior.
A different laptop, installed with Windows7 Professional, works fine.
The solution, under Win7 Home, is to use WebDrive... or to purchase an upgrade.
Two Questions:
1. I'm behind the curve on Win7... Under WinXP, in-situ upgrades didn't work so well. Clean disk installs were recommended. Can anyone advise re Win7?
2. Any suggestions to finesse Home Premium to overcome this limitation and work correctly over VPN? That is, perhaps Home Premium can be "configured" to map drives over VPN? - StephenBGuru - Experienced UserI was thinking about your symptoms again -
With Windows 7, your network connection can be identified as either "home", "work", or "public". Network discovery is turned off in Public. Is your network connection identified the same way when you are home as when you are in the office? - bcmitAspirantThank you for continuing to ponder this. Your brainstorming is kindly appreciated. I'm pretty sure that I was careful to identify all 4 connections as "Work" (Win7 Home laptop at office, Win7 Home laptop at SOHO, Win7 Pro laptop at office and Win7 Pro laptop at SOHO).
However, is there a way after the fact to (1) check how a network connection has been identified, and (2) to change the identification type (home/work/public)?
Thanks for the info about the difference between them (i.e. network discovery = Off). - StephenBGuru - Experienced UserYou go into the control panel's "network and sharing center". The network type is below the active network - you can click on that, and it brings up the choice list in a new window.
- bcmitAspirantMea Culpa.
Due to a lack of alternate machines for testing, I continued until now to believe the fault to be Windows 7 Home vs. Windows 7 Premium. I was wrong.
For some reason, the Win7 Home laptop had a 3rd party firewall installed on it (ZoneAlarm Free). However, although ZoneAlarm was running, there was no icon for it in the system tray and the Windows Firewall also was turned on. Of course ZA showed up in the "Programs and Features" list, but I didn't look there. I assumed I knew what was on the laptop.
Uninstalling ZoneAlarm Free solved the problem for the Windows 7 Home Premium laptop.
My apologies to all who joined in the collective head scratching. - StephenBGuru - Experienced UserInteresting. Still it is odd that it worked locally. ZoneAlarm must be blocking SMB requests that go off the subnet.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!