On 06/22/2011 12:31 AM, mrArcabuz wrote:
Hi, it's been a while since the original message appeared, but here's my
experience in case someone finds it useful:
[...]
I changed the machine account name to uppercase in the passwd & shadow
files and the message does not appear anymore in the log
Hi, it's been a while since the original message appeared, but here's my
experience in case someone finds it useful:
I set up a standalone (tdb backend) PDC on samba 3.4.7 (Ubuntu 10.04 LTS)
and got similar messages as graham-65 did:
[2011/06/21 17:01:45, 1] auth/auth_util.c:577(make_server_inf
BonjourI
I have some problem when I connect my user Windows 7>>user in
passdb - getpwnam+failed
You said
adjust /etc/ldap.conf so that
machine accounts were also listed as valid users on the system.
Could you explain what you do exactly (no /etc/ldap.conf but
/etc/ldap/ldap.con
Hi,
I've just been debugging something related to this. Environment is
samba 3.4.6 with LDAP backend and windows 7 clients. In my case the user
in passdb but getpwnam() fails led me to adjust /etc/ldap.conf so that
machine accounts were also listed as valid users on the system.
I don't reall
Re. the ongoing failure of the windows7 client to authenticate its
machine account, I've upped the log level and added an extra debug
statement to getpwnam_alloc().
There are a couple of discrepancies which I very much hope someone can
explain, or at least point me in the direction of how to r
a slight change in the log entries now, as below.
I don't know why (I don't think I've changed anything), but there is an
extra log entry showing the host is in the passdb, but getpwnam() is
failing.
However, the machine name is definitely in /etc/passwd.
Can anyone cast any light on this appar
Gaiseric Vandal wrote on 03/02/2010 19:15:
it looks like from the log entries that the samba can't find an account
for the machine. The machine- if it is a domain member- does need to
have an account. Were you able to join the machine to the domain? if so
there should be both a samba (windows) ac
it looks like from the log entries that the samba can't find an account
for the machine. The machine- if it is a domain member- does need to
have an account. Were you able to join the machine to the domain? if
so there should be both a samba (windows) account (verify with "pdbedit
-Lv") a
Gaiseric Vandal wrote on 03/02/2010 17:27:
What samba version?
version 3.4.5
> After you login from Win 7 can you actually open
and save files?
yes. I'm not familiar enough with smb etc. to understand why the machine
itself is trying to authenticate in addition to the user, and whether it
What samba version? After you login from Win 7 can you actually open
and save files? It does seem like it is trying to reauthenticate as an
active directory client.
Maybe config samba to only listen on port 139 and not 445 ("smb ports"
in smb.conf.)That might force the Win 7 client to t
10 matches
Mail list logo