Windows 10 does not see NAS

[Станислав Димитров]

Hi,

I really wanted to avoid opening a topic and spamming the group but I'm getting desperate. I've a DNS 320L and run the RC6. No matter what I do my Windows 10 simply refuses to see my see my NAS regardless what settings I put in Samba. I have no problem opening the smb:// path through Linux - both my Linux install and through a virtual machine in my Windows. When I try to connect to the NAS I get an error message saying that "The specified network name is no longer available", regardless if I use the LAN IP of the NAS or the Host Name. Here are my Samba settings:

I get the error message regardless whether I set Allow to anybody or my user.

I'm not the most Linux or network savvy person in the world, so if anybody could tell me what am I missing, I'd be very thankful.

Best regards,

Stan

PS I can add the NAS as a media device after installing the proper packages. However, I really want to be able to map it and use it as a shared drive in my local network.

[João Cardoso]

On Tuesday, 4 April 2017 00:14:51 UTC+1, Станислав Димитров wrote:

Hi,

I really wanted to avoid opening a topic and spamming the group but I'm getting desperate. I've a DNS 320L and run the RC6. No matter what I do my Windows 10 simply refuses to see my see my NAS regardless what settings I put in Samba. I have no problem opening the smb:// path through Linux - both my Linux install and through a virtual machine in my Windows. When I try to connect to the NAS I get an error message saying that "The specified network name is no longer available", regardless if I use the LAN IP of the NAS or the Host Name.

But if you browse the network in Win-10  does the box appears? And can you see its shares and files?

Or is it only when you try to map the box share to a windows drive letter that you have problems?

Have you checked the SMB2 button in the Samba webUI and reboot the box and PC afterwards (should be done after enabling *or* disabling SMB2)

Or didn't you ever checked the SMB2 checkbutton? SMB2 is slower.

Is your PC in the same workgroup?

I don't have win-10, but there are positive reports from other users under the RC6 snapshot topic on that specific ms-win version (from the reported transfer speeds SMB2 was not in use)

 

Here are my Samba settings:

You say you are on RC6, but I don't see the "Use SMB2" checkbutton on your screenshot...

[Станислав Димитров]

So, it gets detected, sometimes, but not always. I just turned my NAS on and Windows managed to detect it and display it in the Network but when I click on it I get this:

If I try to map it - I get the same error. If I try to map via typing \\192'168.1.101\Share - I get an "The specified network name is no longer available" error. I cannot in any way browse or see my files on the NAS (technically only empty folders at this point) through Windows explorer. I can however easily open it via Filezilla or with smb://192.168.1.101 in Linux (both virtual machine and separate Linux install). I'm positively on RC6, it's just that last night in my desperation I tried installing one of the additional Samba packages, which seems to be an older version so the SMB2 option was missing when I took the screenshot. Anyway, I removed it and reverted to the default packages, enabled SMB2, rebooted but still nothing. Also - they're definitely in the same workgroup.
IDK - it's probably some Windows crap but I can't wrap my head around it... 

[João Cardoso]

Do your shares names or description are in cyrillic (if that is cyrillic :-)? Have your tried plain ASCII names? Is win10 sharing any folder?

IDK - it's probably some Windows crap but I can't wrap my head around it... 

Googling for your error message and number gives a lot of answers, including youtube videos, as you certainly know.

Not using MS since win-95, I consider most of them to be just rubbish. Some work for some users but not for others, user cumulative change things and end up not knowing what ultimately solved the problem, most solutions do not have a reasoning behind them... but some make sense.

I followed

https://social.technet.microsoft.com/Forums/windows/en-US/17c9ea7d-52df-4ef9-95fa-0a961d11bfa3/fix-for-cannot-access-nas-drives-sharefolder-is-not-accessible-or-error-code-0x80070035?forum=w8itpronetworking

and some seems to make sense; from some point in the discussion they start talking on NASes, and as most of them are linux based, that might offer some clues. It also seems that the problem also appeared after an automatic update on win 8 or 8.1.

Anyway I can't help with a solution, but try this one:

I finally gave up and thought about re-installing the whole system. But I did not start at once, as there was a bank holiday in Germany and I got a visit from my parents and spent time with my family. My father then asked me to copy some data yesterday and this was the first time I started the WIN 10 system again since Wednesday.... guess what happened: Everything was suddenly working again. I have no idea what happened in the depths of this system but I suppose it is quite weird.

