NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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
- Were you able to browse via Windows Explore first?
- What happens when you try to connect from Windows Explorer by typing \\192.168.1.3\MyShare?
Do your WRVS4400N routers have the latest firmware? Check release notes here. http://www.cisco.com/en/US/docs/routers ... _Notes.pdf - Yes, routers have latest firmware.
No, over VPN I cannot browse network via Windows Explorer (Win7 Network group shows only my own PC).
I also cannot connect by entering \\192.168.1.3\MyShare into Windows Explorer's address bar (although I can do that successfully when at the office).
However, over VPN I can get into frontview admin via https://192.168.1.3/admin and I can print to the office TCPIP printer (192.168.1.222)
Note that all tests conducted at SOHO and office are using the same laptop, which travels back and forth, so that element is constant.
-------
FURTHER UPDATE:
Installed WebDrive trial copy and, when connected via VPN
1. It could not map a drive letter to MyShare over https://192.168.1.3/MyShare, but
2. It could map a drive letter over https://12.34.56.78/MyShare (i.e. using the real external IP for our network)
Need some ideas, guys. - I suspect your VPN is blocking some services. Could you set up a network share on a PC, and attempt to access it from the remote location?
I think https://192.168.1.3/shares will work (in a browser, not mapped to a drive letter), but you might want to confirm that. - An excellent suggestion, thank you. I did just that -- went to the office and shared a folder on the other computer.
Successfully logged onto that share while at the office, both using Windows Explorer and DOS. Was unable to connect to the share over VPN. - Try disabling Windows firewall or any other firewall you have installed. Something is blocking your NetBIOS ports.
It can't be the Windows firewall, since the failure only happens through the VPN tunnel - the same PC and NAS work fine when both on the same LAN.claykin wrote: Try disabling Windows firewall or any other firewall you have installed. Something is blocking your NetBIOS ports.
I think it is the VPN routers that are blocking NetBIOS. There is supposed to be a NetBios Broadcast setting in the routers, you should poke around and see if you can find it.- I thought NetBIOS had to do with Host Name resolution not direct IP addresses....?
Someone enlighten me so I can update that file in my brain. :nashammer:
NetBIOS also includes a session service which is used by CIFS over TCP port 139. NetBios Name resolution is also used by CIFS (UDP broadcasts on port 137).fbmachines wrote: I thought NetBIOS had to do with Host Name resolution not direct IP addresses....? StephenB wrote: NetBIOS also includes a session service which is used by CIFS over TCP port 139. NetBios Name resolution is also used by CIFS (UDP broadcasts on port 137).
http://www.youtube.com/watch?v=Pj-qBUWOYfE
Brain updated.
Thanks!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
