NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
problems with Windows10 connecting to SMB share
I have been using SMB shares from my Readynas for a long time in home network with mostly all macs, but recently I changed one machine to a Windows10 machine and have had some issues with SMB. It worked at first, but then something get wacked and now its not working and I don't know where the problem is.
I hope someone can give some insights...there are a few dimensions to this.
I had originally setup the windows10 pro machine using pretty default network settings and it was connecting to my SMB share, using my readynas credentials. I set up a mapped drive on the windows machine, using my Readynas credentials, which are of course totally different the windows machine
, but then I tried to start up IPVanish for VPN and it immediately killed my SMB access to readynas. SO I rebooted and got it back, but without VPN, as I tried to work through solving this, I tried to set the windows machine to Private rather the public network, since its at home. My hope was that by doing this, VPN would consider everything at 192.168.x.x as local and private stuff that should not be encrypted, including SMB access to readynas, while everything going out to ISP would be. That's how it worked from my macs, easilyi and effortlessly. Anyway, I changed that, and now I can't access readynas SMB share all period. Windows gives me erorrs about network name not existing or something.
I tried to change the windows box to home network rather then business network, but after reboot it always comes back as business network, I don't know if that's because Readynas is broadcasting somehting that Windows10 is automatically reacting too.
Ok...so what is the proper way to configure SMB file sharwing between Readynas and Win10...then after that, what do you guys think I will need to do so that the windows box can run VPN, while accessing local computers and SMB shares in my home network will avoid VPN?
7 Replies
Replies have been turned off for this discussion
Do you have the same issue when you addrerss the NAS by name and IP address? I have a persisting problem accessing by name (which can be worked around using the HOSTS file, but that's not a solution) but have no issue accessing by IP address.
its working 100% with my macs, by name, nothing needed in hosts file.
I don't know if its the name on windows10 or what...don't know if there exists a hosts file for windows or where that would be.
Yes, it is clearly a Windows issue. If you don't know if it does the same thing using the name and IP, then try it. Google is you friend for the Windows Hosts file location.
Dewdman42 wrote:
but then I tried to start up IPVanish for VPN and it immediately killed my SMB access to readynas.
This is running on Windows? (assuming so, but want to confirm).
Dewdman42 wrote:
I tried to change the windows box to home network rather then business network, but after reboot it always comes back as business network, I don't know if that's because Readynas is broadcasting somehting that Windows10 is automatically reacting too.
I am not sure what you mean here, but I don't think this is related to ReadyNAS. If you want to confirm that, just disconnect the NAS from the network when you do it.
Dewdman42 wrote:
Ok...so what is the proper way to configure SMB file shariing between Readynas and Win10...
Since this is working w/o IPvanish, I think you it is already configured correctly. My own approach is to set up the NAS for "everyone" access (both network and file access). All Windows PCs have NAS account credentials in the Windows Credentials Manager for both the NAS hostname and it's IP address. In my case I am using the NAS admin account for both. All the shares also have the owner/group set to admin/admin. Though the reason for using admin is that it translates when using rsync backup to legacy (OS 4) ReadyNAS. Guest doesn't. So if you aren't mixing legacy and OS6 NAS, you can stick with guest/guest for the default ownership.
You could of course use a different user account for credentials.
I've also enabled SMB3 transport encryption.
Dewdman42 wrote:
I tried to set the windows machine to Private rather the public network, since its at home. My hope was that by doing this, VPN would consider everything at 192.168.x.x as local and private stuff that should not be encrypted, including SMB access to readynas, while everything going out to ISP would be.
The local network should be set to private - one reason is that by default Windows disables SMB on public networks, and you don't want to change that setting. But that won't affect routing. If you can't ping the NAS by it's IP address when IPVanish is running, then you clearly have a routing issue.
- Have you tried contacting IPVanish tech support?
- Is your configuration using OpenVPN?
So it works fine by name as long as I don't start the VPN. I do not understand why the VPN should kill the connection.
What is the windows credentials manager you speak of?
Windows10 by default had the network set to public. I did change it to private, but it made no difference, VPN still drops connection to Readynas SMB.
I did not move to SMB3 yet, I'm not sure if my OSX Sierra computers are able to handle SMB3. Do you know?
Yes I believe it is using OpenVPN.
Dewdman42 wrote:
So it works fine by name as long as I don't start the VPN. I do not understand why the VPN should kill the connection.
Can you ping the NAS IP address when the VPN is started?
The VPN changes the Windows routing, to route all internet traffic through the encrypted tunnel to the VPN server. The way this works is that OpenVPN creates a virtual network adapter, and changes the routing tables in Windows to send traffic through that adapter. You don't want to route local traffic through that adapter, but in some setups it does. The first thing to figure out is whether that is happening in your case.
One possibility is that the virtual adapter is using the same address space your home network is using (192.168.1.x). You can open a CMD box with the VPN running, and enter ipconfig. That will give you some information on what IP address is assigned to the VPN adapter.
If you can ping the NAS by IP address, then also try entering \\nas-ip-address in file explorer, and see if that works. The VPN software will also adjust how name resolution is done (because if you use your ISP's DNS server, your ISP will know where you are browsing). Name resolution is different from routing, and would need a different solution.
I do suggest contacting ipvanish support - this issue isn't about the ReadyNAS, and I'm sure other ipvanish customers have had the same problem with network shares (and likely network printers as well).
Dewdman42 wrote:
I did not move to SMB3 yet, I'm not sure if my OSX Sierra computers are able to handle SMB3. Do you know?
Enabling SMB3 on the NAS doesn't disable SMB 1 and SMB 2. So it is safe to enable it. Just don't set SMB3 transport encryption to "required", as that will disable SMB 1 and 2.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
