similar to: Error 'getpwuid(3000007) failed' is again. (Rowland penny)

Displaying 20 results from an estimated 6000 matches similar to: "Error 'getpwuid(3000007) failed' is again. (Rowland penny)"

2016 Mar 14
1
Error 'getpwuid(3000007) failed' is again. (Rowland penny)
What do you want to say that Samba4 can not operate as standalone server, only intend for DC ? Or there is other way to use Samba4 simply as filserver. Btw, I was able to use Samba4 as standalone server of 434 version. 2016-03-14 22:40 GMT+03:00 CpServiceSPb . <cpservicespb at gmail.com>: > Sorry. > But my gmail account ... > > > > 2016-03-14 22:34 GMT+03:00
2016 Mar 14
2
Error 'getpwuid(3000007) failed' is again. (Rowland penny)
By the way I provisioned and started Samba4 as standalone server, then I deleted private folder content, then reprovisioned to DC and started as DC. That is there are 2 independent attempts. >*> - as DC and in the way I launched samba daemon, which started in its own *>*> smbd and winbindd daemons => there wasn' t theerror and shares are *>*> available. * > As you seem
2016 Mar 14
1
Error 'getpwuid(3000007) failed' is again. (Rowland penny)
Sorry. But my gmail account ... 2016-03-14 22:34 GMT+03:00 CpServiceSPb . <cpservicespb at gmail.com>: > I provisioned by 2 way: > - as standalone server and in the way I launched nmbd, smbd and winbind => > error "getpwuid(3000007) failed" is got and shares are inaccessible; > - as DC and in the way I launched samba daemon, which started in its own > smbd and
2016 Mar 13
1
Error 'getpwuid(3000007) failed' is again.
Hi all. Recently I built from tarball sources 436 version of Samba4 at Ubuntu 14.04 x64. There wasn' t any Samba at the server before. All started successfully, but in 'standalone server' mode, while accessing to shares, error 'getpwuid(3000007) failed' is appeared as was here https://lists.samba.org/archive/samba/2014-May/181010.html. And it is impossible to open it even
2014 May 02
2
Auth fail getpwuid(3000007) failed
Hi sorry to bother, but all of a sudden after a fresh install of samba with the regular smb4.conf it keeps on failing when users try to authenticate: smbclient -U MyUser \\\\MyServerName\\MyShare MyPassword session setup failed: NT_STATUS_UNSUCCESSFUL [...] check_ntlm_password: authentication for user [MyUser] -> [MyUser] -> [MyUser] succeeded [2014/05/02 10:29:40.930648, 3]
2007 Oct 17
2
[patch] ssh.c load_public_identity_files calls getpwuid twice without copy
Hi, getpwuid is called as seen in the patch, and is then called again indirectly by tilde_expand_filename without first copying off the results from the first call. This is fatal on MacOSX (and it would seem it should be fatal elsewhere, too). Please CC me in replies; I'm not a subscriber. --- openssh-4.4p1/ssh.c 2006-09-01 22:32:40.000000000 -0700 +++ openssh-4.4p1-fix/ssh.c
2007 Oct 20
5
[Bug 1377] New: getpwuid called twice without pwcopy (percent_expand: NULL replacement)
https://bugzilla.mindrot.org/show_bug.cgi?id=1377 Summary: getpwuid called twice without pwcopy (percent_expand: NULL replacement) Classification: Unclassified Product: Portable OpenSSH Version: 4.4p1 Platform: ix86 OS/Version: Mac OS X Status: NEW Severity: major Priority: P2
2017 May 07
2
Samba login failure: getpwuid failed
Hello, I cannot access a remote drive using Windows or smbclient; my authentication appears successful according to the samba log file, but `getpwuid` fails. The server (remote) is running CentOS 7.2 and Samba 4.2.3. The client is CentOS 7.2 and smbclient 4.2.3. The logfile shows: [2017/05/06 22:57:48.729284, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password) check_ntlm_password:
2004 Nov 30
2
getpwuid vs. getpwnam
This issue has probably been brought up before, but I'll mention it anyway. I just downloaded and built openssh 3.9p1 on Solaris 8. In my environment, I have two root accounts. The normal one and an alternate one (rjohn - uid 0) with it's own home directory (/export/home/rjohn). After building and installing openssh, I was having trouble getting my RSA authentication to work. In
2011 Apr 15
1
Dovecot v2.0.12 OpenBSD - getpwuid() error
Hi! I've upgraded from 2.0.11 to 2.0.12. I've experienced errors during delivery with dovecot-lda. The error log attached contains the errors. Since then I had to downgrade to 2.0.11, to make it work again. When starting 2.0.12, it couldn't chown() the files under /var/dovecot (eg.: dict) to the user specified in the configuration file. Configuration: # doveconf -n # 2.0.11:
2018 Feb 14
2
getpwuid failed for single user on single file share
On 02/14/2018 07:46 PM, Rowland Penny via samba wrote: > On Wed, 14 Feb 2018 19:05:34 +0100 > Arne Zachlod via samba <samba at lists.samba.org> wrote: > >> Hello, >> >> I have a problem with my samba installation I can not get my head >> around, maybe some of you have a good idea about what is going on. >> >> I have a file share called
2015 Jan 11
1
Samba4 and 0.0.0.0:137 and 0.0.0.0:138 opened, why ? How do close it ?
Hmmm, I founded some at https://lists.samba.org/archive/samba-technical/2012-July/085752.html As I saw these patches was already implemented. But is it possible to receive broadcast not to 0.0.0.0 but to x.y.z.255 ? This is network broadcast either. And opened 0.0.0.0 even with checking of source net is quite insecure from net security point of view. I think so. May be is it necessary to add
2015 Dec 07
2
Fwd: Functionality of Nmbd at Active Directory mode of Samba4 !
If my messages seems somehow unreadable - I sent it from Gmail Web UI. mathias dufresne, read my 2 or 3 last messages. I wrote about mounting \\server\share as disk and risky fo viruses crypting files. Also read messages other, who does not work in AirBus. And more over, it' s your oppinion. But I see useless of more discussion at atll. If you want to combine your efforts to help with
2006 Mar 02
0
winbind, sIDHistory and getpwuid problems
In our native Win2K3 AD domain, several AD accounts have a sIDHistory that carry SIDs from before the AD domain migration in addition to the "primary" objectSID. Samba 3.0.21c winbindd (with idmap OpenLDAP backend) on domain member servers (running SuSE 9.3 Pro) allocates multiple uids for these SIDs with the same (AD) user name: Primary SID: # getent passwd myuser
2007 Dec 21
2
[Bug 1414] New: Botched getpwuid usage on Mac OS X
https://bugzilla.mindrot.org/show_bug.cgi?id=1414 Summary: Botched getpwuid usage on Mac OS X Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org
2017 May 07
0
Samba login failure: getpwuid failed
On Sun, 7 May 2017 09:04:25 -0500 Michael Schwager via samba <samba at lists.samba.org> wrote: > Hello, > I cannot access a remote drive using Windows or smbclient; my > authentication appears successful according to the samba log file, but > `getpwuid` fails. The server (remote) is running CentOS 7.2 and Samba > 4.2.3. The client is CentOS 7.2 and smbclient 4.2.3. The
2006 Sep 24
2
[Bug 1235] [PATCH] scp does unnecessary getpwuid(), breaking chroot
http://bugzilla.mindrot.org/show_bug.cgi?id=1235 Summary: [PATCH] scp does unnecessary getpwuid(), breaking chroot Product: Portable OpenSSH Version: -current Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: scp AssignedTo: bitbucket at mindrot.org
2017 May 08
1
Samba login failure: getpwuid failed
Hi Rowland, Thanks for the reply. I did as you suggested and did not see any change in my system behavior. I put everything back the way it was. Then I noticed that I have an identical system (so I think) right next to it, on the same rack, connected to the same switch, with the same OS and hardware, and it is working 100%. Fundamentally, I cannot su to my user "developer_prod" as the
2015 Jan 11
3
Samba4 and 0.0.0.0:137 and 0.0.0.0:138 opened, why ? How do close it ?
Thanks for this answer. As I understood, for example if parameter bind interfaces only = yes is and interfaces = lan0 (192.168.0.254) is and if broadcast packet goes from 95.95.95.14 such packet will be dropped (in other words) ? Am I right ? And other thing. Why is 192.168.0.255 (network broadcast) opened for ? May be exact such address (network broadcast) is inbtended for receiving broadcasts
2019 Nov 12
2
Build some shared libraries, and building exact these libraries directly to binaries at the same time.
As I understood it is 2nd case: > Or are there specified binaries where the libraries are builtin to, for examle: > --nonshared-binary=testparm, smbtorture, smbd and so on ? But in the case of binaries list, all binaries mentioned at the list will be linked statically with ALL libraries, not only 3 (in my case) . Am I right ? ??, 12 ????. 2019 ?. ? 20:19, Andrew Bartlett <abartlet at