Modification à apporter pour dialogue entre client windows et serveur samba :1-Version de windows server : 2003, 2008, 2008 R2 ?
https://blogs.technet.microsoft.com/...s-file-server/SMB2 (technically SMB2 version 2.002) which is the version on Windows Vista SP1 (or later SP) and Windows Server 2008 (or any SP)
SMB2.1 (technically SMB2 version 2.1) which is the version on Windows 7 (or any SP) and Windows Server 2008 R2 (or any SP)
2-Choisir le protocole SMB approprié vis à vis de la version samba :
*SMB 1 introduced in DOS days, and was also called CIFS in its later version (think of it like SMB 1.1). First versions of Samba 1.x supported SMB and CIFS
*SMB 2.0 / SMB2.02 introduced with Windows Vista/2008 is supported with Samba 3.6
*SMB 2.1 introduces with Windows 7 / Windows 2008 R2 is supported with Samba 4.0.0
*SMB 3.0 introduced with Windows 8 / Windows 2012 is supported by Samba 4.2
*SMB 3.02 introduced in Windows 8.1 / Windows 2012 R2 is not yet supported by any version of Samba (its in the works I assume)
*SMB 3.11 introduced in Windows 10 is not yet supported by any version of Samba (its in the works I assume)
2bis-Désactivation du client SMBv1 avec la stratégie de groupe ?? :
3-Activer/désactiver le protocole LM/NTML :
LmCompatibilityLevel
0 Clients use LM and NTLM authentication, but they never use NTLMv2 session security. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
1 Clients use LM and NTLM authentication, and they use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
2 Clients use only NTLM authentication, and they use NTLMv2 session security if the server supports it. Domain controller accepts LM, NTLM, and NTLMv2 authentication.
3 Clients use only NTLMv2 authentication, and they use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
4 Clients use only NTLMv2 authentication, and they use NTLMv2 session security if the server supports it. Domain controller refuses LM authentication responses, but it accepts NTLM and NTLMv2.
5 Clients use only NTLMv2 authentication, and they use NTLMv2 session security if the server supports it. Domain controller refuses LM and NTLM authentication responses, but it accepts NTLMv2.
4-Security signature des mots de passes
*enabling LM and NTLM hashes to be as part of the security policy are Network security: LAN Manager authentication level Send LM & NTLM responses
*changing the 【HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa \【LmCompatibilityLevel 】 value of the registry key to 0 as per here
*Adding the following parameters to LanmanWorkStation and NetLogon in the registry HKLM\System\CCS\Services\LanmanWorkstation\Parameters DWORD DomainCompatibilityMode = 1 DWORD DNSNameResolutionRequired = 0
*HKLM\System\CCS\Services\Netlogon\Parameters DWORD RequireSignOnSeal = 0 DWORD RequireStrongKey = 0
5-Configurer le domain controller accept ??
6-Configurer le groupe résidentiel & centre de réseau et partage
7-Tenter la connexion :
NET USE Z:\\NOM_SERV\Folder_Share MDP_userX /user:userX
NET USE Y: \\SERVEUR\Parents mot_passe_samba_parent1 /user:parent1
Ou net view
Client linux ou macos : smb://ip_serveur/chemin/du/dossier
Compatibilité SMB et serveur samba• SMB 1 introduced in DOS days, and was also called CIFS in its later version (think of it like SMB 1.1). First versions of Samba 1.x supported SMB and CIFS
• SMB 2.0 / SMB2.02 introduced with Windows Vista/2008 is supported with Samba 3.6
• SMB 2.1 introduces with Windows 7 / Windows 2008 R2 is supported with Samba 4.0.0
• SMB 3.0 introduced with Windows 8 / Windows 2012 is supported by Samba 4.2
• SMB 3.02 introduced in Windows 8.1 / Windows 2012 R2 is not yet supported by any version of Samba (its in the works I assume)
• SMB 3.11 introduced in Windows 10 is not yet supported by any version of Samba (its in the works I assume)
A moins qu'il n'y ai autre chose, je ne vois pas, ...
Serveur vue sur le réseauComment s'assurer qu'un serveur soit vu sur le réseau ?
Le serveur est vu sur le réseau avec un client debian mais non un client Windows.
Ce serait donc bien cet histoire de protocole SMB qui serait la cause de ceci ?