can't access shares from one specific PC

---

Case850 wrote:

Seijdel

Due to security concerns Microsoft have disabled SMB1 and have moved to SMB3 on Windows 10. Unfortunately many Netgear routers do not support SMB3 and this is most likely the cause of your problem.

 

https://support.microsoft.com/en-au/help/4034314/smbv1-is-not-installed-by-default-in-windows

---

Case850, unfortunately SMB3 alone isn't the answer. True, MS on W10 since the Fall Creator update (V1709) has basically removed SMB1 from PC (guaranteed on new fresh installs, but others such as Updates and user enabled SMB1 in some cases do remain, even if for a short time) installation that does hinder sharing on LAN's.

 

I can prove that both the R7000 and R8000 for instance DOES have SMB 3 enabled on the router. Still, SMB 1 is required on clients to use shares over the LAN.

 

Reason, it has to be exposed, and NETBIOS names must be sent out via requests and THAT is not happening without using the SMB 1 version. Has to do with WSD https://en.wikipedia.org/wiki/Web_Services_for_Devices which appears to be the problem as not implemented in the router.

 

I have an OPEN case with NG support since 3/31 of this year on this subject. Up until 2 weeks ago I got back the SAME answer every time (maybe 4 times they tried to close it as a W10 problem), I must use SMB 1 to reach the shares using W10. Each time I went back with the SAME MS link calling for it to be NOT used and contact the vendor to use SMB 3 instead... and even the JamesGL post from over a year ago stating this problem IS known and NG is working on correcting it.

 

2 weeks ago NG support from Taiwan got on my PC and I demonstrated the problem with and without SMB 1 enabled. First with SMB 1 enabled I opened Windows Explorer to see the USB drive contents, ran NET VIEW,  NET VIEW \\READYSHARE, NET VIEW \\192.168.1.1 and a NET USE as well. All worked fine. Then I disabled SMB 1, rebooted, reconnected with NG Support and tried the same thing.... READYSHARE could not be seen at all except for NET VIEW \\192.168.1.1, not even could the router be seen in Windows Explorer (but the router itself did show). Interestingly at this point my connection to them (Teamviewer) dropped a few times and when reconnected at one point I had 3 different ID's connected to me... usually only 2 though, but when SMB 1 was enable only one connection was there? My only way to converse with them was to have NOTEPAD open and type into it. With SMB 1 disabled the agent told me they had NEVER seen this problem before and NET VIEW as 'new' to him. Probably why others connected to see the same thing. I asked why since this was easy to recreate they had NOT done this, and all agent said was they were not able to??? At the end the agent said they had to do some research even on WSD, but they do see the problem and what MS 'suggests'. I did prove that SMB 3 was running on the router, and they knew that, and that was one reason they didn't understand why SMB 1 was required...

 

Time will tell if I made any progress on this. I got the feeling this problem is 'new' to them and they didn't fully understand the total picture and felt SMB 3 was all that was required.

 

Along with this the MASTER BROWSER and COMPUTER BROWSER functions are involved. In the Spring Creator Update by MS (W10 V1803) removed HOME GROUPS that used those... and they appear to be gone too from W10 systems...

 

A good web page to read is http://woshub.com/network-computers-not-showing-windows-10/. Particularly the part lower down, "SMB 1.0 and problems with Master Browser in Windows 10". Using WIRESHARK it appears as the router is not responding to a request for the MASTER BROWSER list from a PC and that causes a 1231 error for NET VIEW when SMB 1 is not enabled.