samba - Jul 2021 - - Unable to access share from Windows 2012 client

Since this is an very old samba version, i think the best fix for this person is
also to setup as stand-alone.
 https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server

His Solaris 10 has support until 2024 i believe. 
But he should update it to latest build/patch.. I think he can get upto samba
4.1, or he needs to compile it himself.

His "workgroup" is abused with a AD-domain, and... 
https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/naming-conventions-for-computer-domain-site-ou#netbios-domain-names

Quote "Periods shouldn't be used in Active Directory domains."

So, in my opinion, the "quick fix" is, setup as standalone server. 
You already use hosts allow in smb.conf
So setup as wiki shows. 

Then, if needed, play with the client/server min/max protocols,
but i dont think thats needed after you setup as wiki shows. 

Greetz, 

Louis
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Rowland Penny via samba
> Verzonden: woensdag 14 juli 2021 16:23
> Aan: sambalist
> Onderwerp: Re: [Samba] - Unable to access share from Windows 
> 2012 client
> 
> On Wed, 2021-07-14 at 18:59 +0530, suresh b wrote:
> > Hi Rowland,
> > 
> > Thanks for your response. 
> > 
> > Samba version is : Version 3.6.23 
> > 
> > Also enclosed smb.conf file for your reference. 
> 
> For those who didn't get the smb.conf file because this list strips
> attachments, here it is (with comments and default lines removed):
> 
> [global]
>    workgroup = UG.DCM.in 
>    server string = Samba Server
>    security = share 
>    hosts allow = 10.179.6.60 10.179.3.60 10.179.3.62 
>    guest account = nobody 
>    log file = /var/samba/log/log.%m
>    max log size = 16384
>    log level = 2
>    log file = /var/samba/samba.log.%m
>    max log size = 512
> 
> [Dataflow_Processed]
>    comment =Prod Dataflow Processed
>    path = /processed
>    writable = yes
>    guest ok = yes
> 
> [Dataflow_Error]
>    comment = Prod Error
>    path = /dataflow/error
>    writable = yes
>    guest ok = yes
> 
> What is the DC ? I cannot see it being an NT4-style PDC, so 
> 'security > share' (which doesn't exist in 3.6.23) should be
'security = ADS'
> 'UG.DCM.in' doesn't look like a Netbios domain name (aka 
> workgroup), it
> looks like a kerberos realm, it should be a single word 
> (quite possibly
> 'UG')
> You do not have any 'idmap config' lines, so you are not going to
have
> any AD users or groups.
> You have 'guest ok = yes' in the shares, but because you do not
have
> 'map to guest = bad user' in '[global]', you will not
actually get
> guest access.
> 
> To only use SMB2 and above, add these lines to smb.conf:
> 
> client min protocol = SMB2
> server min protocol = SMB2
> 
> You are still using Solaris and I think (because of the Samba version)
> it is an EOL version.
> 
> Rowland
> 
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
>

On Wed, 2021-07-14 at 16:38 +0200, L.P.H. van Belle via samba
wrote:
> Since this is an very old samba version, i think the best fix for
> this person is also to setup as stand-alone. 
>  
> https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server
> 
> His Solaris 10 has support until 2024 i believe. 
I believe that Solaris 10 went EOL 3 years ago, unless you have
extended support and I don't think the OP has, or he wouldn't be asking
here.
> But he should update it to latest build/patch.. I think he can get
> upto samba 4.1, or he needs to compile it himself. 
Probably would need to compile it, if all the required develop files
are available.
> 
> His "workgroup" is abused with a AD-domain, and... 
>
https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/naming-conventions-for-computer-domain-site-ou#netbios-domain-names
> 
> Quote "Periods shouldn't be used in Active Directory
domains."
> 
> So, in my opinion, the "quick fix" is, setup as standalone
server.
> You already use hosts allow in smb.conf
> So setup as wiki shows. 
> 
> Then, if needed, play with the client/server min/max protocols,
> but i dont think thats needed after you setup as wiki shows. 
You still need to turn off SMBv1

Rowland