similar to: Wrong password, Win10 not using SMB3_11?

On Tue, 16 Jun 2020, Rowland penny via samba wrote: > On 16/06/2020 12:41, Harald Hannelius via samba wrote: >> I have Samba AD-domain with two fileservers and two Samba DS-servers. Most >> people can authenticate OK, but one user always gets "wrong password". > What versions of Samba ? All servers are 4.9.5-Debian. >> Auth: [SMB2,(null)] user [SAD]\[username]

On 16/06/2020 12:41, Harald Hannelius via samba wrote: > I have Samba AD-domain with two fileservers and two Samba DS-servers. > Most people can authenticate OK, but one user always gets "wrong > password". What versions of Samba ? > Auth: [SMB2,(null)] user [SAD]\[username] at [Tue, 16 Jun 2020 > 13:49:02.124298 EEST] with [NTLMv1] status [NT_STATUS_WRONG_PASSWORD]

On Mon, 24 Sep 2018 17:33:47 +0200 Marco Gaiarin via samba <samba at lists.samba.org> wrote: > Mandi! L.P.H. van Belle via samba > In chel di` si favelave... > > > I hope this helps you understanding your problem a bit more. > > See also: > > https://docs.microsoft.com/en-us/windows/security/identity-protection/access-control/local-accounts > > No,

Hi all, Experiencing a really weird issue on my Samba instance (4.7.5). It is not allowing users to browse any shares when running as a systemctl daemon, but it is working fine when running as a foreground service. Contents of systemctl service unit: # cat /usr/lib/systemd/system/smb.service [Unit] Description=Samba SMB Daemon After=syslog.target network.target nmb.service winbind.service

Helpp! :) We didn't catch this in testing and now it's killing me in production! I'm getting stuck with my fresh build of Samba 3.6.10. It isn't honoring groups specified in the valid users clause of the share configuration. I'm running in security = SHARE mode, and user authentication is working just fine. Even if I specify individual users on the valid users = line, it

Hello everyone, I'm sorry for this long post, but I think there is a real understanding problem for many people on ADS domain membership. I'm not the first to post about this type of problem, however I didn't find an answer to it in the archives and I followed the HOWTO-collection. Well, this is what I'm doing : I am using samba-3.0.1 compiled from source, MIT kerberos 1.3.1

I'm running Centos 4.3 and Samba 3.0.24. I have an OpenLDAP backend. I have successfully got a Windows Domain to work, Windows XP -> Samba -> OpenLDAP. I can add machines to the domain and I can login and change passwords. The trouble is that I'm using NTLM and have been told that I must upgrade to NTLMv2, but I'm having great difficulty doing so. I have existing NTLM users. I

Hi all, We're having some issues getting Samba to work in the way we'd like it to in our domain infrastructure. We have a real Windows domain WIN (WIN.DOC.IC.AC.UK) which is run on Windows 2003 domain controllers. We also have an MIT Kerberos realm DOC.IC.AC.UK. A realm trust exists such that WIN.DOC.IC.AC.UK trusts DOC.IC.AC.UK for authentication, and users have appropriate Kerberos

Any and all attempts to connect to our samba server, packaged in the redhat RPM found on samba.org, have failed. The allow statement is set to localhost, x.y.z. where x.y.z is our class C(ended with a period, as per the online help in SWAT.) Local connections via smbclient work beautifully, but connections from any other machine fails. I've followed the troubleshooting procedure to the

Hi I've talked about this in other messages but have a feeling it might have got lost amongst the other symptoms we were discussing. I had a Redhat 9 server on which I'd installed Samba 3.5.6 (built from source). I had it authenticating successfully against a windows 2008 active directory server. I then upgraded the Redhat server to RHEL5.3, on which I installed Samba 3.5.7 (and

Hi, I'm trying to test Samba 3.0.0 beta 1, and so far, one problem I have spent the last couple hours trying to solve, is a problem I am having joining the domain with an NT4 workstation. The samba server is a PDC, and when I try to join the workstation to the samba controlled domain using the root account (which worked on Samba 2.2.8 just fine), I get a message on the NT workstation that it

Hi folks, I'am using Samba 2.0.0 on a Linux and a Sun box and i have the following problem: I can log in from a smbclient but not from an NT Client using Security=Domain. 1.) Doubleclick on the machine opens the password dialouge (which should'n appear, beacuse i'am already logged in the domain) Enter my domainusername and password. Window dissapears and appears again and forces me

Hi, A final repost of the below issue -- we still are not making any progress. It is unclear whether we need to be using winbind -- I don't believe so, and the Terpstra Samba 3 book doesn't suggest that this is necessary in this configuration; but please correct me if my preconception is flawed. If this is the 'wrong place' to ask -- any suggestions about where I should be

smbtorture NEGNOWAIT causes a core dump with a message "Abnormal server exit: multiple negprot's are not permitted". Is that truely by design?? I am running Samba 3.0.23d as AD member server and have smbtorture running on the same machine. Kind regards, Jens Appended: The final second of the smbd... [2007/01/30 16:48:38, 3] smbd/oplock_linux.c:linux_init_kernel_oplocks(260)

So you use images!? Are you shure you used different host names for each client. We found using install images will do this confusion some times because windows announced with the image name not with the new one. EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: mueller at tropenklinik.de

Hello, a heave a share on a samba server 3.6.3 that is used as a DFS-Root. The DFS Links a working on Client with Windows 7 but not on Windows XP clients. Searching on the internet gives me a hint that it can be a problem with "security = ADS". The Samba server is member of a windows 2003 R2 Domain, and the Unix user info (uid, gid) are stored on the domain in der RFC 2302

Hi, I've been fighting against a file server with samba 3.6.9-151.el6 authenticating from a windows 2003 server. I've read a thousand posts and howtos with all kind of samba versions without success. It looks like windbind is not processing things right. I've set the unix permissions on the folder to CANAL4\graficos right and the parent folder is world readable so this should not be

Timo Altun skrev den 2015-05-19 08:12: > Hi Davor, > > thanks for the answer. They were actually part of a NT4 domain called > mayweg.net <http://mayweg.net> (the new realm name). But I did join > workgroup "WORKGROUP" before I tried to join the new domain. > If it's possible that they're sending the information the wrong way > because they were part

I have samba correctly setup to share resources between my linux box and my win98 clients (The encrypted passwording disabled accoringly). I tried to configure it for domain logons with my win98 clients, by enabling WINS server, domain logons, and master browser in the smb.conf. When I login on my win98 machine, I get an error saying that the password is incorrect (which it isn't) or the

I've had the following setup working for years now. Subnet A contains linux/windows workstations along with the PDC+LDAP. Subnet B contains a BDC+LDAP and a domain member on the file server that windows users connect too. Whats new is I'm setting up a new domain member in Subnet B. It has joined the domain and net getdomainsid works. From machines in Subnet B I can run smbclient -L and