search for: lanman1

...with an active directory domain controller? On Apr 3, 2016 11:21 PM, "barış tombul" <bbtombul at gmail.com> wrote: > my conf win10 no problem: > client NTLMv2 auth = Yes > client lanman auth = No > server max protocol = SMB3_11 > server min protocol = LANMAN1 > client max protocol = SMB3_11 > client min protocol = CORE > > > 2016-04-02 22:52 GMT+03:00 Helmut Hullen <Hullen at t-online.de>: > > > Hallo, Luke, > > > > Du meintest am 02.04.16: > > > > > Also, when I run testparm -svv | less I...

Hallo, Luke, Du meintest am 02.04.16: > Also, when I run testparm -svv | less I can find these four lines on > both the working and non-working servers: > server max protocol = SMB3 > server min protocol = LANMAN1 > client max protocol = NT1 > client min protocol = CORE Perhaps a max protocol = NT1 in the global section helps. And then Samba needs a restart. Viele Gruesse! Helmut

On Fri, May 31, 2019 at 06:32:56PM +0200, Andreas Reichel via samba wrote: > Dear samba team, > > I have a lot of hobby projects including old PCs. I wanted to hook up a Win3.11 machine to my current > Arch-Linux Workstation running samba 4.9.4. > > I have used the following configuration: > > [global] > workgroup = HOMEBASE > netbios name = Orcane > wins

On Fri, May 31, 2019 at 07:09:44PM +0200, Andreas Reichel wrote: > > > > > > > When adding me as the user with 'smbpasswd -a andreas', and entering a password, > > > no LANMAN hash is generated. The generated smbpasswd entry always contains 32 X as the first hash. > > > > > > When I do the same with Samba 4.3.11-Ubuntu, the hash IS

Hi, I use eCS as client for samba. with samba 2.2.x I have never problems after configuration. With update my server from suse 8.1 to 9.1 was also samba changed from 2.2.x to 3.0.x. Since this I have only truble. max protocol lanman1 works without problems, only .. I have no longnames. The docs says, lanman1 is the first with long names support, also not about the pm (desktop from os2). With lanman2 (or higher) I see longnames in the commandline. I can save/create files, I can not copy this this commanline tools, only read a...

On Fri, 2019-05-31 at 22:33 +0200, Andreas Reichel via samba wrote: > On 31.05.19 22:07, Andrew Bartlett wrote: > > On Fri, 2019-05-31 at 11:40 -0700, Jeremy Allison via samba wrote: > > > On Fri, May 31, 2019 at 07:09:44PM +0200, Andreas Reichel wrote: > > > > > > When adding me as the user with 'smbpasswd -a andreas', and entering a password, > >

Dear samba team, I have a lot of hobby projects including old PCs. I wanted to hook up a Win3.11 machine to my current Arch-Linux Workstation running samba 4.9.4. I have used the following configuration: [global] workgroup = HOMEBASE netbios name = Orcane wins support = Yes client signing = No domain master = No lanman auth = Yes log file = /var/log/samba/%m.log max log size = 50 name

On 31.05.19 18:47, Jeremy Allison wrote: > On Fri, May 31, 2019 at 06:32:56PM +0200, Andreas Reichel via samba wrote: >> Dear samba team, >> >> I have a lot of hobby projects including old PCs. I wanted to hook up a Win3.11 machine to my current >> Arch-Linux Workstation running samba 4.9.4. >> >> I have used the following configuration: >> >>

Hello, I currently run samba with server min protocol = NT1 but I need to move towards server min protocol = SMB2 is there any way I can detect which clients still use the older protocol versions? I would like to estimate the impact of the change before i do close NT1/SMB1. Thank and kind regards, Heiner Billich

...rotocol = CORE server max protocol = NT1 client max protocol = SMB3 client ipc signing = No (I have had problems with SMB2 even tho samba 3.6.x , Win 7 and Win 2008 shd support it.) On my working samba 4.x system (on fedora core 23), testparm -v shows server min protocol = LANMAN1 min protocol = LANMAN1 client min protocol = CORE client ipc max protocol = default client ipc min protocol = default client ipc signing = default Appreciate any advice. Thanks