Not as weird as it might sound. When trying the "new" samba package in RC6 with an old Vista PC, things (caching in both the server and client) took at while to settle. Caching must have a validity lifetime. That's why I talk on rebooting both the server and client after toggling SMB2. What happens in MS-Win I don't know, but I know that samba keeps some cached data under /var/cache/samba and, instead of a reboot on the box it is enough to stop samba, remove all cache files and start samba again. I guess that under MS-Win persistent (on disk) caching also happens, and cached data should become invalid if conflicting; samba docs say that some of these cache files should be preserved across reboots, but I deliberately choose to not do that because of disk not spinning-down issues.

One of the "solutions" I found interesting was to disable some "let windows handle it automatically".

All the solutions described here didn't work for me.

I'm using Windows10 Ent x64 and I can't even see the SynologyNAS in my network, but I can access is via any web browser.

My solution is:

1. Go to Control Panel>Network and Internet>Network and Sharing Center> Advanced sharing settings.

2. Remove the check box from [Turn on automatic setup of network connected devices.

Viola! Your NAS appeared on your network!

Regards,

Ali Tweel

Another interesting one talked on enabling the SMB1 protocol, another said to turn netbios on over tcp.

For me, a solution must be reproducible, i.e., if you turn something off and it solves the problem, then the problem should reappear if you turn the same thing on again. And if something doesn't solve the problem, undo the changes before trying another solution. But that's asking too much :-)

In any case, if you solve the issue, please let us know how.

[Todd Lowe]

Joao,

I also lost network access from Windows 10 when I upgraded a 320L to RC6 from 4.1.  Couldn't browse and couldn't connect explicitly via a UNC path.   At the time I tried changing smb settings, flipped between SMB2 and back, twiddled with SWAT. reverted to the ALT-f config, and it started working.   I saw this thread after that, but had no idea what I actually had done to make it start working again - using smb1. (and still don't know other than somehow when flipping between smb1 and 2, defaults, and not, and using SWAT, something wrote out changes that worked.)

Today I had some extra time, so I upgraded a 323 from 4.1 to RC6 and again lost samba access from Windows 10 to the newly upgraded NAS.  

I checked logs and config and found a small set of differences in the global section between the smb.conf on my working RC6 and the inaccessible one:

Working smb.conf global section:

[global]

server string = dns320l NAS - PHOTOS

map to guest = Bad User

passdb backend = smbpasswd

username map = /etc/samba/smbusers

log level = 1

syslog only = Yes

max log size = 32

enable core files = No

client ipc signing = auto

idmap config * : range = 

idmap config * : backend = tdb

hosts allow = 127. 192.168.10.0/255.255.255.0

use sendfile = Yes

print command = lpr -P %p %s; rm %s

Newly upgraded and inaccessible one:

[global]

server string = DNS-323 NAS

map to guest = Bad User

passdb backend = smbpasswd

username map = /etc/samba/smbusers

log level = 2

syslog only = Yes

max log size = 32

enable core files = No

client ipc signing = auto

server signing = auto

socket options = IPTOS_LOWDELAY TCP_NODELAY

idmap config * : backend = tdb

hosts allow = 127., 192.168.10.0/255.255.255.0

use sendfile = Yes

print command = lpr -P %p %s; rm %s

The first change I tried to make was to remove "server signing = auto" from the 323, essentially disabling signing for smb1 and setting it to auto for smb2.

I restarted smbd and now I can connect again (still smb1, not using 2), and everything seems to be working fine.  

Hope this is the root and can help anyone else running into this issue.

I have another 320 that is still on 4.1. I will post a followup if I have this issue with it and this conf change isn't enough to solve it.

Todd

[João Cardoso]

Hi,

I stopped Samba, commented the "server signing" and "max protocol" entries in /etc/samba/smb.conf, removed everything under /var/cache/samba (to avoid cache effects on Samba), started Samba, and tested on Windows Vista Business with no troubles, either browsing or mapping a share (and rebooting).

So it looks like "server signing = auto" only causes problems.

Unless someone else on other Windows versions claims that it is needed, the next release will have it disabled.

The samba-3.6.25 (RC6) manual page says:

server signing (G)

This controls whether the client is allowed or required to use SMB signing. Possible values are auto, mandatory and disabled.

When set to auto, SMB signing is offered, but not enforced. When set to mandatory, SMB signing is required and if set to disabled, SMB signing is not offered either.

Default: server signing = Disabled 

Thanks!

[Ram Set]

I can confirm that disabling the  server signing fixed the same issue (that surfaced on Win7).

[Iz]

Hi,

Can you please explain how you edited the file /etc/samba/smb.conf?

I am trying to resolve NAS access issues with a DNS-321 (Alt-F 1.0 with kernel 4.4.86), Windows 10 (I have activated SMB1)