inadmissible : F4-210 SMB access failed !!!!

[mpicollet]

Hello

No, I'm not in a Activated directory domain.

The problem is between Windows 10 and the NAS TOS system. Because if this is actually a standard, the procedure/help (smb) does not specify that we need to enter the netbios name of the NAS in prefix.

Moreover, the formalism without specifying the netbios name, works with the Net Use command. That concludes the debate!

To answer the SMB protocol, version 1 is enabled on my PC. I hope now that I can disable this version for a security issue...

Regards,

M.

[mpicollet]

Hello

SMBv1 disabled!
TNAS is still working!

Get-WindowsOptionalFeature -Online -FeatureName smb1protocol

FeatureName : SMB1Protocol
DisplayName : Support de partage de fichiers SMB 1.0/CIFS
Description : Support du protocole de partage de fichiers SMB 1.0/CIFS et du protocole Explorateur d’ordinateurs.
RestartRequired : Possible
State: Disabled

CustomProperties :
ServerComponent\Description : Support du protocole de partage de fichiers SMB 1.0/CIFS et du
protocole Explorateur d’ordinateurs.
ServerComponent\DisplayName : Support de partage de fichiers SMB 1.0/CIFS
ServerComponent\Id : 487
ServerComponent\Type : Feature
ServerComponent\UniqueName : FS-SMB1
ServerComponent\Deploys\Update\Name : SMB1Protocol

Regards

M.

[David M]

I'm a long way from a networking geek but here is a snippet of my experience.

Besides my TM, I also have a QNAP. I can set the SMB lower level and upper level on the QNAP. If I don't set the lower level to "1", my QNAP will not appear in Windows Explorer. My Terramaster also will not appear in Windows Explorer unless I type in its address. It then appears and I map the main data folder that I created.