search for: lanman2

...ested and also partial changes. Both are presenting the same behaviour. Nothing was changed in the AD side. I also re-checked the permissions/ownership on "/var/db/samba4/winbindd_privileged" folder which is used by SQUID. To Rowland: You asked if I really need the "min protocol = LANMAN2" option. Well, the idea was to enforce a minimum security level. Any help will be very appreciated. Regards Fabricio. -----Original Message----- From: Kontrol-Suporte <suporte at kontrolsecurity.com.br> Sent: Saturday, June 23, 2018 3:42 PM To: 'samba at lists.samba.org' &lt...

...ged' dir went away quite some time ago." Shouldn't that folder be there anymore? Everytime I install Samba47 or 48 it creates the folder with the "pipe" inside of it. I just needed to change the permissions/ownership to the folder. Isn't Ok to use that way anymore? About Lanman2: Hummm... now you got me confused. I could swear that option was to force ntlm v2 as minimum. The idea is to force NTLM v2 as minimum protocol. Should I use option "smb2" instead? Thanks a Lot, Fabricio. -----Original Message----- From: samba <samba-bounces at lists.samba.org>...

...t; > security = user > > > > passdb backend = tdbsam > > > > printing = cups > > printcap name = cups > > load printers = yes > > cups options = raw > > protocol = LANMAN2 > > map to guest = Bad User > > username map = /etc/samba/smbusers > > guest account = nobody > > log level = 2 > > ########### > > lanman auth = yes > > allow nt4 crypto = yes > >...

...workgroup = MYDOMAIN map to guest = never logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: usershare allow guests = no client NTLMv2 auth = yes client lanman auth = no client plaintext auth = no use spnego = yes client use spnego = yes min protocol = LANMAN2 idmap gid = 10000-20000 idmap uid = 10000-20000 realm = MYDOMAIN.CORP security = ads template homedir = /home/%D/%U template shell = /bin/bash winbind offline logon = yes winbind refresh tickets = yes winbind enum users = yes winbind enum groups = yes winbind nested groups = yes winbin...

...arge file results in 6M/s, but writing is only 2M/s, which is far below writing to an NT server (6M/s). If any of "read raw" or "write raw" is off, the result is the other way around, with writing a file to be around 6M/s, and reading around 2M/s. When I changed the protocol to LANMAN2, "read raw = yes" and "write raw = no" result in good throughput for both reading and writing. The only problem is that LANMAN2 doesn't support long filenames. So we looked at the source searching for places where "read raw" and "write raw" are used. To...

