Problems using SMBv2 only

[nikkoaki]

I've been having problems trying to use SMBv2 only on my AC66U. I was using SMBv1 + SMBv2 with no (major) problems but when i updated to the latest firmware i decided to try just v2 for security reasons.
As soon as i changed it i noticed i couldn't access my shares anymore and the router's log was getting spammed with errors

Apr 29 17:48:35 smbd[14719]: [2018/04/29 17:48:35.992402,  0] smbd/negprot.c:706(reply_negprot)
Apr 29 17:48:35 smbd[14719]:   No protocol supported !
Apr 29 17:48:37 smbd[14721]: [2018/04/29 17:48:37.697373,  0] smbd/negprot.c:706(reply_negprot)
Apr 29 17:48:37 smbd[14721]:   No protocol supported !
Apr 29 17:48:38 smbd[14722]: [2018/04/29 17:48:38.541404,  0] smbd/negprot.c:706(reply_negprot)
Apr 29 17:48:38 smbd[14722]:   No protocol supported !
Apr 29 17:51:17 smbd[14844]: [2018/04/29 17:51:17.052940,  0] smbd/negprot.c:706(reply_negprot)
Apr 29 17:51:17 smbd[14844]:   No protocol supported !

I then switch to SMBv1 only, tested it and it was working fine. Then i tried SMBv1 + v2 again and it worked fine also (i checked the smb version my pc was using in powershell and it said v 2.02). I tried just SMBv2 one more time and it failed again, giving me those error messages in the log.
I was able to browse my shares with just SMBv2 after a (router) restart... i thought it was the only thing it needed to be fixed but when i woke up this morning and tried to access them again, i couldn't reach them and it was giving me errors again.
I tried with a laptop (win 8.1), desktop (win10) and an android phone (with an app that supports SMBv2).

Any help is appreciated.

 

[ColinTaylor]

The error messages are probably from when you had SMBv1 enabled on your client.

Remember that "browsing" network shares in Windows Explorer is a function of SMBv1, you can't do that in SMBv2. With only SMBv2 enabled you have to manually type in the complete address of the share into the application, or map the drive.

 

[nikkoaki]

Thanks for your reply.

The error messages appear when i click "refresh" to make windows search for devices. Since you told me that's a SMBv1 only feature, it makes sense then.
I tried it again, trying to discover the network device creates those errors as expected. Mapping the drive works flawlessly.
Thanks a lot.

I would never suspected that they would remove such a feature.
Do you know why this is? Does it mean that for ex, my win 8.1 machine is able to see my other win10 machine because it is "broadcasting" itself with SMBv1? I ask this because i deactivated SMBv1 on my win8.1 machine via powershell and my other machine with win10 can see it clearly, or did they bring the feature back with SMBv3? (Or am i completely mixing things up, like some sort of "windows only" zeroconf that samba doesn't use? ps: i'm a network newbie)

 

[ColinTaylor]

I don't know the development history for SMB so I don't know why there's no browsing equivalent in SMBv2+. Windows 7 onwards (and probably earlier) have different methods of being discovered on the network and don't need SMB anymore. That's why if you turn off SMB completely on all your Windows machines they can still detect each other, but SMB-only machines (like Samba on Linux) become invisible to Windows and vice versa.

You don't need to use powershell to turn off SMBv1 in Windows 8.1/10, you can do it easily through "Turn Windows features on or off".

 

[nikkoaki]

I see
Thanks again!

 

[joe scian]

I got exactly the errors above this evening accessing windows shares using Map Network Drive. All Drives are available - just these errors appeared in log when using SMB V2 only.

un  5 18:45:13 RT-AC5300 smbd[6535]: [2019/06/05 18:45:13.607449,  0] smbd/negprot.c:706(reply_negprot)
Jun  5 18:45:13 RT-AC5300 smbd[6535]:   No protocol supported !
Jun  5 18:45:13 RT-AC5300 smbd[6538]: [2019/06/05 18:45:13.762168,  0] smbd/negprot.c:706(reply_negprot)
Jun  5 18:45:13 RT-AC5300 smbd[6538]:   No protocol supported !
Jun  5 18:45:13 RT-AC5300 smbd[6539]: [2019/06/05 18:45:13.797730,  0] smbd/negprot.c:706(reply_negprot)
Jun  5 18:45:13 RT-AC5300 smbd[6539]:   No protocol supported !
Jun  5 18:45:13 RT-AC5300 smbd[6540]: [2019/06/05 18:45:13.824240,  0] smbd/negprot.c:706(reply_negprot)
Jun  5 18:45:13 RT-AC5300 smbd[6540]:   No protocol supported !

 

[ColinTaylor]

I got exactly the errors above this evening accessing windows shares using Map Network Drive. All Drives are available - just these errors appeared in log when using SMB V2 only.

Just ignore the messages.

 

[joe scian]

Just ignore the messages.

Yes will do it thanks