Cannot Access NAS-server after Win10 update

jimbo45 · 08 Nov 2018

Hi folks

@philosopher

W10 updates cause this problem regularly but typically problems appear with latest version of 1803 and all versions of build 1809.

You'll need to change this in the SAMBA.CONF file on your NAS -- it's usually in a folder /etc/samba. You'll need root (su) or sudo access

in the [global] section

max protocol = NT1

(Use NT1 instead of SMB1 in the samba config).

Restart samba -- if you don't know how to do that then re-boot the NAS.

Otherwise again as root (su) or sudo from the console type

service smb(d) restart
service nmb(d) restart.

the (d) is in brackets because depending on the OS of your NAS you might have smbd / nmbd. Both services need to be re-started.

now it's fine

Cannot Access NAS-server after Win10 update-sam.png

and from the NAS

Cannot Access NAS-server after Win10 update-snapshot8.png

cheers
jimbo

M A Weiss · 30 Mar 2022

I have been dealing with this problem for years.

First, I would unplug the drive from the NAS and plug it into my PC to copy files to it.

Then later, I found that I could run Win 7 in a virtual session and copy the files that way.

Windows 10 Pro cannot do what Windows 7 can do.

I made a screen capture of what I'm experiencing:

Windows 10 Cannot Connect to NAS, but Windows 7 Can - YouTube

As you can see, Win 7 has no problem--even running on Win 10 Pro. But Win 10 Pro cannot access it. I get the remote procedure call failed error. I have been researching this problem since 2017 and have tried SCORES of "solutions" and not one has worked.

M A Weiss · 27 Apr 2022

None of these suggestions worked for me. For four years I've been trying to get Win 10 Pro machines to access an NAS attached to a WRT3200ACM with no success. Every other PC, whether it be Win XP, Win 7 Pro, Win 10 Home or LINUX, including my Oppo UDP-203, have never had a problem accessing this media drive. My two Win 10 Pro machines have never been able to do this. Even after enabling SMB 1.0 and NetBIOS.
The odd part is that in late March, Win 10 Pro had a 3 week window where access to the NAS worked, and it was automatic. For a week, I could access NAS drive by device name only--IP address would produce an error. After a week, the device name failed to work, so I tried IP address and that worked--for two weeks. then I rebooted my PC last night and can no longer access the NAS at all. Other devices NOT running Win 10 Pro can access it without issue.
If it weren't for the fact that so much of my software suite only runs on Windows or Mac, I would be running LINUX now. Windows has had over 30 years to figure out networking and they STILL can't get it right.