On 01/08/2019 14:38, Helmut Harnisch wrote:
> Am 01.08.2019 um 14:17 schrieb The Natural Philosopher:
>> I seems that:
>>
>> 1/. Win10 requires at least SMBV3 or it wont connect UNLESS
>>
>> - you tell windows ten to use SMB v1

SMB1 client and server are installed

> Here: Windows 1903 (Build 18362.267)
> and SMB v1 not enebled:
> Get-SmbServerConfiguration
>
>
> AnnounceComment                 :
> AnnounceServer                  : False
> AsynchronousCredits             : 64
> AuditSmb1Access                 : False
> AutoDisconnectTimeout           : 15
> AutoShareServer                 : True
> AutoShareWorkstation            : True
> CachedOpenLimit                 : 10
> DurableHandleV2TimeoutInSeconds : 180
> EnableAuthenticateUserSharing   : False
> EnableDownlevelTimewarp         : False
> EnableForcedLogoff              : True
>                                                  EnableLeasing
>          : True
>                          EnableMultiChannel              : True
>
> EnableOplocks                   : True
>                                                  EnableSecuritySignature
>          : False
> ___________________________________________
> EnableSMB1Protocol              : False
> EnableSMB2Protocol              : True
> ____________________________________________
> EnableStrictNameChecking        : True
> EncryptData                     : False
> IrpStackSize                    : 15
> KeepAliveTime                   : 2
> MaxChannelPerSession            : 32
> MaxMpxCount                     : 50
> MaxSessionPerConnection         : 16384
> MaxThreadsPerQueue              : 20
> MaxWorkItems                    : 1
> NullSessionPipes                :
> NullSessionShares               :
> OplockBreakWait                 : 35
> PendingClientTimeoutInSeconds   : 120
> RejectUnencryptedAccess         : True
> RequireSecuritySignature        : False
> ServerHidden                    : True
> Smb2CreditsMax                  : 2048
> Smb2CreditsMin                  : 128
> SmbServerNameHardeningLevel     : 0
> TreatHostAsStableStorage        : False
> ValidateAliasNotCircular        : True
> ValidateShareScope              : True
> ValidateShareScopeNotAliased    : True
> ValidateTargetName              : True
>
> But it sees the pishares:
> net view bigbrother2
> Freigegebene Ressourcen auf bigbrother2
>
> bigbrother2 server (Samba, Ubuntu)
>
> Freigabename  Typ      Verwendet als  Kommentar
>
>
-------------------------------------------------------------------------------
> MP-C3003      Drucker                 RICOH MP C3003
> pishare       Platte                  Pi Shared Folder
> Der Befehl wurde erfolgreich ausgeführt.
>
>
>>
>> 2/. Windows ten will not 'browse' a network AT ALL. Yiou have to know
>> where you want to connect., Soe sites suggest this is cinfiguranble on W10
> you have to enable the "Datei und Druckerfreigabe" (turn on network
> discovery in your different network profiles under Control Panel - All
> Control Panel Items - Network and Sharing Center - Advanced Settings)

Windows 10 does browse the network. I can see all my other Windows
machines. And now also the raspberry pi. It shows up, but I can't connect.

>> 3/. Later versions of SAMBA can be forced to use SMB V2 or V3 by putting
>>
>>
>> protocol = SMB3
>>
>>      or
>>
>> protocol = SMB2
>>
>> into the [global] section of the smb.conf file
> Thats not in my smb.conf and it works nevertheless. But its an ubuntu 19.04

I will try this.

--- SoupGate-Win32 v1.05