...you'll find it ugly, but it works. Under CORE protocol, the $"#&^ MS client sends unencrypted passwords to the samba server (maybe there is no support of encryption in CORE, I don't know). So as my clients are either W95, WfW, NT or DOS machines, I simply remove the support of LANMAN1 and LANMAN2 protocols in the negotiation between Samba and the client. All machines which are not DOS will agree on a higher protocol anyway ... The only trade-off (?) is that at the first time, the DOS clients have to connect with the syntax : net use \\machine\share%username [password], no big...

...smb.conf is : [global] netbios name = SAMBASERVER netbios aliases = sambaserver server string = SambaServer security = SHARE encrypt passwords = Yes log level = 100 log file = /var/log/samba/%m.log max log size = 0 protocol = LANMAN1 max protocol = LANMAN1 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 os level = 33 preferred master = False domain master = False dns proxy = No guest account = pcuser printing = lprng [workinprogress] comment = s...

...see on https://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html Normally this option should not be set as the automatic negotiation phase in the SMB protocol takes care of choosing the appropriate protocol. Default: //|server max protocol|/ = |SMB3| / Example: //|server max protocol|/ = |LANMAN1| / -- -James

Okay then, this sounds very bad :-( One more thing: There is a system using PAM SMB (https://www.samba.org/~airlied/) with lanman1 protocol on port 139. After upgrading our domain level, will we be able to keep some MEMBER servers, to which this PAM SMB remains to be able to authenticate via TCP/139 and some kind of NTLM (let's say NTLMv1) authentication, or even member servers will only authenticate via kerberos? Thank y...

On 10/03/2023 14:18, Tam?s N?meth via samba wrote: > Okay then, this sounds very bad :-( One more thing: There is a system using > PAM SMB (https://www.samba.org/~airlied/) with lanman1 protocol on port > 139. After upgrading our domain level, will we be able to keep some MEMBER > servers, to which this PAM SMB remains to be able to authenticate via > TCP/139 and some kind of NTLM (let's say NTLMv1) authentication, or even > member servers will only authenticate vi...

...t; client ipc signing = No >> >> (I have had problems with SMB2 even tho samba 3.6.x , Win 7 and Win 2008 >> shd support it.) >> >> >> On my working samba 4.x system (on fedora core 23), testparm -v shows >> >> >> server min protocol = LANMAN1 >> min protocol = LANMAN1 >> client min protocol = CORE >> client ipc max protocol = default >> client ipc min protocol = default >> client ipc signing = default >> >> >> >> >> Appreciate any advice. >> >&...

...winbind use default domain = false winbind offline logon = false server string = linuxserver1 netbios name = linuxserver1 winbind enum users = yes winbind enum groups = yes winbind nested groups = yes client max protocol = LANMAN1 client use spnego = yes #client ldap sasl wrapping = plain #ldap server require strong auth = yes kccsrv:samba_kcc = no ntlm auth = yes smb2 leases = no allow trusted domains = yes vfs objects = acl_xattr map...

...uest but not receiving the answer it requires to > make the connection. > I thought that something like that might be the problem, but I can connect from a win10 machine to a standalone Samba 4.4.5 server, which has these as the defaults: server max protocol = SMB3 server min protocol = LANMAN1 So, as Windows PE 10 is probably a subset of Windows 10, it should work. It is definitely worth trying, but if it doesn't work, then it could be a bug, but in Windows PE 10 not Samba. Rowland

Hi, Installed latest Samba3.0.2a on NT4 domain, security = domain and net rpc join successfully. everything work great, but group permission failed, error message is "user_in_winbind_group_list: nametogid for group NTGROUP failed". smb.conf on shares as below: ===================== omitted base configurations... [shareA] path = /public/shareA valid users =

...ase and not Novell database, how can I do this? I send my configuration of smb.conf file: # Global parameters workgroup = "I put here the NIS name..." netbios name = STATION1 server string = Serveur Samba password server = station1 protocol = LANMAN1 announce version = announce as = win95 name resolve order = host lmhosts wins bcast domain master = Yes hosts allow = "I put here my IP domain" [hp4m_4_gt] comment = HP4M Postscript, labo GT, 4eme etage path = /tmp/samba/lp-spool/h...