...re is what I've determined. Could some please verify this for me? Samba Microsoft CORE ??? (Something really old that I don't care about) COREPLUS ??? (Something really old that I don't care about) LANMAN LAN Manager (LM) LANMAN2 LAN Manager (LM) NT1 NTLMv1 ** Not Supported NTLMv2 Microsoft does not seem to differentiate between a LANMAN and a LANMAN2 on their website, I usually just see references to a "LAN Manager (LM)". I never see a reference on Microsoft.com to an &...

I have tried to upgrade our samba server from 3.6.18 to 3.6.22 but found that our DOS clients could no longer connect (using DOS 6.22 and Microsoft LAN Manager 2.1). With 3.6.18 we use smb.conf setting 'min protocol = LANMAN2' and it works great, with 3.6.22 although clients can connect ok, they cannot obtain a directory listing. Instead the first file (sometimes misnamed) just relists endlessly. Using loglevel 4 I find this text in log file when a DOS client connects to either version of samba 3.6: Request...

...the extended attributes are not applied. > > Since the Win32 API does not have a single function that overwrites a > file and associates extended attributes in one call, it is very unlikely > to cause any harm to windows clients. But OS/2 clients have this API > function and the LANMAN2 trans2open request is forwarded to create_file. > > I have no sufficiently detailed documentation of the LANMAN2 protocol, > but the OS/2 API docs for DosOpen clearly say: > > "peaop2 (PEAOP2) - in/out Extended attributes. > This parameter is only used to specify exte...

...mb.conf file [global] workgroup = Test netbios name = server security = user passdb backend = tdbsam printing = cups printcap name = cups load printers = yes cups options = raw protocol = LANMAN2 map to guest = Bad User username map = /etc/samba/smbusers guest account = nobody log level = 2 ########### lanman auth = yes allow nt4 crypto = yes mangled names = yes dos charset = CP850 unix charset...

...permissions/ownership on > "/var/db/samba4/winbindd_privileged" folder which is used by SQUID. I think you might want to check that again, the 'winbindd_privileged' dir went away quite some time ago. > > To Rowland: You asked if I really need the "min protocol = LANMAN2" > option. Well, the idea was to enforce a minimum security level. > I actually thought that, but 'LANMAN2' ??? why not 'NT1' at least. Have you considered using kerberos with squid ? Rowland

...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 deal. But I...

...h 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 and save as. no access about the pm, No Ideas, only dowgrade to Samba 2.2.x, this maks other truble with my wine. Dietrich

...n a workstation and are ok. the printer has full access to the network. unfortunally samba denies access: <snip filename="log.smbd"> [2005/10/06 14:46:22, 0] smbd/negprot.c:reply_negprot(557) No protocol supported ! </snip> in smb.conf we'd defined the max protocol as LANMAN2 on the printer we've tested following options: LM/NTLM NTLM NTLM2 allways the same message. samba version: 3.0.11 can somebody help / has somebody experiences? thx in adv kurt

...Hanging does happen on both, explorer and CMD. In Explorer it shows up to calculate how long it might take. In CMD nothing happend. - Afterwards Vista refuses to shut down. - Creating an File on the Share and saving it from within notepad does not cause any trouble. - Limiting protocol to lanman2 seems to help regarding the hangup. But it is raising other problems (Long Filenames on Win98 clients, Domain Login). - The problem did occur on two 32Bit Athlon machines. On another Machine equipped with Athlon 64 (running 64 Bit Linux) the hanging seems not to reproduce. With identical s...

...[2004/10/03 19:19:54, 0] lib/util_sock.c:read_socket_data(384) read_socket_data: recv failure for 4. Error = Connection reset by peer --- I've enabled debug level 10 and loads of tcpdumps but nothing stands out as being obviously wrong. Out of some bizzare hunch I added "max protocol = LANMAN2" and restarted samba. This has made the problems dissapper. However my wife has an older notebook and is still running Win98se, "dropping" the protocol level to LANMAN2 seems to break her machine. I rarely use windows on my laptop but it'd be nice to be wheer I was before the...

...a charm in 3.0.11 domain) When max protocol is NT1 (as in 3.0.11), I can add XP into domain, but can not do domain logon nor "net view /DOMAIN:NIS7" -> the domain is not longer available. "Net view /DOMAIN:NIS" works good - NIS is 3.0.11 samba domain. When I set protocol to LANMAN2, "net view" shows my SAMBA7 server, I can log into domain from already-in-domain XP, but I can not add the XP into domain, when it was removed from it - with "incorrect parameter" message. (The XP is in LDAP and can join the domain with max protocol NT1, as I said). I have trie...

...ested and also partial changes. Both are presenting the same behaviour. Nothing was changed in the AD side. I also re-checked the permissions/ownership on "/var/db/samba4/winbindd_privileged" folder which is used by SQUID. To Rowland: You asked if I really need the "min protocol = LANMAN2" option. Well, the idea was to enforce a minimum security level. Any help will be very appreciated. Regards Fabricio. -----Original Message----- From: Kontrol-Suporte <suporte at kontrolsecurity.com.br> Sent: Saturday, June 23, 2018 3:42 PM To: 'samba at lists.samba.org' <...

...t; logon home = \\%L\%U\.9xprofile > > logon drive = P: > > usershare allow guests = no > > client NTLMv2 auth = yes > > client lanman auth = no > > client plaintext auth = no > > use spnego = yes > > client use spnego = yes > > min protocol = LANMAN2 > > idmap gid = 10000-20000 > > idmap uid = 10000-20000 > > realm = MYDOMAIN.CORP > > security = ads > > template homedir = /home/%D/%U > > template shell = /bin/bash > > winbind offline logon = yes > > winbind refresh tickets = yes > &gt...

hi all! i'm pretty new to linux and just installed a mandrake 8.1 on a little machine in my network. I got the samba server up and running and it even is visible in my windows network folder. but when i try to connect from windows 2000 sp3 the server refuses my login attempts even root... any idea? /christian

Hi, I am having a lot of trouble with getting 0s2 to talk with samba. They seem to be making the right noises at handshake time, and seem to set up a session no problems (using ethereal, monitoring packets). However, when it comes to actually transferring information (such as doing a listing of a share from the os2 box) it crashes with the error: Open AndX Request, Path: \OSO001.MSG; Read